Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

netconn: last_update vs start #5

Open
jeromekleinen opened this issue Feb 26, 2018 · 0 comments
Open

netconn: last_update vs start #5

jeromekleinen opened this issue Feb 26, 2018 · 0 comments

Comments

@jeromekleinen
Copy link

Hey guys,

First of all, thanks for the scripts.

I have a small remark regarding the netconn script. I would expect this script to pull out all the network connections that occurred over the past x minutes. However, because carbon black stores its information structured around processes I feel that the current query is not entirely accurate. The script is currently pulling out the network connections for processes started in the last x minutes.

If a process has been running for over the x minute threshold and it performs a new network connection, the last_update timestamp of that process would be updated. Therefore I would suggest to change the query from 'start:-x' to 'last_update:-x' and (optionally) filtering the results returned in the process_search function based on the timestamp of the network connection.

What do you guys think? I guess it somewhat depends on what you are trying to achieve with the script :)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant