Has disabled Purview Audit on targeted accounts prior to stealing emails from Microsoft 365 tenants.1
Disable or Modify Cloud Log T1685.002
- Tactic
- Defense Impairment
- Platforms
- IaaS, SaaS, Identity Provider, Office Suite
- Version
- 1.0
- Created
- 14 April 2026
- Last modified
- 12 May 2026
- Contributors
- Alex Soler, AttackIQ; Arun Seelagan, CISA; Ibrahim Ali Khan; Janantha Marasinghe; Joe Gumke, U.S. Bank; Matt Snyder, VMware; Prasad Somasamudram, McAfee; Sekhar Sarukkai, McAfee; Syed Ummar Farooqh, McAfee
An adversary may disable or modify cloud logging capabilities and integrations to limit what data is collected on their activities and avoid detection. Cloud environments allow for collection and analysis of audit and application logs that provide insight into what activities a user does within the environment. If an adversary has sufficient permissions, they can disable or modify logging to avoid detection of their activities.
Disable or Modify Cloud Log MITRE reference T1685.002
1 group has been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
All 1 groups for this technique
1 software entry is documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Can disable or otherwise restrict various AWS logging services, such as AWS CloudTrail and VPC flow logs.1
All 1 software entries for this technique
Offense vs defense T1685.002
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Disable or Modify Cloud Log detection strategy DET0289
MITRE names one behaviour worth catching for this technique and breaks it into 4 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection Strategy for Disable or Modify Cloud Log
AN0801 · IaaS
Cloud API events where logging services are stopped, deleted, or modified in a way that disables audit visibility. Defender view: unauthorized StopLogging, DeleteTrail, or UpdateSink operations correlated with privileged user activity.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Cloud Service ModificationDC0069 | gcp:config | UpdateSink request modifying log export destinations |
| Cloud Service DisableDC0090 | AWS:CloudTrail | Stop logging for an existing CloudTrail |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| AdminRoles | Define which roles are authorized to stop or modify logging. |
| RegionScope | Adjust monitoring to ensure multi-region logging tampering is caught. |
AN0802 · Identity Provider
Disabling or modifying sign-in or audit log collection for user activities. Defender view: policy or configuration updates removing logging coverage for critical accounts.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Cloud Service ModificationDC0069 | azure:policy | DisableAuditLogs or ConditionalAccess logging changes |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| CriticalAccounts | Tune to prioritize logging changes that affect administrative or high-value accounts. |
AN0803 · Office Suite
Disabling mailbox or tenant-level audit logging, often using Set-MailboxAuditBypassAssociation or downgrading license tiers. Defender view: sudden absence of mailbox activity logging for monitored users.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| User Account ModificationDC0010 | m365:unified | Set-MailboxAuditBypassAssociation or disabling Advanced Auditing |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| UserScope | Tune alerts for users where mailbox auditing should always remain enabled. |
AN0804 · SaaS
Disabling or altering security and audit logs in SaaS admin panels (e.g., Slack, Zoom, Salesforce). Defender view: API calls or admin console changes that stop event exports or logging integrations.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Cloud Service DisableDC0090 | saas:audit | Log export integration removed or disabled |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| IntegrationScope | Define which SaaS log integrations are required and alert if removed. |
Configure default account policy to enable logging. Manage policies to ensure only necessary users have permissions to make changes to logging policies.
Tests from Atomic Red Team (MIT licence) · technique definition