Cloud Audit Logging
Also called Control plane logs, API activity logs.
The record of management-plane API calls made across a cloud account.
What it is
A service-generated log that records who called which management API, when, from where, and with what result, across an account or organization. It is the primary forensic timeline for cloud activity.
Why it matters
These logs are often the only durable evidence of an attacker's cloud actions, so confirming they are enabled, centralized, and tamper-resistant is one of the first things a responder checks.
In practice
Pulling the audit trail, an analyst reconstructs the full sequence from the first stolen-credential call to the attempt to disable logging itself.
What to look for
- Regions or accounts with audit logging turned off.
- StopLogging, DeleteTrail or similar calls.
- Data events not captured for sensitive storage.
Common mistake
Thinking management logs show data access. Reads of objects and secrets often need data event logging enabled separately.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Amazon GuardDuty Cloud service
AWS threat detection that analyzes CloudTrail, VPC flow logs and DNS logs.
-
Microsoft Defender for Cloud Commercial
Posture and threat protection for Azure, AWS and Google Cloud.
-
Wiz Commercial
Maps cloud resources, identities and exposures into one graph of risk.
-
Prowler Open source
An open source tool that checks cloud accounts against benchmarks such as CIS.
Read next
- Shared Responsibility Model: The split of security duties between a cloud provider and its customer.
- Cloud Persistence: Techniques that let an attacker retain cloud access across sessions.