[New Rule] Elastic Endpoint and External Alerts#42
Conversation
| rule_name_override = "message" | ||
| severity = "medium" | ||
| tags = ["Elastic"] | ||
| timestamp_override = "event.ingested" |
There was a problem hiding this comment.
I don't think we want to override the timestamp here since event.ingested might not be filled in for most external alerts?
There was a problem hiding this comment.
when a timestamp override is defined and missing, does it default back to @timestamp?
There was a problem hiding this comment.
Yes, will need to add to signal metadata so the user knows this happened.
|
For the folder layout, I think we can rename the |
| investigating external alerts in the app. | ||
| """ | ||
| language = "kuery" | ||
| license = "Elastic License" |
There was a problem hiding this comment.
Add max_signals = unbounded (and support for unbounded 😉 )
Co-authored-by: Ross Wolf <31489089+rw-access@users.noreply.github.com>
Co-authored-by: Justin Ibarra <brokensound77@users.noreply.github.com>
rw-access
left a comment
There was a problem hiding this comment.
LGTM if we can make logs-* more precise
|
|
||
|
|
||
| [[rule.risk_score_mapping]] | ||
| field = "event.risk_score" |
There was a problem hiding this comment.
We may want to use event.risk_score_norm here, but I'm not quite sure the endpoint is populate that field as well. Will verify during testing.
I've asked internally for what we could refine this further to. Will leave the comment above unresolved for reference/tracking. |
Issues
Resolves #41
Summary
In support of elastic/kibana#65942 to create two new pre-packaged rules that will enable
Elastic Endpoint AlertsandExternal Alertsto be used in investigations.This also includes updates to
schema.pyfor the new fields added to therules_schemaas part of elastic/kibana#70288. These new fields include:Note:
risk_score_mappingandseverity_mappingare subject to change depending on the desired implementation.Contributor checklist