Study guide

2.5 Analyzing, Normalizing & Correlating Security Logs

AWS Certified Security – Specialty SCS-C03

Track your progress as you read

Finished sections get a check mark.

1 Chapter 0: Getting Started with the SCS-C03 Exam

0.1 SCS-C03 Exam Format, Domains & Study Strategy

2 Chapter 1: Security Monitoring, Alerting & Threat Detection Services

1.1 Workload Monitoring & Health Check Strategies 1.2 Amazon GuardDuty Architecture & Finding Types 1.3 AWS Security Hub & Automated Conformance Assessment 1.4 Amazon Macie & Automated Data Classification

3 Chapter 2: Enterprise Logging Architecture & Analysis

2.1 Multi-Account CloudTrail & Organization Trails 2.2 Amazon Security Lake & OCSF Log Normalization 2.3 Network Telemetry: VPC Flow Logs & Route 53 Resolver Logs 2.4 Troubleshooting Security Telemetry & Log Ingestion 2.5 Analyzing, Normalizing & Correlating Security Logs

4 Chapter 3: Incident Readiness, Response Planning & Automated Runbooks

3.1 Incident Response Planning & Blast Radius Mitigation 3.2 Testing & Validating Incident Response Plans 3.3 Automated Incident Remediation with EventBridge & Step Functions 3.4 Systems Manager OpsCenter & Incident Manager Runbooks

5 Chapter 4: Digital Forensics, Evidence Preservation & Root Cause Analysis

4.1 Forensic Artifact Capture & Chain of Custody 4.2 Threat Containment & Network Quarantine Techniques 4.3 Correlating Events & Root Cause Analysis with Amazon Detective

6 Chapter 5: Edge Protection, WAF & DDoS Mitigation

5.1 CloudFront Security Headers & Origin Access Control 5.2 AWS WAF Architecture & Advanced Rule Sets 5.3 AWS Shield Advanced & DDoS Defense Architectures 5.4 Edge Integrations: Managed Rule Groups, OCSF Ingestion, IoT Policies & CORS

7 Chapter 6: Compute Workload Hardening, Vulnerability Management & GenAI Security

6.1 Golden AMIs & Container Image Hardening Pipelines 6.2 Amazon Inspector Vulnerability Management & Patch Automation 6.3 Generative AI Security: Amazon Bedrock Guardrails & Model Protection 6.4 Instance Profiles, Service Roles & Execution Roles for Compute 6.5 Secure Administrative Access: Session Manager & EC2 Instance Connect

8 Chapter 7: Network Security, Segmentation, Private Connectivity & Encryption in Transit

7.1 Layered Traffic Filtering: SGs, NACLs & AWS Network Firewall 7.2 Hybrid Connectivity Security: VPN, Direct Connect & MACsec 7.3 Zero-Trust Access & Network Access Analysis 7.4 Enforcing Encryption in Transit: ELB Security Policies, TLS & HTTPS-Only Access 7.5 Private Access: VPC Endpoints, PrivateLink, Client VPN & Verified Access 7.6 Inter-Resource Encryption in Transit: Nitro, EMR, EKS & SageMaker AI

9 Chapter 8: Enterprise Authentication, Federation & Directory Services

8.1 AWS IAM Identity Center & Enterprise IdP Integration 8.2 Amazon Cognito User Pools & Identity Pools 8.3 AWS Security Token Service (STS) & Temporary Credential Workflows 8.4 Troubleshooting Identity & Authentication Failures

10 Chapter 9: Advanced Authorization Architecture & Policy Evaluation

9.1 Complete AWS Policy Evaluation Logic & Decision Flow 9.2 Permission Boundaries & Safe Admin Delegation 9.3 Attribute-Based Access Control (ABAC) with IAM Tags

11 Chapter 10: Least Privilege, Policy Validation & External Access Auditing

10.1 IAM Roles Anywhere & Amazon Verified Permissions 10.2 Auditing External & Unused Access with IAM Access Analyzer 10.3 Analyzing Authorization Failures & Policy Simulation

12 Chapter 11: Cryptographic Services: KMS Architecture & Key Governance

11.1 AWS KMS Architecture, Key Policies & Key Types 11.2 KMS Grants, Encryption Context & Multi-Region Keys 11.3 Imported Key Material (BYOK) & CloudHSM Key Stores

