Skip to content

About

Free SCS-C03 study guide: the full AWS Certified Security – Specialty exam blueprint as a checklist, key facts per topic, and worked sample questions.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

Repository files navigation

SCS-C03 Study Guide: AWS Certified Security – Specialty

A free, open study guide for the AWS Certified Security – Specialty (SCS-C03) exam: revision notes for every domain, side-by-side comparisons of commonly confused services, a glossary, 20 worked sample questions, and the official syllabus as a checklist with a full free lesson for every topic.

Maintained by SaveMyCert, where you can read every lesson free, practice with explained questions and take timed mock exams.

Contents

Exam at a glance

Exam code SCS-C03
Level Specialty
Questions 65
Time limit 170 min
Passing score 750 / 1000
Format Multiple choice & more
Exam fee $300
Valid for 3 years

Exam details change. Always confirm them in the official AWS Certified Security – Specialty (SCS-C03) exam guide from Amazon Web Services.

Exam domains

# Domain Weight Topics
1 Detection 16% 3
2 Incident Response 14% 2
3 Infrastructure Security 18% 3
4 Identity and Access Management 20% 2
5 Data Protection 18% 3
6 Security Foundations and Governance 14% 3

That is 6 domains and 16 topics. Spend your time in proportion to the weights: the heaviest domain decides more of your score than the lightest.

What is in this repo

File What it gives you
Domain 1 notes Detection: condensed revision notes per topic
Domain 2 notes Incident Response: condensed revision notes per topic
Domain 3 notes Infrastructure Security: condensed revision notes per topic
Domain 4 notes Identity and Access Management: condensed revision notes per topic
Domain 5 notes Data Protection: condensed revision notes per topic
Domain 6 notes Security Foundations and Governance: condensed revision notes per topic
Commonly confused services Side-by-side tables of the services questions set against each other
Glossary Every in-scope term and service in one sentence
Sample questions 20 worked questions with answers and reasoning
Exam-day guide Booking, testing options, scoring, results and retakes

Syllabus checklist

Tick each topic off once you can explain it without notes. The "Must know" facts are the ones questions turn on. Each lesson link goes to the complete, free lesson.

Domain 1: Detection

Weight: 16%. Designing monitoring, alerting, and logging solutions across accounts and organizations, and troubleshooting them when they break.

📝 Revision notes: Domain 1: Detection

  • 1 Design and implement monitoring and alerting solutions for an AWS account or organization
    1 (SCS-C03). Analyzing workloads to determine monitoring requirements; designing and implementing workload monitoring strategies (e.g. resource health checks); aggregating security and monitoring events; creating metrics, alerts, and dashboards to detect anomalous data and events (Amazon GuardDuty, Amazon Security Lake, AWS Security Hub, Amazon Macie); creating and managing automations for regular assessments and investigations (AWS Config conformance packs, Security Hub, Systems Manager State Manager).
    • 📖 Lesson: Designing Security Monitoring and Alerting Across an AWS Organization
    • Must know: Security Hub CSPM with a delegated administrator and cross-Region aggregation gives one view of findings: member findings reach the administrator account and linked-Region findings reach the home Region.
    • Must know: Central configuration lets the delegated administrator, from the home Region, apply policies to the root, OUs or accounts. Children inherit from the nearest parent, and a self-managed OU passes self-management to everything under it.
  • 1 Design and implement logging solutions
    2 (SCS-C03). Identifying sources for log ingestion and storage; configuring logging for AWS services and applications (an organization CloudTrail trail, a dedicated CloudWatch logging account, the CloudWatch Logs agent); implementing log storage and log data lakes (Security Lake) and integrating with third-party security tools; analyzing logs with AWS services (CloudWatch Logs Insights, Amazon Athena, Security Hub findings); normalizing, parsing, and correlating logs (Amazon OpenSearch Service, AWS Lambda, Amazon Managed Grafana); configuring appropriate log sources based on network design, threats, and attacks (VPC Flow Logs, transit gateway flow logs, Route 53 Resolver logs).
    • 📖 Lesson: Designing Security Logging Solutions: CloudTrail, Flow Logs, Central Archives
    • Must know: An organization trail from the management account logs every member automatically, and member accounts cannot modify, stop, or delete it — the answer to tamper-resistant org-wide logging.
    • Must know: Management events record the control plane and are on by default; data events (S3 objects, Lambda invokes) are high-volume, off by default, scoped with event selectors — and never appear in the 90-day event history.
  • 1 Troubleshoot security monitoring, logging, and alerting solutions
    3 (SCS-C03). Analyzing the functionality, permissions, and configuration of resources (Lambda function logging, API Gateway logging, health checks, CloudFront logging); remediating misconfiguration of resources (troubleshooting CloudWatch Agent configurations, troubleshooting missing logs).
    • 📖 Lesson: Troubleshooting Security Monitoring, Logging, and Alerting on AWS
    • Must know: Triage every broken pipeline in order — source, delivery, destination permissions, consumer — because downstream stages fail silently with no error anywhere.
    • Must know: IsLogging true does not mean delivery works: read LatestDeliveryError for S3 files (and the digest, notification and CloudWatch Logs error fields for their paths), then the bucket policy and KMS key policy for cloudtrail.amazonaws.com. CloudTrail retries failed deliveries for up to 30 days.

