AWS CloudTrail Log Suspended
Description
Detects Cloudtrail logging suspension via StopLogging API. Stopping CloudTrail eliminates forward audit visibility and is a classic defense evasion step before sensitive changes or data theft. Investigate immediately and determine what occurred during the logging gap.
Query · kuery
data_stream.dataset: "aws.cloudtrail"
and event.provider: "cloudtrail.amazonaws.com"
and event.action: "StopLogging"
and event.outcome: "success"
Investigation fields
Pivot points the source recommends for triage.
@timestampuser.nameuser_agent.originalsource.ipaws.cloudtrail.user_identity.arnaws.cloudtrail.user_identity.typeaws.cloudtrail.user_identity.access_key_idevent.actionevent.outcomecloud.account.idcloud.regionaws.cloudtrail.request_parameters
Known false positives
- Suspending the recording of a trail may be done by a system or network administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment. Trail suspensions from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
Analyst notes
Investigating AWS CloudTrail Log Suspended
AWS CloudTrail is a service that enables governance, compliance, and operational and risk auditing of your AWS account. It logs API calls and related events, providing visibility into user activity. This rule identifies the suspension of an AWS log trail using the StopLogging API. Attackers can do this to cover their tracks and impact security monitoring that relies on this source.
Possible investigation steps
- Actor & scope
- Identify
aws.cloudtrail.user_identity.arn,user_agent.original,source.ip. - Determine which trail stopped and whether it’s multi-region or organization-wide.
- Timing and impact
- When did logging stop and resume (if at all)? Are there overlapping detections indicating activity during the gap?
- Correlate activity
- Search for sensitive API activity around the stop event (IAM changes, S3 policy changes, EC2 exports, KMS changes).
- Check for preceding
UpdateTrail(e.g., destination change) and subsequentDeleteTrail.
False positive analysis
- Planned suspensions: Rare; verify maintenance tickets and ensure post-change validation.
Response and remediation
- Restart logging (
StartLogging) immediately. - Investigate actor’s recent activity; rotate credentials if suspicious.
- Validate trail configuration, destination bucket/CMK, and event selectors.
- Hardening: Limit
cloudtrail:StopLoggingto break-glass roles; alert on any future stops; enforce via AWS Config/SCPs.
Additional information
- AWS IR Playbooks
- AWS Customer Playbook Framework
- Security Best Practices: AWS Knowledge Center – Security Best Practices.