-
Notifications
You must be signed in to change notification settings - Fork 500
aws.cloudtrail: improve CloudTrail user identity processing #15601
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -32,7 +32,6 @@ | |
"session_issuer": { | ||
"account_id": "00000000000", | ||
"arn": "arn:aws:iam::00000000000:role/private-ec2-instance-role", | ||
"principal_id": "PRINCIPALID", | ||
"type": "Role" | ||
} | ||
}, | ||
|
@@ -70,8 +69,9 @@ | |
"arn:aws:sts::00000000000:assumed-role/private-ec2-instance-role/i-03cd6b2a7eb4bf3ae" | ||
], | ||
"user": [ | ||
"PRINCIPALID:i-03cd6b2a7eb4bf3ae", | ||
"private-ec2-instance-role" | ||
"PRINCIPALID", | ||
"private-ec2-instance-role", | ||
"i-03cd6b2a7eb4bf3ae" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This seems more odd, since this is a session now. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. From this same conversation, the goal is to consider the session name as temporary user name, that's why it is being mapped as |
||
] | ||
}, | ||
"source": { | ||
|
@@ -113,7 +113,10 @@ | |
"version_protocol": "tls" | ||
}, | ||
"user": { | ||
"id": "PRINCIPALID:i-03cd6b2a7eb4bf3ae", | ||
"changes": { | ||
"name": "i-03cd6b2a7eb4bf3ae" | ||
}, | ||
"id": "PRINCIPALID", | ||
"name": "private-ec2-instance-role" | ||
}, | ||
"user_agent": { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems odd to me to map a role as a user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This come from this conversation with the trade team, where they need to treat the IAM user name and the role name as the
user.name
for the AWS SIEM rules.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@efd6 A lot of our cloud based detection rules are anomaly based, so doing it this way allows us to track the overall behavior of a role across many different temporary sessions in the same way that we track a user's behavior over time. Here is an example rule that uses the user.name field to determine the first time a User or a Role updates an existing AssumeRole Policy, which could be a privilege escalation attempt. We want to examine the history of the Role's behavior in the same way we would an IAMUser identity.