Domain 2: Incident Response

Weight: 14%. Designing and testing incident response plans, and responding to security events with containment, forensics, and root cause analysis.

📝 Revision notes: Domain 2: Incident Response

  • 2 Design and test an incident response plan
    1 (SCS-C03). Designing and implementing response plans and runbooks (Systems Manager OpsCenter, Amazon SageMaker AI notebooks); configuring services to be prepared for incidents (provisioning access, deploying security tools, minimizing the blast radius, AWS Shield Advanced protections); testing and validating incident response plan effectiveness (AWS Fault Injection Service, AWS Resilience Hub); automatic incident remediation (Systems Manager, Automated Forensics Orchestrator for Amazon EC2, AWS Step Functions, Amazon Application Recovery Controller, Lambda functions).
    • 📖 Lesson: Design and Test an AWS Incident Response Plan (SCS-C03)
    • Must know: Pre-provision a scoped IR role in every account, protect it with an SCP, and remember a chained AssumeRole above one hour fails.
    • Must know: Break-glass must not depend on the failed identity provider: hardware-MFA IAM users in the security account, credentials out of band, an alarm on every sign-in, and SCP exceptions that name the role ARN.
  • 2 Respond to security events
    2 (SCS-C03). Capturing and storing system and application logs as forensic artifacts; searching and correlating logs for security events across applications and AWS services; validating findings from AWS security services to assess the scope and impact of an event; containing and eradicating threats and recovering resources (network containment controls, restoring backups); root cause analysis methods (Amazon Detective).
    • 📖 Lesson: Responding to AWS Security Events: Compromised EC2, Credentials, and S3
    • Must know: Validate first, then contain, preserve, eradicate and recover — in that order; suppress a proven-benign finding only for the validated resource.
    • Must know: Tracked connections survive security-group changes; untracked flows (all-addresses rule plus all-ports return rule) drop at once. A narrow network ACL deny or the two-step security group swap cuts a live session; idle timeouts never do.

Domain 3: Infrastructure Security

Weight: 18%. Security controls for network edge services, compute workloads, and network traffic — from WAF rules to hardened AMIs to segmentation.

