Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Get Process #590

Open
ai-ryanbess opened this issue Dec 17, 2024 · 6 comments
Open

Get Process #590

ai-ryanbess opened this issue Dec 17, 2024 · 6 comments

Comments

@ai-ryanbess
Copy link

Hello,
Is there a module created that would allow a user to enter a source and destination ip and when entered the result would be the process from an endpoint that initiated the connection?

@carlosmmatos
Copy link
Contributor

@ai-ryanbess - unfortunately an API for this does not currently exist.

@ai-ryanbess
Copy link
Author

Is there a module that we can use to send a custom written FQL search that the API would take in and process?

@carlosmmatos
Copy link
Contributor

We'll poke around - might be able to leverage the Logscale API's to see if it's doable

@ai-ryanbess
Copy link
Author

Thank you. That seems like exactly what we would like to do.

@ai-ryanbess
Copy link
Author

We'll poke around - might be able to leverage the Logscale API's to see if it's doable

Also to add, we'd like to also get the command line that called the processes and possible some other stuff like parent process etc. Our goal is to provide our IR team a quick simple way of feeding in some simple data (collected via an ansible survey) and have ansible quickly spit back the root cause.

@carlosmmatos
Copy link
Contributor

The way this would most likely work is:

  • You define the LogScale FQL filter. Obviously this must be a valid filter and something you can define/test via logscale.
  • The Module will send that query and then wait for the response
  • You will then get back a JSON representation of that response.
    With the return, you can parse/use whatever fields are returned back based on your query.

So ideally, if you can do this in logscale/ngsiem today from the UI in the sense of getting the data you need, then this module will essentially do the same.

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

No branches or pull requests

2 participants