Attack scenario · Data security

CloudTrail logging impairment

How can CloudTrail logging be disabled, and how do you prevent it? Before acting, an adversary with administrative rights stops or narrows CloudTrail logging so that later activity leaves little evidence.

Fictional, educational scenarioLoss of visibilityLast updated · ATT&CK v20.1

Attack path · 5 stages

  1. 1

    Obtain administrative access

    T1078.004

  2. 2

    Inspect logging configuration

    T1526

  3. 3

    Stop or narrow logging

    T1685.002

  4. 4

    Remove stored evidence

    T1070T1485

  5. 5

    Act with reduced visibility

    T1530

For leadership

Executive summary

Audit logs are how an organization reconstructs what happened during an incident, satisfies regulators and decides what to tell customers. An attacker with enough privilege will try to switch them off, narrow what they record, or delete what has already been collected — leaving the company unable to answer basic questions later. The good news is that AWS offers strong ways to make logging tamper-resistant: an organization-wide trail managed centrally, logs stored in a separate account, and organization policies that stop even account administrators from disabling them. If an ordinary administrator in a production account can turn off logging, that is a governance gap worth closing quickly.

For engineers

Technical summary

cloudtrail:StopLogging, DeleteTrail, UpdateTrail (for example, disabling multi-region or changing the destination), PutEventSelectors (dropping event types) and log-bucket policy or lifecycle changes reduce or remove audit evidence. Since ATT&CK v19 this behaviour is T1685.002 under the Defense Impairment tactic (previously T1562.008 under Defense Evasion, now revoked).

Environment and assumptions

Fictional company: each account has its own single-region trail created by a setup script, writing to a bucket in the same account. Account administrators have AdministratorAccess. No SCPs protect CloudTrail.

  • The adversary has administrator-level access in one member account.
  • GuardDuty is enabled but its findings go to an unmonitored email list.
  • Fictional and simplified for education.

Interactive

Attack sequence

Select a stage, or use the arrow keys, to see preconditions, evidence and controls.

Stage 1

Obtain administrative access

The adversary operates with an administrator session in the account.

Preconditions
  • Compromised admin identity
Required access
  • AdministratorAccess.
Potential evidence
  • IdP and CloudTrail anomalies
Defensive controls
  • Phishing-resistant MFA
  • Minimize standing admin access
Text version of the attack sequence
  1. Obtain administrative access (T1078.004). The adversary operates with an administrator session in the account. Preconditions: Compromised admin identity. Evidence: IdP and CloudTrail anomalies. Controls: Phishing-resistant MFA; Minimize standing admin access.
  2. Inspect logging configuration (T1526). The adversary checks which trails, event selectors and detectors exist. Preconditions: cloudtrail:DescribeTrails / GetEventSelectors. Evidence: CloudTrail: DescribeTrails, GetTrailStatus, GetEventSelectors, guardduty:ListDetectors. Controls: None preventive; useful as context for detection.
  3. Stop or narrow logging (T1685.002). The adversary stops the trail, or more subtly removes write events via event selectors or limits the trail to one region. Preconditions: cloudtrail:StopLogging / PutEventSelectors / UpdateTrail on the trail; No SCP denying these actions. Evidence: CloudTrail records StopLogging / PutEventSelectors / UpdateTrail before taking effect; GuardDuty Stealth finding for disabled logging. Controls: Organization trail managed centrally; SCP denying trail changes in member accounts.
  4. Remove stored evidence (T1070, T1485). Because logs are stored in the same account, the adversary shortens bucket lifecycle rules or deletes objects. Preconditions: s3:PutLifecycleConfiguration / DeleteObject on the log bucket. Evidence: CloudTrail: PutBucketLifecycle, DeleteObjects on the log bucket (data events). Controls: Logs delivered to a separate log-archive account; S3 Object Lock on the log bucket.
  5. Act with reduced visibility (T1530). Subsequent data access or changes are not recorded, or records are later lost. Preconditions: Logging impaired. Evidence: Gaps in log delivery; GuardDuty findings (separate data pipeline). Controls: Independent detection sources (GuardDuty) with monitored delivery.

Technique mapping

MITRE ATT&CK and ATLAS techniques referenced in this scenario
IDTechniqueTactics (official)Stages
T1078.004Valid Accounts: Cloud AccountsInitial Access, Persistence, Privilege Escalation, Stealth1
T1526Cloud Service DiscoveryDiscovery2
T1685.002Disable or Modify Tools: Disable or Modify Cloud LogDefense Impairment3
T1070Indicator RemovalStealth4
T1485Data DestructionImpact4
T1530Data from Cloud StorageCollection5

Technique names and tactic assignments come from the imported MITRE data. Mapping a stage to a technique is Securitain’s analysis.

Why the attack can succeed

  • Each account controls its own trail, so any account administrator can change it.
  • Logs live next to the workloads they describe.
  • Alerts exist but nobody owns them.

What prevents or limits the attack

What may detect the attack

Detection signals and telemetry sources
SignalTelemetry sourceNotes
StopLogging, DeleteTrail, UpdateTrail, PutEventSelectorsCloudTrail management events (recorded before the change takes effect)Alert in real time via EventBridge.
Gap in log delivery for an account or regionLog pipeline monitoring / CloudTrail digest files—
GuardDuty finding for CloudTrail logging disabledGuardDuty—
Lifecycle or deletion activity on log bucketsCloudTrail management and S3 data events—

Telemetry only helps if it is enabled before the incident and someone acts on it. Listing a signal here does not mean it is collected or monitored in your environment.

What Securitain may assess

  • Securitain can assess todayEffective-permission view that considers managed, inline, group, boundary and SCP policies together. Learn more
  • Outside Securitain’s current scopeSecuritain’s current product pages do not describe CloudTrail or GuardDuty configuration checks; validate logging posture with AWS Config, Security Hub or your own review.
  • Outside Securitain’s current scopeReal-time detection of attacker activity in CloudTrail is not part of Securitain’s current assessment — use GuardDuty, a SIEM or your SOC for that.

For leadership

Executive implications

operations
Investigation becomes slower and less certain; responders may have to assume worst-case scope.
compliance
Audit-logging requirements in most frameworks are directly affected; regulators and customers may require evidence that no longer exists.
integrity
Without logs it is harder to prove which resources were changed.

No financial loss estimates are given; impact depends on the data, contracts and regulation involved.

Next steps

  1. Confirm a multi-region organization trail exists and delivers to a separate account.
  2. Attach an SCP protecting CloudTrail and GuardDuty to all workload OUs.
  3. Route logging-change alerts and GuardDuty findings to an owned queue.
  4. Enable log file integrity validation and Object Lock on the archive bucket.
  5. Use the Cloud Logging Readiness Checklist to check remaining gaps.

References

MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. ATT&CK data © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation (ATT&CK v20.1). Securitain is not affiliated with or endorsed by MITRE. Explanations, scenarios and control mappings on this page are Securitain’s own analysis. Sources and licensing

Stay in the loop

Cloud security insights, early access & compliance updates

Weekly InsightsEarly AccessExpert Content
No spam, everUnsubscribe anytimeWeekly updates
Chat with Securitain