📝 Revision notes: Domain 3: Infrastructure Security

  • 3 Design, implement, and troubleshoot security controls for network edge services
    1 (SCS-C03). Defining and selecting edge security strategies based on anticipated threats and attacks; implementing network edge protection (CloudFront headers, AWS WAF, AWS IoT policies, OWASP Top 10 protections, Amazon S3 CORS, Shield Advanced); designing edge controls and rules from requirements (geography, geolocation, rate limiting, client fingerprinting); configuring integrations with edge and third-party services (ingesting data in Open Cybersecurity Schema Framework [OCSF] format, third-party WAF rules).
    • 📖 Lesson: Edge Security on AWS: WAF, Shield, and CloudFront as Controls
    • Must know: Match the control to the layer: Shield for L3/4 floods, WAF rate-based rules and the Anti-DDoS managed rule group for L7 floods, managed rule groups for exploits, Bot Control for automation — and put CloudFront in front of anything WAF cannot attach to.
    • Must know: Web ACLs attach to CloudFront and Amplify (global scope, us-east-1) and to Regional ALBs, API Gateway REST APIs, AppSync, Cognito, App Runner and Verified Access — never to NLBs, EC2 or HTTP APIs.
  • 3 Design, implement, and troubleshoot security controls for compute workloads
    2 (SCS-C03). Hardened Amazon EC2 AMIs and container images (Systems Manager, EC2 Image Builder); instance profiles, service roles, and execution roles to authorize compute workloads; scanning compute resources for vulnerabilities (Amazon Inspector for container images and Lambda functions, GuardDuty runtime monitoring); automated patching and continuous validation (Systems Manager Patch Manager, Amazon Inspector); secure administrative access (Systems Manager Session Manager, EC2 Instance Connect); discovering and remediating vulnerabilities within a pipeline (Amazon Q Developer, Amazon CodeGuru Security); protections and guardrails for generative AI applications (GenAI OWASP Top 10 for LLM Applications).
    • 📖 Lesson: Securing Compute Workloads: EC2, Containers, and Lambda
    • Must know: IMDSv2 defeats SSRF credential theft; a hop limit of 1 keeps bridged containers out only when HttpTokens is required. Launch parameters beat account defaults, which beat the AMI setting, so only an ec2:MetadataHttpTokens deny or account-level IMDSv2 enforcement makes an IMDSv1 launch fail.
    • Must know: Instance profiles store nothing on the host; GetSessionToken and IAM Roles Anywhere both depend on a stored secret. Pin role credentials with aws:Ec2InstanceSourceVpc compared to ${aws:SourceVpc}, scoped to ec2:SourceInstanceARN and excluding aws:ViaAWSService.
  • 3 Design and troubleshoot network security controls
    3 (SCS-C03). Network controls to permit or prevent traffic (security groups, network ACLs, AWS Network Firewall); secure connectivity between hybrid and multi-cloud networks (AWS Site-to-Site VPN, AWS Direct Connect, MAC Security [MACsec]); security requirements for communication between hybrid environments and AWS (AWS Verified Access); network segmentation from security requirements (north/south and east/west traffic protections, isolated subnets); identifying unnecessary network access (AWS Verified Access, Network Access Analyzer, Amazon Inspector network reachability findings).
    • 📖 Lesson: Network Security Controls: SGs, NACLs, Network Firewall, and Egress
    • Must know: Security groups are stateful and allow-only; referencing SGs as sources gives micro-segmentation that survives IP churn — behind a load balancer reference the load balancer's group, and across a transit gateway referencing works inbound only and not through an inspection VPC.
    • Must know: NACLs are stateless, ordered (lowest matching number wins), subnet-wide, and the only layer with an explicit deny: allow the ephemeral range in the reply direction, and number an exception below the deny it carves out.

Domain 4: Identity and Access Management

Weight: 20%. Authentication and authorization strategies for human, application, and system access — the heaviest-weighted domain on the exam.

📝 Revision notes: Domain 4: Identity and Access Management

  • 4 Design, implement, and troubleshoot authentication strategies
    1 (SCS-C03). Identity solutions for human, application, and system authentication (AWS IAM Identity Center, Amazon Cognito, multi-factor authentication [MFA], identity provider [IdP] integration); mechanisms to issue temporary credentials (AWS STS, Amazon S3 presigned URLs); troubleshooting authentication issues (CloudTrail, Amazon Cognito, IAM Identity Center permission sets, AWS Directory Service).
    • 📖 Lesson: AWS Authentication Strategies: MFA, STS, and Federation
    • Must know: Enforce MFA with an explicit deny using BoolIfExists on aws:MultiFactorAuthPresent (or Null on aws:MultiFactorAuthAge) and put the enrollment carve-out inside the deny with NotAction — a separate Allow cannot beat an explicit deny.
    • Must know: FIDO2 security keys and passkeys resist real-time phishing because they sign for the origin; any typed code, virtual or hardware TOTP, can be relayed. SMS is not an IAM MFA option, and each IAM user can register up to eight devices.
  • 4 Design, implement, and troubleshoot authorization strategies
    2 (SCS-C03). Authorization controls for human, application, and system access (Amazon Verified Permissions, IAM paths, IAM Roles Anywhere, resource policies for cross-account access, IAM role trust policies); attribute-based access control (ABAC) and role-based access control (RBAC) strategies (resource access based on tags or attributes); IAM policies following least privilege (permission boundaries, session policies); analyzing authorization failures (IAM Policy Simulator, IAM Access Analyzer); investigating and correcting unintended permissions, authorizations, or privileges (IAM Access Analyzer).
    • 📖 Lesson: IAM Policy Evaluation and Authorization Strategies on AWS
    • Must know: Evaluation order: explicit deny first, then the organization ceilings, resource-based and identity-based grants, permissions boundaries, and session policies — with implicit deny for anything never allowed.
    • Must know: Only identity-based and resource-based policies grant access; SCPs, RCPs, boundaries, and session policies are ceilings that can only take away.

