Audit Logging Fundamentals
What you'll learn: How audit logs capture the "who, what, when, and where" of system activity to support compliance tracking and security investigation.
What Are Audit Logs?
Audit logs are immutable records of events that occur within your cloud infrastructure and applications. Think of them as a detailed security camera feed for your systems—capturing every significant action so you can answer critical questions during compliance audits or security investigations.
Unlike application logs that track performance and debugging information, audit logs specifically record security-relevant events: who accessed what resource, when they did it, where they connected from, and whether the action succeeded or failed.
The Four Pillars of Audit Logging
Every useful audit log entry should answer these questions:
- Who: Which user, service account, or system initiated the action? (identity/principal)
- What: What operation was performed? (read, write, delete, configuration change)
- When: Precise timestamp of the event (with timezone and millisecond accuracy)
- Where: Source location (IP address, region, service endpoint)
Many frameworks add a fifth element: Why (the outcome—success or failure, with error codes if applicable).
Why Audit Logs Matter
For compliance frameworks like SOC 2, ISO 27001, and PCI DSS, audit logs provide evidence that security controls are functioning. They demonstrate that only authorized personnel accessed sensitive data, that configuration changes followed change management processes, and that security incidents can be investigated.
Without comprehensive audit logs, you cannot prove compliance—even if your controls are perfect.
Key Takeaway: Audit logs are immutable records capturing who performed what action, when, and where—forming the evidentiary foundation for compliance validation and security forensics.