Study guide

5.4 Edge Integrations: Managed Rule Groups, OCSF Ingestion, IoT Policies & CORS

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

5.4 Edge Integrations: Managed Rule Groups, OCSF Ingestion, IoT Policies & CORS

Key Takeaways Explain This Topic AI

AWS WAF web ACLs can include AWS managed rule groups and third-party rule groups from AWS Marketplace; test new groups by overriding rule actions to Count.

AWS WAF logging destinations must be named with the aws-waf-logs- prefix, and Firehose can forward logs to third-party SIEMs.

Security Lake ingests AWS WAF logs natively in OCSF, while third-party custom sources must write OCSF records in Parquet format.

AWS IoT Core policies with variables such as iot:Connection.Thing.ThingName scope one policy to each device's own client ID and topics.

S3 CORS configuration is not authorization; wildcard origins let any website drive cross-origin requests from a user's browser.

Last updated: September 2026

5.4 Edge Integrations: Managed Rule Groups, OCSF Ingestion, IoT Policies & CORS

SCS-C03 Skill 3.1.4 asks you to integrate AWS edge services with third-party services , for example by using third-party WAF rules and ingesting data in Open Cybersecurity Schema Framework (OCSF) format. Skill 3.1.2 also lists edge controls that don't fit neatly into CloudFront or AWS WAF alone: AWS IoT policies and Amazon S3 cross-origin resource sharing (CORS) . This section covers those integrations.

Managed Rule Groups: AWS and Third-Party

AWS WAF web ACLs can combine your own rules with managed rule groups maintained by someone else.

Rule Group Source Examples Notes

AWS Managed Rules Core rule set, Known bad inputs, SQL database, Linux and POSIX operating system, PHP and WordPress application, Amazon IP reputation list, Anonymous IP list Most are included in AWS WAF pricing

AWS Managed Rules (paid features) Bot Control, Account Takeover Prevention (ATP), Account Creation Fraud Prevention (ACFP) Extra fees; use scope-down statements to inspect only relevant requests, such as login paths

AWS Marketplace sellers Rule groups from security vendors (for example, OWASP-focused or bot-management sets) Subscribe in AWS Marketplace, then add to the web ACL; the vendor updates the rules

Operating managed rule groups well:

Test before blocking : Override a new rule group's rule actions to Count , review the WAF logs and labels, then switch to the vendor's actions.

Use labels : Managed rules add labels (for example, awswaf:managed:aws:bot-control:bot:category:... ). Later rules in the web ACL can match on labels to build logic such as "block this bot category only on the checkout path."

Control versions : AWS managed rule groups can be pinned to a static version and subscribed to SNS notifications about new versions, so updates don't surprise production.

Budget capacity : Every rule group consumes web ACL capacity units (WCUs). Vendor rule groups can't be edited, but individual rules can be overridden.

Deploy centrally : AWS Firewall Manager can push a web ACL containing AWS and Marketplace rule groups to every account in an organization.

Client Fingerprinting at the Edge

AWS WAF can match the JA3 and JA4 TLS client fingerprints of requests to CloudFront distributions and Application Load Balancers. A fingerprint identifies the TLS client software regardless of the source IP address, so a botnet rotating through thousands of IP addresses can still be blocked if its client library produces a consistent fingerprint. Combine fingerprint matches with rate-based rules and Bot Control labels rather than relying on any single signal.

Sending Edge Data to Third-Party Tools and OCSF

Edge telemetry is most useful when it reaches the tools your security operations center already uses.

AWS WAF logging destinations are a CloudWatch Logs log group, an S3 bucket, or an Amazon Data Firehose stream, and each destination name must start with aws-waf-logs- . Firehose can deliver to third-party SIEM destinations such as Splunk, Datadog, or an HTTP endpoint.

Amazon Security Lake collects AWS WAF logs as a native source and converts them to OCSF, alongside CloudTrail, VPC Flow Logs, Route 53 Resolver query logs, and Security Hub findings. Subscribers such as a SIEM receive the normalized data through S3 access or Lake Formation-based query access.

Third-party edge data , such as logs from a third-party CDN, WAF, or firewall, can be added to Security Lake as a custom source . The provider must write records in OCSF format as Apache Parquet files to the custom source's S3 location; Security Lake creates the Glue crawler and IAM role that register the data.

CloudFront standard logs can be delivered to CloudWatch Logs, Firehose, or S3, which lets the same pipelines handle CDN access logs.

Normalizing to OCSF means a detection written against src_endpoint.ip works whether the event came from AWS WAF, a VPC Flow Log, or a partner firewall.

AWS IoT Core Policies

Internet of Things devices connect to AWS IoT Core at the edge of your environment, usually over MQTT with mutual TLS and an X.509 client certificate. AWS IoT Core policies (separate from IAM policies) are attached to the device certificate, a thing group, or an Amazon Cognito identity, and they authorize MQTT actions:

  • Action Resource Type Purpose
  • iot:Connect client/<client-id> Connect with a specific MQTT client ID
  • iot:Publish topic/<topic-name> Publish to a topic
  • iot:Subscribe topicfilter/<topic-filter> Subscribe to a topic filter
  • iot:Receive topic/<topic-name> Receive messages delivered on a topic
  • The key least-privilege technique is policy variables , which scope one policy to many devices: {
  • "Version": "2012-10-17",
  • "Statement": [
  • {
  • "Effect": "Allow",
  • "Action": "iot:Connect",
  • "Resource": "arn:aws:iot:us-east-1:111122223333:client/${iot:Connection.Thing.ThingName}"
  • },
  • {
  • "Effect": "Allow",
  • "Action": "iot:Publish",
  • "Resource": "arn:aws:iot:us-east-1:111122223333:topic/devices/${iot:Connection.Thing.ThingName}/telemetry"
  • }
  • ]
  • }

Each device may connect only with its own thing name as the client ID and publish only to its own telemetry topic, so one stolen certificate can't impersonate other devices. AWS IoT Device Defender audits for overly permissive policies, shared certificates, and revoked or expiring certificates, and its detect feature flags unusual device behavior.

Amazon S3 Cross-Origin Resource Sharing (CORS)

Browsers block a web page on one origin from reading responses from another origin unless the response includes CORS headers. An S3 CORS configuration lists rules with AllowedOrigins , AllowedMethods , AllowedHeaders , ExposeHeaders , and MaxAgeSeconds .

Two security points matter for the exam:

CORS is not access control. It tells browsers which cross-origin reads to allow; it doesn't stop a direct request from a script or the AWS CLI. Protect the data with bucket policies, Block Public Access, CloudFront origin access control, and presigned URLs.

Keep origins specific. "AllowedOrigins": ["*"] combined with methods such as PUT lets any website drive a user's browser to upload using the user's own presigned URLs or cookies. List exact origins, such as https://app.example.com .

When CloudFront fronts the bucket, forward the Origin header through an origin request policy (or a managed CORS policy) and, if needed, add CORS headers with a response headers policy. Otherwise the cached response may not include the headers the browser expects.

Specialty Exam Pitfalls

Blocking with an untested vendor rule group : Start new managed rule groups in Count mode to avoid blocking legitimate traffic.

Wrong WAF log destination name : Log groups, buckets, and Firehose streams for AWS WAF logs must be named with the aws-waf-logs- prefix.

Custom Security Lake sources in raw JSON : Custom sources must provide OCSF data in Parquet.

One broad IoT policy for all devices : Use policy variables so each certificate can act only as its own thing.

Treating CORS as authorization : CORS relaxes browser restrictions; it never protects data from direct requests.

Loading diagram... Edge Integrations with Third-Party Tools, IoT, and OCSF