Domain 5: Data Protection

Weight: 18%. Encryption in transit and at rest, plus protecting confidential data, credentials, secrets, and cryptographic key materials.

📝 Revision notes: Domain 5: Data Protection

  • 5 Design and implement controls for data in transit
    1 (SCS-C03). Requiring encryption when connecting to resources (Elastic Load Balancing [ELB] security policies, enforcing TLS configurations); secure and private access to resources (AWS PrivateLink, VPC endpoints, AWS Client VPN, AWS Verified Access); inter-resource encryption in transit (inter-node encryption for Amazon EMR, Amazon EKS, SageMaker AI, Nitro encryption).
    • 📖 Lesson: Data in Transit on AWS: TLS, ACM, and End-to-End Encryption Design
    • Must know: Enforcement is server-side: a Deny on aws:SecureTransport = false for S3 (with any s3:TlsVersion deny added alongside, never instead), CloudFront viewer and origin protocol policies, rds.force_ssl or require_secure_transport, and ElastiCache transit encryption mode required.
    • Must know: ELB security policy names encode the versions (TLS13-1-2 = TLS 1.2 minimum, TLS13-1-3 = TLS 1.3 only); listeners created by CLI or CloudFormation without SslPolicy get ELBSecurityPolicy-2016-08, so govern them with an SCP on elasticloadbalancing:SecurityPolicy.
  • 5 Design and implement controls for data at rest
    2 (SCS-C03). Data encryption at rest — selecting the appropriate encryption key service (AWS CloudHSM, AWS KMS) and encryption type (client-side vs server-side); protecting data integrity (S3 Object Lock, S3 Glacier Vault Lock, versioning, digital code signing, file validation); automatic lifecycle management and retention (S3 Lifecycle policies, S3 Object Lock, Amazon EFS Lifecycle policies, Amazon FSx for Lustre backup policies); secure data replication and backup (Amazon Data Lifecycle Manager, AWS Backup, ransomware protection, AWS DataSync).
    • 📖 Lesson: Encryption at Rest on AWS: KMS Keys, Key Policies, and Service Integration
    • Must know: Customer managed keys are the only key type with editable key policies, a chosen rotation period, grants, disabling, deletion, and cross-account use; KMS-generated material supports all of it.
    • Must know: Use CloudHSM directly only when you must manage the HSM users or keep PKCS#11/JCE code; a CloudHSM-backed custom key store is still reached only through the KMS API. Choose client-side encryption when the storage service must never see plaintext.
  • 5 Design and implement controls to protect confidential data, credentials, secrets, and cryptographic key materials
    3 (SCS-C03). Management and rotation of credentials and secrets (AWS Secrets Manager); managing and using imported key material (rotating imported key material, external key stores); differences between imported key material and AWS generated key material; masking sensitive data (CloudWatch Logs data protection policies, Amazon SNS message data protection); creating and managing encryption keys and certificates across a single AWS Region or multiple Regions (AWS KMS customer managed keys, AWS Private Certificate Authority).
    • 📖 Lesson: Protecting Secrets, Confidential Data, and Cryptographic Key Material
    • Must know: Secrets Manager earns its cost with rotation, cross-account resource policies and multi-Region replication; a standard-tier Parameter Store SecureString is the free answer for encrypted configuration that never rotates.
    • Must know: Four rotation forms: service-managed secrets (no function), AWS-provided templates (a Lambda in your account), managed external secrets (onboarded SaaS partners only, no Lambda) and custom four-step functions for everything else.

Domain 6: Security Foundations and Governance

