TA0112Tactic 8 of 15

Defense Impairmentin cloud and AI environments

How do attackers disable cloud logging and security monitoring?

ATT&CK v20.1Updated Official tactic page
Defense Impairment technique map18 techniques in Defense Impairment, 6 of them apply to cloud platforms. Highlighted: T1685.002, T1685, T1686.001, T1578, T1556.009.T1556T1578T1685T1686TA011218 TECHNIQUES
Key for cloud (this guide)Applies to cloud platformsOther platforms
18
Techniques
39
Sub-techniques
6
Apply to cloud platforms
4
Defensive controls
3
Detection signals

What the tactic means

Defense Impairment covers techniques that degrade, disable or undermine security controls and monitoring — direct interference with defensive systems, so defenders cannot see or trust what is happening. It was introduced in ATT&CK v19 (April 2026) when the former Defense Evasion tactic was split.

The adversary is trying to break security mechanisms, pipelines, and tooling so defenders can’t see or trust what’s happening.

Defense Impairment consists of techniques that degrade, disable, or undermine the effectiveness and trustworthiness of security controls and monitoring mechanisms. These techniques are characterized by direct interference with defensive systems. The goal is to reduce defenders’ ability to detect, interpret, or respond to adversary activity.

MITRE ATT&CK TA0112 description

Why it matters: cloud, AWS and AI

Cloud environments

In cloud, defenses are configured through the same APIs an adversary uses. Anyone with enough permissions can stop logging, narrow event selectors, disable detectors or open firewalls unless organization-level guardrails prevent it.

AWS specifics

Key AWS examples: cloudtrail:StopLogging / DeleteTrail / PutEventSelectors, guardduty:DeleteDetector / UpdateDetector, deleting VPC flow logs, modifying security groups or network ACLs (cloud firewall), and modifying compute infrastructure (snapshots, instances) to sidestep controls.

AI & workloads

Disabling model-invocation logging or agent audit trails removes the only record of what an AI agent was asked and did.

AWS API calls to know
  • cloudtrail:StopLogging / PutEventSelectors / UpdateTrailStop or narrow CloudTrail recording.
  • guardduty:DeleteDetector / UpdateDetectorDisable managed threat detection.
  • ec2:DeleteFlowLogs / AuthorizeSecurityGroupIngressRemove network visibility or open access.

What the attacker is trying to achieve

  1. 01Stop or reduce audit logging
  2. 02Disable or blind detection services
  3. 03Weaken network controls

Techniques that matter most in cloud

What it needs, and what breaks it

Attacker needs

  • Permissions to administer logging or detection
  • No organization guardrails

Defenders control

  • Organization trail managed centrally
  • SCPs denying logging/detection changes in member accounts
  • Separate log-archive account with Object Lock and integrity validation
  • Owned real-time alerts on logging changes

Detection signals and telemetry

Signal
  • StopLogging, DeleteTrail, UpdateTrail, PutEventSelectors

    CloudTrail (recorded before taking effect)
  • GuardDuty detector changes and logging-disabled findings

    GuardDuty / CloudTrail
  • Gaps in log delivery

    Log pipeline monitoring

For leadership

What this means for the business

If an ordinary account administrator can switch off the audit trail, the organization’s ability to investigate depends on attackers being polite. Organization-level guardrails make this a governance decision rather than an individual one.

Common misconceptions

Myth

“If CloudTrail is enabled, we will see the attack.”

Reality

Trails can be stopped, narrowed or deleted by sufficiently privileged identities; and many data reads are not logged without data events.

Myth

“Defense Impairment is the same as the old Defense Evasion.”

Reality

Defense Impairment contains the tampering half of the old tactic; concealment techniques moved to Stealth (TA0005).

Practical security checklist

0 of 4 done

Saved only in this browser. Nothing is sent to Securitain.

Related attack scenarios

Where Securitain fits

  • 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.

Official sources and 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