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

Additional fields to Detection Finding #965

Open
ggacusan-at-duo opened this issue Feb 14, 2024 · 1 comment
Open

Additional fields to Detection Finding #965

ggacusan-at-duo opened this issue Feb 14, 2024 · 1 comment
Labels
findings Issues related to Findings Category

Comments

@ggacusan-at-duo
Copy link

ggacusan-at-duo commented Feb 14, 2024

Tagged Events if Raised
There might be some cases where an IT configures their threat detection platform to highlight specific events that are of interest to them. For example, the IT configures their platform to highlight / tag if a Finding originates from a known anomalous network. If the Product surfaces an event from this known anomalous network, then we need some way to highlight or tag the event to the IT with associated reasons. This might make sense in the Metadata field

New User
It might be of interest to note if a user has been newly added or has not authenticated in a while. Attackers can create new users or authenticate into a dormant user. This might make sense in the User field

Additional Network Connection fields
To help an incident responder, it might be helpful to highlight benign characteristics of certain network details, such as if it is a frequent network / netblock for an organization or if the IP is allow-listed. This might make sense in the Network Connection Information field


Example of this use case from Duo Trust Monitor
https://duo.com/docs/adminapi#trust-monitor

@floydtree floydtree added the findings Issues related to Findings Category label Feb 27, 2024
@guy9001
Copy link

guy9001 commented Mar 28, 2024

@ggacusan-at-duo do you have examples of how you would like to embed this in the objects?
This sounds to me like general enrichments and not necessarily a new attribute.
Something we just wanted to suggest as well is to have Array[Enrichment] for OCSF objects as well, and not just for event classes like today. I think this could help your use case, so for User you could have an enrichment called "is_new" with a boolean value ,etc.
WDYT?

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

No branches or pull requests

3 participants