Log-Auditing - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/tags/log-auditing/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 15 Jul 2026 14:10:02 +0000AWS CloudTrail Log Updatedhttps://feed.craftedsignal.io/briefs/2026-07-aws-cloudtrail-updated/Wed, 15 Jul 2026 14:10:02 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-07-aws-cloudtrail-updated/Adversaries can modify AWS CloudTrail configurations via the UpdateTrail API to reduce logging visibility, change log destinations, or weaken integrity, aiming to evade detection by preventing critical audit information from being collected or stored properly.Adversaries often seek to impair an organization's ability to monitor their activities, and modifying logging configurations is a key tactic. This threat involves the use of the AWS CloudTrail UpdateTrail API call by malicious actors to alter existing CloudTrail configurations. These modifications can include changing the S3 bucket where logs are stored, redirecting logs to a different CloudWatch Logs log group, modifying the KMS Key ID used for encryption, or disabling critical features like multi-region logging or the inclusion of global service events. The primary goal is to reduce visibility into their actions, weaken logging integrity, and evade detection by security monitoring systems. This technique allows attackers to maintain a facade of logging while preventing crucial audit data from being captured, making it harder for defenders to trace their activities.

Attack Chain

[Attack Chain is omitted as the source only describes a single, specific API action for defense evasion, not a multi-step sequence from initial access to impact.]

Impact

Successful modification of AWS CloudTrail logs can severely degrade an organization's security posture by creating blind spots in audit trails. If an attacker successfully reconfigures CloudTrail, security teams may lose critical visibility into API calls and other events within their AWS environment, especially during a period of active compromise. This lack of logging hinders incident response, forensic analysis, and compliance efforts, potentially allowing attackers to maintain persistence, exfiltrate data, or deploy further malicious payloads undetected. The integrity of past and future audit data is compromised, making it difficult to assess the full scope of a breach or to prove compliance with regulatory requirements.

Recommendation

  • Deploy the AWS CloudTrail Log Updated Sigma rule to detect any modifications to CloudTrail configurations.
  • Investigate all alerts from the AWS CloudTrail Log Updated rule by examining the aws.cloudtrail.user_identity.arn, user_agent.original, and source.ip fields to verify if the user identity, user agent, or hostname involved in the UpdateTrail call is authorized to make such changes.
  • Review the aws.cloudtrail.request_parameters for specific changes to S3BucketName, CloudWatchLogsLogGroupArn, KmsKeyId, IsMultiRegionTrail, or IncludeGlobalServiceEvents to understand the exact nature of the modification.
  • Correlate UpdateTrail events with preceding StopLogging or subsequent DeleteTrail API calls to identify more severe attempts to disable logging entirely.
  • Harden your AWS environment by constraining cloudtrail:UpdateTrail permissions to only authorized roles or users and require approval workflows for any CloudTrail configuration changes. Implement AWS Config rules to monitor for unauthorized modifications to CloudTrail trails.
]]>highadvisorycloud-securityawslog-auditingimpactdefense-evasion