Turn on organization-wide audit logging of control-plane actions
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Check 27 of 30: Turn on organization-wide audit logging of control-plane actions. Without audit logs there is no record of which role or setting the agent changed, or who changed the agent's access. A log kept outside the agent's reach is the base for every investigation.
The whole checklist ยท The map
Why it matters
Without audit logs there is no record of which role or setting the agent changed, or who changed the agent's access. A log kept outside the agent's reach is the base for every investigation.
How, in each cloud
- AWS
- Create an organization trail in CloudTrail.
- Google Cloud
- Rely on Admin Activity audit logs, which cannot be disabled.
- Azure
- Use the Azure Monitor activity log, which records management operations for Azure resources.
What the documentation says
- "and apply it to an organization, making it an organization trail. Organization trails log" (source)
- "You can't disable Admin Activity audit logs." (source)
- "Azure Monitor records management operations for your Azure resources through the activity log feature." (source)
- Previous: Remove the agent's identity and access when the agent is retired
- Next: Log reads and writes to the data the agent touches
Related pages
- Log reads and writes to the data the agent touches: the check, and how in AWS, Google Cloud and Azure
- Make every logged action traceable to the specific agent identity: the check, and how in AWS, Google Cloud and Azure
- Alert on denied calls and on changes to the agent's role or policies: the check, and how in AWS, Google Cloud and Azure
Sources
- docs.aws.amazon.com/awscloudtrail/latest/userguide/creating-trail-organization.h, read 10 Nov 2026
- cloud.google.com/kubernetes-engine/docs/how-to/audit-logging, read 10 Nov 2026
- learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log, read 10 Nov 2026
Last reviewed 16 Nov 2026.