13 Chapter 12: Secrets Management, Sensitive Data Masking & PKI

12.1 AWS Secrets Manager & Systems Manager Parameter Store 12.2 Sensitive Data Masking in Telemetry & Messaging 12.3 AWS Certificate Manager (ACM) & Private CA Architecture

14 Chapter 13: Storage Encryption, Integrity, Lifecycle & Backup Protection

13.1 S3 Encryption Modes & S3 Bucket Keys 13.2 Data Integrity Protection: Object Lock, Vault Lock & Code Signing 13.3 Secure Data Lifecycle, Cross-Account Replication & Backup Vault Lock 13.4 Lifecycle, Backup & Secure Replication Beyond S3: EFS, FSx, DLM, DataSync & Air-Gapped Vaults

15 Chapter 14: Multi-Account Architecture, Organizations & Control Tower Governance

14.1 AWS Organizations Structure, Hierarchy & Resource Control 14.2 AWS Control Tower Landing Zone & Guardrail Framework 14.3 Delegated Administrator Architecture & Root User Governance 14.4 Centralized Resource Sharing with RAM & Service Catalog

16 Chapter 15: Compliance Automation, Infrastructure as Code Security & Auditing

15.1 Infrastructure as Code Security & Multi-Account Deployment 15.2 AWS Config, Conformance Packs & Automated Remediation 15.3 Audit Evidence Collection & Well-Architected Security Reviews

2.5 Analyzing, Normalizing & Correlating Security Logs

Key Takeaways Explain This Topic AI

CloudWatch Logs Insights queries only CloudWatch Logs data, using the Logs Insights query language, OpenSearch PPL, or SQL, and charges by data scanned.

Amazon Athena queries CloudTrail, VPC Flow Logs, ALB, WAF, and Security Lake data in S3 with SQL; partition projection keeps investigations fast and inexpensive.

Security Hub CSPM insights group findings by an attribute such as resource or account to prioritize remediation.

Lambda functions, invoked through subscription filters or Firehose transformations, parse, enrich, and normalize logs, ideally to OCSF.

OpenSearch Service Security Analytics uses Sigma-rule detectors and correlation rules, and Amazon Managed Grafana provides shared dashboards with IAM Identity Center sign-in.

Last updated: September 2026

2.5 Analyzing, Normalizing & Correlating Security Logs

Collecting logs is only half of detection. SCS-C03 Skills 1.2.4 and 1.2.5 test whether you can query logs to answer an investigation question and normalize, parse, and correlate logs from different sources. The exam names CloudWatch Logs Insights, Amazon Athena, Security Hub findings, Amazon OpenSearch Service, AWS Lambda, and Amazon Managed Grafana. The skill is choosing the right tool for where the data lives, how fast you need answers, and who will look at them.

Choosing an Analysis Tool

Tool Best For Data Location Query Style

CloudWatch Logs Insights Fast, ad hoc queries on recent operational and security logs CloudWatch Logs log groups Logs Insights query language, OpenSearch PPL, or SQL

Amazon Athena Large historical investigations on logs stored in Amazon S3 S3 (CloudTrail, VPC Flow Logs, ALB, CloudFront, WAF logs, Security Lake) Standard SQL, pay per data scanned

Security Hub CSPM insights Grouping and prioritizing findings Findings from GuardDuty, Inspector, Macie, Config, and partners Filters plus a group-by attribute

Amazon OpenSearch Service Near real-time search, dashboards, and correlation at scale OpenSearch indexes, or direct query of S3, CloudWatch Logs, and Security Lake Query DSL, PPL, SQL, Security Analytics detectors

AWS Lambda Parsing, enriching, and normalizing records in flight Subscription filters, Firehose transformations, S3 events Your code

Amazon Managed Grafana Shared dashboards across many data sources CloudWatch, OpenSearch, Athena, Prometheus, and others Data source query editors

CloudWatch Logs Insights

Logs Insights runs interactive queries across one or more log groups, which makes it the fastest option when CloudTrail, VPC Flow Logs, Route 53 Resolver query logs, Lambda logs, or application logs already stream to CloudWatch Logs. Queries can be written in the Logs Insights query language, OpenSearch Piped Processing Language (PPL), or SQL. You pay for the data scanned, so narrow the time range and log groups first.

