CyberKit

Cloud Audit Logs

Also called Control-Plane Logs.

Records of management-plane API activity in a cloud environment.

What it is

Cloud audit logs capture control-plane activity (the API calls that create, modify, and delete resources, along with identity and access management changes) recording who did what, when, from where, and whether it succeeded. They are the cloud equivalent of an operating system's security log for the management layer.

Why it matters

In cloud intrusions, attacker actions are largely API calls, so these logs are the primary evidence of privilege escalation, persistence, and data access at the platform level. Disabling or failing to enable them creates a blind spot that can hide an entire breach of the management plane.

In practice

An audit log entry showing an unfamiliar identity assigning itself an administrative role moments before exporting a storage bucket.

What to look for

  • IAM changes, key creation and logging changes.
  • API calls from new IPs or user agents.
  • Calls made by roles outside their normal pattern.

Common mistake

Collecting only one region. Attackers use regions you never touch.

Use it in CyberKit

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

  • Authentication Logs: Records of login attempts, successes, and failures across systems.
  • Telemetry Gap: A blind spot where the data needed to detect activity isn't collected.
  • Log Retention: How long logs are kept available before deletion or archival.

Sources