AWS Suspicious SAML Activity
Identifies when suspicious SAML activity has occurred in AWS. An adversary could gain backdoor access via SAML.
Detection logic
Detection requirements
- Platform
- ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 3 ATT&CK techniques it maps to.
- Log source product
- aws
- Log source service
- cloudtrail
Known benign triggers
- Automated processes that uses Terraform may lead to false positives.
- SAML Provider being updated from unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
- SAML Provider could be updated by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| docs.aws.amazon.com/IAM/latest/APIReference/API_UpdateSAMLProvider.html | 2from 2 sources |
| docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithSAML.html | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- f43f5d2f-3f2a-4cc8-b1af-81fde7dbaf0e
- Tagged by the source as
- attack.initial-accessattack.lateral-movementattack.persistenceattack.privilege-escalationattack.stealth
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1