Log reads and writes to the data the agent touches
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Check 28 of 30: Log reads and writes to the data the agent touches. Control-plane logs show configuration changes, not which records the agent read. Data-level logs are what show whether the agent touched something it should not have. In AWS: Configure CloudTrail data events, which trails do not log by default.
The whole checklist ยท The map
Why it matters
Control-plane logs show configuration changes, not which records the agent read. Data-level logs are what show whether the agent touched something it should not have.
How, in each cloud
- AWS
- Configure CloudTrail data events, which trails do not log by default.
- Google Cloud
- Enable Data Access audit logs, which are disabled by default for most services.
- Azure
- Create a diagnostic setting to collect resource logs, which are not collected until you do.
What the documentation says
- "By default, trails and event data stores do not log data events." (source)
- "Data Access audit logs are disabled by default for all services except some" (source)
- "Resource logs aren't collected and stored until you create a diagnostic setting" (source)
- Previous: Turn on organization-wide audit logging of control-plane actions
- Next: Make every logged action traceable to the specific agent identity
Related pages
- 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
- Give each agent its own role or service account, not a shared one: the check, and how in AWS, Google Cloud and Azure
Sources
- docs.aws.amazon.com/awscloudtrail/latest/userguide/logging-data-events-with-clou, read 10 Nov 2026
- cloud.google.com/logging/docs/audit/configure-data-access, read 10 Nov 2026
- learn.microsoft.com/en-us/azure/storage/blobs/monitor-blob-storage, read 10 Nov 2026
Last reviewed 16 Nov 2026.