-
Notifications
You must be signed in to change notification settings - Fork 176
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
fix - IAM User takeover Correlation Rule correlating on IP instead of user #1362
fix - IAM User takeover Correlation Rule correlating on IP instead of user #1362
Conversation
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.
I think this need to correlate on both IP and target user name. We want to detect when [email protected] resets Bob's password, then Bob logs in from 11.22.33.44.
Username Bob is in the requestParameters.userName
field in the PasswordReset rule, and would be the last part of userIdentity.arn
in the Login rule.
…ating-on-IP-instead-of-user
@arielkr256 We cannot correlate on both. We can add some context field to both rules that will contain both IP and user name and try correlating on this list, but I'm not sure that this is a good idea (it is not an explicit approach) and that it will work. What do you think about that? |
…ating-on-IP-instead-of-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.
LGTM!
Background
Fixes #1359
Changes