Disable or Modify Tools: Disable or Modify Cloud Log
- ID
- T1685.002
- Tactics
- TA0112 Defense Impairment
- Sub-technique of
- T1685 Disable or Modify Tools
- Platforms
- IaaS, SaaS, Identity Provider, Office Suite
- Data sources
- Cloud Service Disable, Cloud Service Modification, User Account Modification
- Source
- attack.mitre.org
- MITRE last modified
- 12 May 2026
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.
For example, in AWS an adversary may disable CloudWatch/CloudTrail integrations prior to conducting further malicious activity. They may alternatively tamper with logging functionality, for example, by removing any associated SNS topics, disabling multi-region logging, or disabling settings that validate and/or encrypt log files.[1][2] In Office 365, an adversary may disable logging on mail collection activities for specific users by using the Set-MailboxAuditBypassAssociation cmdlet, by disabling M365 Advanced Auditing for the user, or by downgrading the user’s license from an Enterprise E5 to an Enterprise E3 license.[3]
Detection
- DET0289 Detection Strategy for Disable or Modify Cloud Log
Data components: Cloud Service Disable, Cloud Service Modification, User Account Modification
Mitigations (1)
- M1018 User Account Management
Configure default account policy to enable logging. Manage policies to ensure only necessary users have permissions to make changes to logging policies.