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

Evidence Artifacts object doesn't have attributes to describe registry keys or values #1077

Closed
davemcatcisco opened this issue May 7, 2024 · 0 comments

Comments

@davemcatcisco
Copy link
Contributor

davemcatcisco commented May 7, 2024

A Detection Finding event contains an array of Evidence Artifacts objects whose purpose is:

Describes various evidence artifacts associated to the activity/activities that triggered a security detection.

The Evidence Artifacts object in turn has attributes which enable a security product to describe all the observables and activities associated with the detection. The description for each of these attributes is almost identical, following the pattern:

Describes details about the [whatever] associated to the activity that triggered the detection.

These attributes cover many things (files, processes, network endpoints, DNS queries, etc.) but don't cover registry keys and values. The registry is hugely important in the context of Windows detections because adversaries use the registry to implement many tactics including Defense Evasion, Persistence, Privilege Escalation, etc. Hence a lot of detection content is triggered by registry activity.

I propose to address this gap with a PR that will add the pre-existing reg_key and reg_value attributes to the Evidence Artifacts object.

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

1 participant