2026 Exam Guide
AWS Certified Security - Specialty Study Guide
Current exam coverage, candidate guidance, important topics, and practical preparation advice for the SCS-C03 exam.
What Is AWS Certified Security - Specialty?
AWS Certified Security - Specialty is an advanced certification for professionals who secure workloads and data on Amazon Web Services. The current SCS-C03 exam validates the ability to detect threats, respond to incidents, protect infrastructure, design identity controls, secure data, and establish governance across AWS environments. It expects candidates to connect security requirements with AWS-native controls rather than simply recognize service names.
SCS-C03 contains 65 multiple-choice or multiple-response questions and allows 170 minutes. AWS identifies 50 scored questions and 15 unscored questions. The passing score is 750 on a scaled range of 100 to 1,000. The blueprint covers Detection, Incident Response, Infrastructure Security, Identity and Access Management, Data Protection, and Security Foundations and Governance.
Current preparation should include multi-account security, centralized logging, GuardDuty, Security Hub, Inspector, Macie, CloudTrail, AWS Config, IAM Access Analyzer, Organizations, SCPs, VPC security, KMS, Secrets Manager, incident automation, and resilient forensic processes. Questions are commonly scenario-based and distinguish controls that detect, prevent, contain, or remediate a security condition.
Who Should Take This Exam?
The certification is intended for experienced security engineers, cloud security architects, incident responders, security operations professionals, and AWS engineers with substantial security responsibility. AWS targets candidates with the equivalent of three to five years securing cloud solutions and practical AWS experience.
Candidates should already understand IAM evaluation, networking, encryption, logging, monitoring, automation, and multi-account governance. It is not an entry-level AWS certification. Hands-on experience configuring organization trails, delegated security administration, key policies, cross-account roles, private connectivity, detection services, and incident-response runbooks is strongly recommended.
Exam Domains
Detection
16%Telemetry, logging, monitoring, threat detection, findings, and anomalous activity.
Incident Response
14%Investigation, containment, eradication, recovery, evidence, and automation.
Infrastructure Security
18%Network, compute, container, edge, and workload security controls.
Identity and Access Management
20%Federation, IAM policy evaluation, organizations, privileges, and access analysis.
Data Protection
18%Encryption, KMS, secrets, certificates, storage security, and data discovery.
Security Foundations and Governance
14%Multi-account governance, compliance, standards, architecture, and risk.
Common Topics Covered
- GuardDuty and Security Hub
- CloudTrail and AWS Config
- IAM policies, roles, and SCPs
- KMS key policies and grants
- VPC endpoints and network inspection
- Incident isolation and forensics
- Macie and data classification
- Secrets Manager and ACM
- Organizations and delegated administrators
- Security automation and remediation
Study Tips
Study policy evaluation deeply, including identity policies, resource policies, permission boundaries, session policies, SCPs, key policies, and explicit denies. Build multi-account labs for centralized CloudTrail, Security Hub, GuardDuty, and Config. Practice cross-account encrypted S3 access because it requires correct authorization across IAM, S3, and KMS.
For every scenario, identify whether the requirement is preventive, detective, responsive, or governance-focused. Review how to preserve evidence while isolating resources and how to automate containment without destroying forensic value. Compare overlapping services and understand their data sources, delegated-administration models, and regional behavior.
Practice Questions Overview
Certoga's SCS-C03 bank contains 200 original questions covering all six domains. The scenarios focus on realistic IAM, KMS, centralized detection, private access, incident containment, and audit-integrity decisions. Use the explanations to trace every authorization layer and understand why a technically related service may not satisfy the exact security objective.