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

[Deprecation] AWS EC2 Snapshot Activity #3906

Open
imays11 opened this issue Jul 18, 2024 · 2 comments
Open

[Deprecation] AWS EC2 Snapshot Activity #3906

imays11 opened this issue Jul 18, 2024 · 2 comments

Comments

@imays11
Copy link
Contributor

imays11 commented Jul 18, 2024

Link to Rule

https://github.com/elastic/detection-rules/blob/main/rules/integrations/aws/exfiltration_ec2_snapshot_change_activity.toml

Description

This rule is very broad, capturing any time an EC2 instance snapshot's permission settings are modified via the ModifySnapshotAtrribute API.

This could be used to:

  • grant access to a single external account add: <external.account.id>
  • make the snapshot public add : all
  • remove access from a single external account remove: <external.account.id>

PROBLEM:
The problem is that this rule is too generic and so captures all 3 of these very different activities. Additionally, this new rule : AWS EC2 EBS Snapshot Shared with Another Account @terrancedejesus captures the first use case listed above which means duplicate alerts for the same behavior as shown below.

Screenshot 2024-07-18 at 4 17 25 PM

SUGGESTION:

  1. deprecate this rule because it's too broad
  2. tune the existing new rule description, AWS EC2 EBS Snapshot Shared with Another Account, to include that this query actually captures both external account sharing and when a snapshot is made public
  3. create a new rule to capture the removal of permissions for a snapshot
@imays11 imays11 self-assigned this Jul 18, 2024
@botelastic
Copy link

botelastic bot commented Sep 16, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added the stale 60 days of inactivity label Sep 16, 2024
@Mikaayenson Mikaayenson added backlog and removed stale 60 days of inactivity labels Sep 17, 2024
@imays11
Copy link
Contributor Author

imays11 commented Sep 17, 2024

this will be addressed this quarter as a part of AWS rule tuning effort

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

No branches or pull requests

2 participants