A typical investigation query finds which principals are generating access denials in a CloudTrail log group: fields @timestamp, eventSource, eventName, userIdentity.arn, sourceIPAddress

  • | filter errorCode = "AccessDenied" or errorCode = "UnauthorizedOperation"
  • | stats count(*) as denials by userIdentity.arn, eventName
  • | sort denials desc
  • | limit 20

Useful features include saved queries, adding query results to CloudWatch dashboards, and the pattern command, which clusters similar log lines so unusual messages stand out. Logs Insights only sees data in CloudWatch Logs, so logs that go straight to S3 need Athena instead.

Amazon Athena for Logs in S3

Organization trails, VPC Flow Logs, ALB and CloudFront access logs, and AWS WAF logs commonly land in a central log archive bucket. Athena queries them in place with SQL. Two practices keep investigations fast and affordable:

Partition the tables (by account, Region, and date) and use partition projection , so a query for one day in one account doesn't scan years of logs.

Use workgroups to enforce an encrypted query-results location, per-query data-scan limits, and separate access for the security team. SELECT eventtime, useridentity.arn, eventname, sourceipaddress

  • FROM cloudtrail_logs
  • WHERE eventsource = 'iam.amazonaws.com'
  • AND eventname IN ('CreateAccessKey', 'AttachUserPolicy', 'PutUserPolicy')
  • AND timestamp BETWEEN '2026/09/01' AND '2026/09/07'
  • ORDER BY eventtime;

Here timestamp is the partition column that CloudTrail's generated table uses. Amazon Security Lake stores normalized OCSF data in S3 and registers it in the AWS Glue Data Catalog, so a subscriber with query access can run the same kind of SQL across CloudTrail, VPC Flow Logs, Route 53, and Security Hub data at once.

Security Hub CSPM Findings as an Analysis Source

Security Hub CSPM collects findings from GuardDuty, Inspector, Macie, IAM Access Analyzer, AWS Config, and partner products. Insights group related findings by an attribute, such as resource ID or AWS account, so you can see, for example, which EC2 instances have the most critical findings. With cross-Region aggregation and a delegated administrator, one account can analyze findings for the whole organization. Findings also flow to Amazon EventBridge for automated response and can be sent to Security Lake for long-term SQL analysis.

Normalizing, Parsing & Correlating

Logs from different sources use different field names, time formats, and identifiers. Correlation needs a common shape.

OCSF normalization : Security Lake converts supported AWS sources to the Open Cybersecurity Schema Framework automatically. Custom sources must be written as OCSF records in Parquet format.

Lambda transformation : A CloudWatch Logs subscription filter can send events to Lambda, or an Amazon Data Firehose stream can invoke Lambda to transform records before delivery. Typical jobs include parsing an application's text log into JSON, converting timestamps to UTC, adding account names or asset owners, and mapping fields to OCSF. Send failed records to a dead-letter destination so parsing errors don't silently drop evidence.

Amazon OpenSearch Service : OpenSearch Ingestion pipelines load logs from S3, Security Lake, or HTTP sources. The Security Analytics feature applies detectors built from Sigma rules to log types such as CloudTrail, VPC Flow Logs, and DNS, and correlation rules link findings across log types (for example, a suspicious DNS query followed by an outbound connection from the same host). Direct query (zero-ETL) integrations can also query data in S3, CloudWatch Logs, and Security Lake without copying it into an index. Protect the domain with VPC access, fine-grained access control, and encryption.

Amazon Managed Grafana : A managed Grafana workspace builds shared dashboards over CloudWatch, OpenSearch, Athena, and other data sources. Users sign in through IAM Identity Center or SAML, and the workspace uses an IAM role to read each data source, so dashboards can span accounts without handing out console access.

Specialty Exam Pitfalls

Choosing Logs Insights for data in S3 : Logs Insights queries CloudWatch Logs only. For an organization trail delivered only to S3, use Athena or Security Lake.

Unpartitioned Athena tables : Full-table scans over years of CloudTrail logs are slow and expensive; partition projection limits the scan.

Correlating without normalization : Joining events on inconsistent field names or time zones produces false conclusions. Normalize to OCSF or a common schema first.

Treating dashboards as detection : Grafana and OpenSearch dashboards show data; alerts, detectors, or EventBridge rules are what notify responders.

Loading diagram... Security Log Analysis and Correlation Pipeline