Weight: 14%. Multi-account strategy, secure and consistent deployment of cloud resources, and evaluating compliance across AWS environments.

📝 Revision notes: Domain 6: Security Foundations and Governance

  • 6 Develop a strategy to centrally deploy and manage AWS accounts
    1 (SCS-C03). Deploying and configuring organizations with AWS Organizations; implementing and managing AWS Control Tower in new and existing environments with optional and custom controls; organization policies to manage permissions (SCPs, RCPs, AI service opt-out policies, declarative policies); centrally managing security services (delegated administrator accounts); managing AWS account root user credentials (centralizing root access for member accounts, managing MFA, break-glass procedures).
    • 📖 Lesson: AWS Organizations, SCPs, and Control Tower: Multi-Account Security Strategy
    • Must know: Separate accounts are the blast-radius boundary: cross-account access is denied by default, so IAM changes inside one account cannot reach another — only an explicit resource or trust policy grant can open it.
    • Must know: Logs go to the log-archive account, security tooling to the audit account; the Suspended OU is a pre-built quarantine you move a compromised account into without changing anything inside it.
  • 6 Implement a secure and consistent deployment strategy for cloud resources
    2 (SCS-C03). Infrastructure as code (IaC) to deploy cloud resources consistently and securely across accounts (CloudFormation stack sets, third-party IaC tools, CloudFormation Guard, cfn-lint); using tags to organize AWS resources into groups (by department, cost center, environment); deploying and enforcing policies and configurations from a central source (AWS Firewall Manager); securely sharing resources across AWS accounts (AWS Service Catalog, AWS Resource Access Manager [AWS RAM]).
    • 📖 Lesson: Secure IaC Deployment: CloudFormation, StackSets, and Service Catalog
    • Must know: Peer review, attribution, and revert together need source control with pull requests; a versioned S3 bucket gives only the revert.
    • Must know: Drift detection compares only properties explicitly set in the template or parameters, so declare security-relevant settings; CloudTrail, not drift, tells you who changed something.
  • 6 Evaluate the compliance of AWS resources
    3 (SCS-C03). Rules to detect and remediate noncompliant AWS resources and send notifications (AWS Config alert aggregation and remediation, Security Hub); AWS audit services to collect and organize evidence (AWS Audit Manager, AWS Artifact); evaluating architecture for compliance with AWS security best practices (AWS Well-Architected Framework tool).
    • 📖 Lesson: Evaluating AWS Resource Compliance: Config, Security Hub, Audit Manager
    • Must know: AWS Config evaluates only what it records: a customer managed recorder (one per account per Region, needs a delivery channel to start) produces configuration items, and rules evaluate them on change or on a schedule.
    • Must know: A stopped recorder silences change-triggered rules and leaves a permanent gap in history; periodic rules keep running, so the breakage is easy to miss.

How to study for SCS-C03

  1. Read the lesson for each topic in the checklist above, starting with the heaviest domain. Every lesson is free on the SCS-C03 revision notes.
  2. Practice straight after reading. Answer SCS-C03 practice questions on the topic you just read. Each option comes with an explanation of why it is right or wrong.
  3. Review what you got wrong, re-read that lesson section, and tick the topic off only when you get its questions right.
  4. Take a full-length SCS-C03 mock exam under the real time limit. Aim to pass mocks comfortably before you book.
  5. On the last day, skim the SCS-C03 cheat sheet instead of starting anything new.

Sample questions

sample-questions.md has 20 worked SCS-C03 questions with the answer, why each option is right or wrong, and the reasoning steps.

Free resources

Contributing

Spotted an error or an out-of-date fact? Open an issue with the topic and a link to the official source. See CONTRIBUTING.md.

License and disclaimer

This guide is licensed under CC BY 4.0. You can reuse and adapt it, including commercially, as long as you credit SaveMyCert with a link to https://www.savemycert.com/.

This is an independent study resource. It is not affiliated with or endorsed by Amazon Web Services. AWS Certified Security – Specialty and SCS-C03 are trademarks of their respective owner. Exam domains and weights are taken from the official exam guide linked above.

About

Free SCS-C03 study guide: the full AWS Certified Security – Specialty exam blueprint as a checklist, key facts per topic, and worked sample questions.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors