Study guide
1.3 AWS Security Hub & Automated Conformance Assessment
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
1.3 AWS Security Hub & Automated Conformance Assessment
Key Takeaways Explain This Topic AI
AWS Security Hub CSPM (the original Security Hub, renamed in 2025) provides posture management and finding aggregation, normalizing findings from AWS and third-party tools into the AWS Security Finding Format (ASFF).
Security Hub CSPM continuously evaluates resources against standards including AWS Foundational Security Best Practices (FSBP), CIS AWS Foundations Benchmark, PCI DSS, and NIST SP 800-53.
Security scores represent the percentage of passed controls relative to total enabled controls, weighted by control requirements.
Cross-Region finding aggregation designates an aggregation Region that centralizes findings, compliance statuses, and workflow updates from all linked spoke Regions into a single pane of glass.
Automated remediation leverages EventBridge rules matching ASFF finding schemas to trigger AWS Systems Manager Automation runbooks or Lambda functions.
Last updated: September 2026
1.3 AWS Security Hub & Automated Conformance Assessment
Enterprise cloud environments generate security telemetry across dozens of specialized tools, including Amazon GuardDuty, Amazon Inspector, Amazon Macie, AWS IAM Access Analyzer, and third-party vulnerability scanners. Without a centralized aggregation layer, security teams face fragmented dashboards, inconsistent alert formats, and manual compliance audits. AWS Security Hub resolves this operational challenge as a comprehensive Cloud Security Posture Management (CSPM) service that normalizes, correlates, and prioritizes findings while continuously assessing adherence to industry compliance standards.
Note
2025 naming change. AWS renamed the original service AWS Security Hub CSPM and launched a new, unified AWS Security Hub that correlates signals from GuardDuty, Inspector, Macie, and Security Hub CSPM into exposures and threats. Security Hub CSPM still runs the standards, controls, and security scores described here, and it still uses ASFF. The SCS-C03 outline removed ASFF as a named topic, so expect questions about what the service does (aggregation, standards, automation) rather than ASFF field trivia. This section uses "Security Hub" for the CSPM capabilities.
Centralized Posture Management & The ASFF Schema
Security Hub acts as a single pane of glass for security posture. It ingests findings from native AWS services, third-party security products, and custom internal scanners. The foundational mechanism enabling this integration is the AWS Security Finding Format (ASFF) .
Loading diagram...
The AWS Security Finding Format (ASFF)
Before ASFF, each security tool emitted telemetry with unique JSON keys (e.g., one tool used severity_level , another used priority , a third used an integer scale). ASFF enforces a strict, consistent JSON syntax across all finding providers: {
"SchemaVersion": "2018-10-08",
"Id": "arn:aws:securityhub:us-east-1:123456789012:subscription/aws-foundational-security-best-practices/v/1.0.0/S3.1/finding/a1b2c3d4",
- "ProductArn": "arn:aws:securityhub:us-east-1::product/aws/securityhub",
- "GeneratorId": "aws-foundational-security-best-practices/v/1.0.0/S3.1",
- "AwsAccountId": "123456789012",
- "Types": [
- "Software and Configuration Checks/Industry and Regulatory Standards/AWS-Foundational-Security-Best-Practices"
- ],
- "CreatedAt": "2026-09-29T04:15:30Z",
- "UpdatedAt": "2026-09-29T04:15:30Z",
- "Severity": {
- "Label": "CRITICAL",
- "Normalized": 90
- },
- "Title": "S3.1 S3 Block Public Access setting should be enabled",
"Description": "This AWS control checks whether S3 buckets have bucket-level Block Public Access settings enabled.",
- "Resources": [
- {
- "Type": "AwsS3Bucket",
- "Id": "arn:aws:s3:::customer-confidential-financial-records",
- "Partition": "aws",
- "Region": "us-east-1"
- }
- ],
- "Compliance": {
- "Status": "FAILED",
- "SecurityControlId": "S3.1"
- },
- "Workflow": {
- "Status": "NEW"
- },
- "RecordState": "ACTIVE"
- }
- Core ASFF Attributes Worth Recognizing
ProductArn : The ARN of the product that created the finding (e.g., arn:aws:securityhub:... for native controls, or a partner ARN).
GeneratorId : The specific security rule, control, or detector that generated the finding.
Severity.Label : Standardized string classification: INFORMATIONAL , LOW , MEDIUM , HIGH , or CRITICAL .
Severity.Normalized : An integer between 0 and 100 that normalizes disparate third-party scoring systems into a universal baseline.
Compliance.Status : The compliance state of the evaluated resource: PASSED , WARNING , FAILED , or NOT_AVAILABLE .
Workflow.Status : Tracking the lifecycle of a finding: NEW , NOTIFIED , RESOLVED , or SUPPRESSED .
RecordState : Indicates whether the finding is ACTIVE (still present) or ARCHIVED (resolved or outdated).
Supported Compliance Standards & Security Score Mechanics
Security Hub continuously assesses resource configurations against enabled regulatory and industry benchmarks.
Major Compliance Frameworks
AWS Foundational Security Best Practices (FSBP) : AWS-curated security controls representing AWS security architects' baseline recommendations. Covers IAM, data protection, network hardening, logging, and encryption across all primary AWS services. Updated continuously by AWS.
CIS AWS Foundations Benchmark : Industry-standard configuration guidelines developed by the Center for Internet Security (CIS). Covers identity, logging, monitoring, and networking across multiple versions (v1.2.0, v1.4.0, v3.0.0, and v5.0.0).
Payment Card Industry Data Security Standard (PCI DSS) : Specific controls for workloads handling, storing, or transmitting cardholder data (versions v3.2.1 and v4.0).
NIST SP 800-53 Rev. 5 : Comprehensive federal information security controls catalog required for United States government agencies and regulated contractors.
Underlying Evaluation Engine: AWS Config Dependency
Security Hub controls do not perform direct API polling against your infrastructure. Instead, Security Hub relies on AWS Config managed rules as its underlying configuration evaluation engine.
Exam Trap Alert : For Security Hub compliance standards to generate findings and calculate security scores, AWS Config resource recording must be enabled in the target account and Region. If AWS Config recording is disabled or configured to record only a subset of resource types, Security Hub controls will display a compliance status of NOT_AVAILABLE and the security score will be incomplete.
Security Score Calculation
Security Hub calculates a quantitative Security Score (expressed as a percentage from 0% to 100%) for each enabled standard and a consolidated security score across all standards: Security Score = (Number of Passed Controls / Total Number of Enabled Controls) * 100
Crucial operational nuances govern this calculation:
Consolidated Controls View : Many controls are shared across standards (e.g., enforcing S3 bucket encryption is required by FSBP, CIS, and PCI DSS). Under the Consolidated Controls View, Security Hub evaluates the control once; passing or failing it updates all associated standards simultaneously.
Disabled Controls vs Suppressed Findings : If an organization intentionally disables a control (e.g., RDS multi-AZ is not required in development sandboxes), the control is removed from the denominator and does not penalize the security score. If a failed control finding is set to Workflow.Status = SUPPRESSED , the control is treated as non-breaching and does not degrade the score, while preserving an audit record of the business exception.
Cross-Region Finding Aggregation Architecture
In an enterprise environment operating across global AWS Regions, managing findings locally in each individual Region is operationally unsustainable. Security Hub provides Cross-Region Finding Aggregation to establish a single pane of glass.
Hub-and-Spoke Aggregation Mechanics
Designate an Aggregation Region : The security engineering team selects one primary Region (the Hub or Aggregation Region , e.g., us-east-1 ) in the delegated administrator account.
Link Spoke Regions : The administrator links all active Regions (the Spokes ) to the aggregation Region. Linking can include all current Regions and automatically opt into any newly enabled future Regions.
Continuous Asynchronous Replication : Findings, compliance statuses, and security scores generated in spoke Regions are automatically replicated asynchronously to the aggregation Region.
Bi-Directional Status Synchronization : If a security analyst in the aggregation Region updates a finding's workflow status (e.g., changing Workflow.Status from NEW to RESOLVED or adding an audit note), the change is automatically synchronized back to the originating spoke Region.
Centralized EventBridge Automation : Because all findings from all linked Regions flow into the aggregation Region, security teams configure their primary Amazon EventBridge routing rules and automated remediation pipelines solely in the aggregation Region , eliminating the need to duplicate Lambda remediation functions and EventBridge rules in every spoke Region.
Automated Remediation with AWS Config & Systems Manager
Security Hub provides two remediation paradigms: automated real-time remediation and user-driven custom actions .
Automated Real-Time Remediation Flow
A resource configuration change breaches a security control (e.g., an S3 bucket is created with public read access).
AWS Config detects the configuration drift and emits a compliance state change to Security Hub.
Security Hub generates an ASFF finding with Compliance.Status = FAILED and Severity.Label = HIGH or CRITICAL .
Security Hub emits the finding to the Amazon EventBridge default event bus as a Security Hub Findings - Imported event.
An EventBridge rule matches the failed control ID and triggers an AWS Systems Manager (SSM) Automation Document (e.g., AWSConfigRemediation-ConfigureS3BucketPublicAccessBlock or a custom runbook).
The SSM Automation runbook assumes an IAM remediation role, applies S3 Block Public Access, and updates the finding's Workflow.Status to RESOLVED .
Custom Actions for Human-in-the-Loop Triage
Not all remediation actions can be fully automated without risking application availability (e.g., isolating a production database instance). For high-impact resources, Security Hub supports Custom Actions :
An administrator creates a custom action in Security Hub (e.g., IsolateCompromisedEC2Instance ), generating a unique Custom Action ARN.
An analyst reviewing findings in the Security Hub console selects one or more findings and clicks the custom action from the Actions dropdown.
Security Hub publishes a Security Hub Findings - Custom Action event to EventBridge containing the selected finding payloads.
EventBridge routes the event to an automated Step Functions state machine or Lambda function to execute the controlled quarantine workflow.
Scheduled Assessments: Conformance Packs, Security Hub CSPM & State Manager
Skill 1.1.5 asks you to automate regular assessments and investigations rather than one-off checks. Three services cover different layers:
Mechanism What it assesses How it runs on a schedule Typical exam use
AWS Config conformance pack Resource configuration against a packaged set of Config rules (for example, an operational best-practices template) Change-triggered and periodic Config rules; organization conformance packs deploy to every member account "Continuously evaluate all accounts against a framework and remediate automatically"
Security Hub CSPM standards Controls such as FSBP or CIS, scored per account and Region Change-triggered or periodic controls that Security Hub CSPM runs through service-linked Config rules "Give me a security score and prioritized failed controls across the organization"
Systems Manager State Manager The state inside managed nodes (agents installed, configuration files, inventory collected) Associations that apply a document on a cron or rate schedule and report compliance "Every 12 hours, confirm the EDR agent is installed and running, and reinstall it if missing"
State Manager is the piece candidates forget. An association binds an SSM document (for example, AWS-GatherSoftwareInventory , AWS-RunShellScript , or an Automation runbook) to targets selected by tag, and re-applies it on a schedule. Its compliance results appear in Systems Manager Compliance, so an EventBridge rule or a Security Hub CSPM integration can alert when a node drifts. Use it for host-level assessments that Config rules cannot see, such as a disabled auditd service or a missing CloudWatch agent configuration.
Specialty Exam Pitfalls & Governance Strategies
Security Hub Does Not Auto-Enable AWS Config : A frequent misunderstanding is believing that enabling Security Hub automatically activates AWS Config. Security Hub checks Config, but if Config recording has not been initialized, Security Hub cannot evaluate compliance. You must enable Config in every account and Region.
Custom Actions Require Explicit Invocation : Custom actions are never triggered automatically by incoming findings. They only fire when an operator selects findings in the console and chooses the custom action. For automated remediation without human intervention, use EventBridge rules matching Security Hub Findings - Imported .
Finding Ingestion vs Security Score Impact : Third-party findings and GuardDuty threat findings ingested into Security Hub appear in the findings dashboard, but they do not affect the compliance security score. The security score is derived exclusively from enabled compliance standard controls (FSBP, CIS, PCI DSS, NIST).
AWS Organizations Delegated Admin Boundary : You cannot designate an account as the Security Hub Delegated Administrator unless it is first registered as a member account within AWS Organizations. The Organizations management account should only configure delegation; day-to-day operations must reside in the designated security tooling account.