Isai
28f227ab6f
* [Rule Tunings] AWS EC2 EBS Snapshot and Encryption Rules AWS EC2 Encryption Disabled rule performance is good, telemetry looks low as expected - additional context to description to emphasize the security concern and purpose of the rule - updated investigation guide - added highlighted fields - reduced execution window AWS EC2 EBS Snapshot Access Removed rule alerts as expected, telemetry volume is low as expected. however, this rule can be accomplished using EQL so I've changed the rule type - changed rule type to eql - added index - updated IG - added highlighted fields note: I have to use `any` for the query since there is no `event.category` defined for `event.action: ModifySnapshotAttribute` AWS EC2 EBS Snapshot Shared or Made Public Converted to EQL. As an ESQL rule the primary benefit was being able to definitely exclude instances where a user adds their own account id when calling the ModifySnapshotAttribute instead of an external account id. This is a redundant action as the snapshot when created is automatically shared with the account it's created in. But this could be a false positive if it's done by mistake. Instead of keeping this as an ESQL rule, I still think there is more value to converting this to EQL for both customer alert context and telemetry. When looking at production data, I saw no instances where the owning account id was added in this way. Its a rare mistake that shouldn't happen often enough to support keeping this as an ESQL rule. - converted to EQL - added index - updated IG - updated description - added highlighted fields * adding event_category_override = "event.provider" override event.category to event.provider to account for the use of "any" in EQL query * normalizing IG title capitalization normalizing IG title capitalization * bumping severity to medium since EC2 snapshot data can be sensitive, unauthorized sharing or access removal should be triaged * updated event_category_override field replaced event.provider with event.type to satisfy EQL library parsing requirements
rules/
Rules within this folder are organized by solution or platform. The structure is flattened out, because nested file hierarchies are hard to navigate and find what you're looking for. Each directory contains several .toml files, and the primary ATT&CK tactic is included in the file name when it's relevant (i.e. windows/execution_via_compiled_html_file.toml)
| folder | description |
|---|---|
. |
Root directory where rules are stored |
apm/ |
Rules that use Application Performance Monitoring (APM) data sources |
cross-platform/ |
Rules that apply to multiple platforms, such as Windows and Linux |
integrations/ |
Rules organized by Fleet integration |
linux/ |
Rules for Linux or other Unix based operating systems |
macos/ |
Rules for macOS |
ml/ |
Rules that use machine learning jobs (ML) |
network/ |
Rules that use network data sources |
promotions/ |
Rules that promote external alerts into detection engine alerts |
windows/ |
Rules for the Microsoft Windows Operating System |
Integration specific rules are stored in the integrations/ directory:
| folder | integration |
|---|---|
aws/ |
Amazon Web Services (AWS) |
azure/ |
Microsoft Azure |
cyberarkpas/ |
Cyber Ark Privileged Access Security |
endpoint/ |
Elastic Endpoint Security |
gcp/ |
Google Cloud Platform (GCP) |
google_workspace/ |
Google Workspace (formerly GSuite) |
o365/ |
Microsoft Office |
okta/ |
Oka |