Protego field desk
Security Logging and Monitoring · 18% of exam

L4. CloudTrail: Management vs Data Events & Log Integrity

Video generating

Check back soon for the video lesson on CloudTrail: Management vs Data Events & Log Integrity

Course outlineLesson 4 of 18
AWS Security Specialty Exam Prep: course overview

Why data events are not logged by default, how CloudTrail proves its own logs have not been tampered with, and how organization trails centralize auditing across every account.

Management Events vs Data Events

CloudTrail records supported API and non-API account activity. Management and data events are the key distinction in this lesson; CloudTrail also supports Insights and network activity events. Management events are control-plane operations: creating a bucket, launching an instance, modifying an IAM policy. Actions like CreateBucket and RunInstances fall here. Management events are logged by default and are visible for free in the 90-day Event History, with no trail required. Data events are object-level, data-plane operations: an S3 GetObject or PutObject call, a Lambda function Invoke. These are NOT logged by default. Enable them with event selectors on a trail or event data store, selecting the resource types and scope you need. Data events incur additional charges and can be high volume; they do not appear in Event History.

Spotting Anomalies Automatically

CloudTrail Insights, when explicitly enabled with the required event logging, baselines normal API activity and automatically flags unusual patterns, such as a spike in call volume or an unusual jump in error rates, without you writing custom detection logic. Insights is optional and incurs additional charges; enabling a trail alone does not enable Insights.

Centralizing Logs Across an Organization

An organization trail, created from the AWS Organizations management account or a registered delegated administrator account, automatically aggregates CloudTrail logs from every current and future member account into one central S3 bucket. This bucket is typically locked down and accessible only to a small security team, giving you a single, consistent audit trail across an entire multi-account environment instead of stitching together per-account trails yourself.

Proving Logs Have Not Been Tampered With

CloudTrail's log file integrity validation lets you cryptographically prove that a delivered log file has not been altered or deleted after the fact. Each log file is hashed with SHA-256, and the hashes are chained together into a digest file that is itself digitally signed by CloudTrail using a Region-specific RSA key pair. To verify a log, you recompute its hash and compare it against the signed digest chain. Enable digest delivery first, then run validation with the AWS CLI. Enabling integrity validation does not automatically validate files or prevent deletion. SSE-KMS encryption and digest signing are separate controls. This matters enormously for forensic investigations, where you may need to demonstrate in court or to an auditor that evidence was not manipulated.

Querying Logs Without Building Infrastructure

CloudTrail Lake lets you run standard SQL queries directly against your event data, without standing up your own Athena tables or S3 pipeline. Availability: CloudTrail Lake closed to new customers on May 31, 2026. Existing customers can continue using it, with critical fixes and security updates. For new implementations, AWS directs customers to CloudWatch for similar capabilities; trails and Event History remain available.
CloudTrail conceptKey fact
Management eventsControl-plane actions; 90-day regional Event History is free
Data eventsOff by default; configure selectors; additional charges
CloudTrail InsightsOpt-in anomaly detection with additional charges
Organization trailAggregates all member accounts into one central bucket
Log file integrity validationSHA-256 hashes + CloudTrail RSA-signed digest chain detects changes
CloudTrail LakeSQL queries for existing customers; closed to new customers
Exam tip: The recommended CloudTrail baseline is a multi-region trail, SSE-KMS encryption on the log bucket, and a bucket policy that denies delete permissions on the log-archive bucket, even to the security team's own day-to-day role. Logs that anyone can delete are not a reliable audit trail.

Continue Learning

Connect auditing to S3 data protection. For current exam coverage, compare these fundamentals with the SCS-C03 guide.

References

Exam Focus Points
  • ✓Management events appear in free 90-day regional Event History; trails, additional copies and other event types have separate pricing rules
  • ✓CloudTrail log file integrity validation uses a SHA-256 hash chain plus digitally signed digest files to prove logs have not been altered or deleted after delivery
  • ✓An organization trail, created from the management or registered delegated administrator account, aggregates CloudTrail logs from every member account into one central S3 bucket
  • ✓CloudTrail Insights requires explicit enablement and supporting event logging; it detects unusual API rates and has additional charges
  • ✓CloudTrail Lake supports SQL for existing customers but closed to new customers on May 31, 2026
Knowledge Check

1. A security team notices that S3 GetObject calls are not appearing in CloudTrail for a sensitive bucket. What is the most likely reason?

2. How does CloudTrail log file integrity validation help during an incident investigation?

3. What is the purpose of an AWS Organizations trail (organization trail)?