SCS-C03 · CHEAT SHEET
AWS Certified Security - Specialty
Key concepts grouped by official exam weight.
Download as PDF (free, no sign-up)1. Detection
16–16%Design and implement monitoring and alerting solutions for an AWS account or organization
- Monitoring requirements start from the workload type: GuardDuty analyzes CloudTrail, VPC flow logs and DNS logs with no extra setup, and protection plans extend it per resource (RDS Protection for Aurora and RDS logins, Lambda Protection, EKS Protection and Runtime Monitoring for containers and instances). Inspector, Macie and Security Hub CSPM cover vulnerabilities, sensitive data and controls.
- Route 53 offers endpoint health checks (HTTP, HTTPS, TCP and string matching), calculated health checks and CloudWatch alarm-based health checks, useful for instances with only private IP addresses. Security groups must allow the health checkers through the managed prefix list, and alarms on health check status are created in US East (N. Virginia). Synthetics canaries mimic customers and detect unauthorized changes.
- To centralize events, Security Hub CSPM replicates findings and control statuses to a home Region, GuardDuty uses the same delegated administrator account in every Region, an organization-based Config aggregator gives a read-only view without per-account authorization, and CloudWatch links source accounts to a monitoring account. EventBridge does not forward events received from another account to a third account.
- Metric filters on CloudTrail logs in CloudWatch Logs, with alarms and SNS, alert on events such as root user usage; the CIS controls require the exact pattern. GuardDuty, Macie and Security Hub CSPM publish findings to EventBridge, and one rule in the administrator account covers the members. CloudWatch anomaly detection learns daily and weekly patterns instead of a static threshold.
- A conformance pack bundles AWS Config rules and remediation actions; deployed for the organization it reaches new accounts and members cannot modify it, but Config recording must be on. Config remediates with Automation documents, State Manager keeps nodes in a defined state on a schedule, and Security Hub CSPM central configuration enforces standards across accounts and Regions.
Design and implement logging solutions
- Each need has its source: CloudTrail data events (off by default) record Lambda Invoke and S3 object operations, but not requests with invalid credentials, which S3 server access logs do record. Resolver query logs keep DNS queries, Transit Gateway Flow Logs keep traffic through the transit gateway, and AWS WAF requires destinations whose names start with aws-waf-logs-.
- An organization trail, created from the management or delegated administrator account, logs all accounts and member accounts cannot change it; the bucket policy aws:SourceArn uses the management account ID. The CloudWatch agent needs CloudWatchAgentServerPolicy and parameters prefixed AmazonCloudWatch-, API Gateway needs a cloudWatchRoleArn per Region, and CloudWatch Logs centralization copies new log data.
- Security Lake centralizes AWS, SaaS, on-premises and third-party data in S3 buckets in your account, normalized to OCSF in Apache Parquet. Native sources need no logging setup, except management events, which require a multi-Region organization trail. Custom sources must deliver OCSF in Parquet, and subscribers get data access (notifications) or query access (Athena) per source.
- CloudWatch Logs Insights analyzes logs in CloudWatch Logs with its query language, OpenSearch PPL or SQL (with JOINs across log groups) and speeds up searches with field indexes. Athena runs SQL over CloudTrail or flow logs in S3, and partition projection avoids adding partitions by hand. Security Hub CSPM insights group findings from several providers by an attribute.
- CloudWatch Logs transformers normalize events at ingestion with templates for AWS vended logs or Grok parsers. Security Lake normalizes data to OCSF in Parquet, OpenSearch Ingestion indexes it without servers, and OpenSearch Security Analytics applies Sigma rules with alerts. Managed Grafana combines several data sources in one panel.
Troubleshoot security monitoring, logging, and alerting solutions
- Lambda writes logs only if its execution role has logs:CreateLogGroup, CreateLogStream and PutLogEvents. API Gateway needs a role in cloudWatchRoleArn in each Region. Route 53 health checks require allowing the route53-healthchecks prefix list, and CloudFront legacy logging needs ACLs enabled and a customer managed key when SSE-KMS is used.
- When CloudWatch agent logs are missing: an i/o timeout in private subnets calls for interface endpoints with private DNS; after editing the configuration you must run fetch-config; without log_group_name the group is named after file_path. Flow logs need a role that trusts vpc-flow-logs.amazonaws.com, and CloudTrail needs permissions in the bucket policy and the KMS key policy.
2. Incident Response
14–14%Design and test an incident response plan
- OpsCenter creates OpsItems from EventBridge events and CloudWatch alarms, avoids duplicates with /aws/dedup and lets you run Automation runbooks from each OpsItem, also across accounts with a delegated administrator. Playbooks follow the analyze, contain, eradicate and recover phases, and SageMaker AI Jupyter notebooks support investigations with root access disabled and no direct internet access.
- Preparation means pre-provisioning incident response roles in every account, with policies generated by IAM Access Analyzer, trust limited to the security account and MFA, and named break-glass users without keys. Per-Region forensics accounts are created before incidents. Shield Advanced proactive engagement requires Route 53 health checks, and the SRT cannot read KMS-encrypted buckets.
- To test the response plan: GuardDuty CreateSampleFindings validates rules and automation without real attacks; AWS FIS runs experiments with alarm-based stop conditions and a safety lever that stops them all; Resilience Hub assesses RTO and RPO against a policy. Simulations can be tabletop, purple team or red team exercises.
- AWS Config remediates automatically with Systems Manager Automation runbooks and retries. AWSSupport-ContainEC2Instance contains instances reversibly, also in Auto Scaling groups. Revoking role sessions uses aws:TokenIssueTime. Step Functions orchestrates responses with Retry and Catch, Automated Forensics Orchestrator captures memory and disk, and ARC zonal shift moves traffic away from a zone.
Respond to security events
- On a compromised EC2 instance, acquire the metadata, instance protections and tags, EBS snapshots and memory, in that order and before isolation or shutdown. Store evidence in a forensic account: snapshots encrypted with a customer managed key, S3 Object Lock in compliance mode, and CloudTrail logs with integrity validation.
- To search logs in S3, use Athena with partition projection; for CloudWatch Logs, use Logs Insights, which with cross-account observability queries log groups of several accounts in a Region. Security Lake normalizes AWS and external sources to OCSF in Parquet, and query access subscribers use Athena. The STS source identity attributes actions taken with shared roles.
- Analysis starts by validating the alert, then scopes it and finally assesses the business impact. In GuardDuty, Resource role shows whether the resource was the target or the actor; confirmed false positives are archived with suppression rules, which Extended Threat Detection does not use as signals. AWS Security Hub exposure findings correlate signals with network reachability.
- Containment can target the source, the technique and access, or the destination. Changing a security group does not cut tracked connections; a network ACL does, but affects the whole subnet. Role sessions are revoked with AWSRevokeOlderSessions, and AWSSupport-ContainEC2Instance isolates an instance reversibly. Recovery uses clean backups from before the first event and is tested.
- Amazon Detective builds a behavior graph from CloudTrail, VPC flow logs and GuardDuty findings through its own streams, without changing existing configurations. Finding groups are the starting point for root cause analysis, and Detective Investigation analyzes IAM roles and users against indicators of compromise. The AWS Config Resource Timeline shows what changed and who changed it.
3. Infrastructure Security
18–18%Design, implement, and troubleshoot security controls for network edge services
- Shield Advanced only protects the resources you specify (CloudFront, Route 53, Global Accelerator, Elastic IPs, ALBs and NLBs through Elastic IPs) and adds the SRT and cost protection; Firewall Manager applies protection across the organization. Route 53 health checks improve detection and are required for proactive engagement. Evasive bots and fraud call for targeted Bot Control, ATP and ACFP.
- To let only CloudFront reach an ALB, use a secret custom header required by the listener rules and the CloudFront managed prefix list. Response headers policies add HSTS and other headers; the core rule set covers XSS and the SQL database group covers SQL injection. S3 CORS requires matching origin, method and headers, and AWS IoT policies use thing policy variables.
- CloudFront geographic restrictions act on the whole distribution and by country; AWS WAF combines geo match with paths, IP sets and region labels. Rate-based rules aggregate on source IP, IP in a header, Count all or custom keys such as IP and User-Agent, with scope-down statements. JA3 and JA4 fingerprints identify the client's TLS configuration.
- Amazon Security Lake natively collects services such as AWS WAFv2 logs and normalizes them to OCSF in Parquet; third-party data enters as a custom source, already converted to OCSF and written under its prefix with the role that Security Lake creates. AWS Marketplace rule groups are subscribed to, added to the web ACL, and tested by overriding their rule actions to Count.
Design, implement, and troubleshoot security controls for compute workloads
- EC2 Image Builder hardens AMIs with Amazon managed STIG components and AWS Marketplace CIS components (image recipes only, not container recipes); the instance profile needs EC2InstanceProfileForImageBuilder and AmazonSSMManagedInstanceCore, and a clean-up script removes SSH keys and logs unless user data is overridden without creating perform_cleanup. Allowed AMIs, set by a declarative policy, limits which AMIs can be used.
- Each workload gets temporary credentials from its own role: an instance profile on EC2, an execution role on Lambda (trusting lambda.amazonaws.com), a task role for ECS application code and a task execution role for image pulls, logs and secrets, and EKS Pod Identity or IRSA for pods. Passing a role requires iam:PassRole, scoped with Resource and iam:PassedToService.
- Amazon Inspector scans EC2 with the SSM Agent or agentlessly through EBS snapshots (hybrid mode), ECR images with enhanced scanning (operating system and language packages) and Lambda with standard and code scanning. GuardDuty Runtime Monitoring detects runtime threats on EKS, EC2 and ECS on Fargate with a managed agent; on Fargate it is a sidecar pulled with the task execution role.
- Patch Manager defines compliance with patch baselines (auto-approval rules with a delay, approved and rejected lists, where rejection wins) and AWS-RunPatchBaseline scans or installs. A Quick Setup patch policy covers every account and Region in the organization. Continuous validation relies on the Config patch compliance rule and on Amazon Inspector, which closes remediated findings.
- Session Manager gives access without inbound ports, bastion hosts or SSH keys, controlled with IAM, with session logging to S3 or CloudWatch Logs (not available for port forwarding or SSH), extra encryption with a symmetric KMS key and Run As through the SSMSessionRunAs tag. EC2 Instance Connect pushes a temporary public key, and EC2 Instance Connect Endpoint reaches instances without public IPs with OpenTunnel limited by conditions.
Design and troubleshoot network security controls
- Security groups are stateful, support allow rules only and can reference other groups; network ACLs are stateless, apply to the subnet and evaluate rules from the lowest number, with the first match deciding. AWS Network Firewall filters the traffic that route tables send to its endpoints, with stateless rules (Pass, Drop or Forward to stateful rules) and stateful rules such as domain lists.
- Direct Connect does not encrypt traffic by default: MACsec encrypts at Layer 2 the segment between your router and the Direct Connect device on dedicated connections (not hosted ones), and must_encrypt mode never allows unencrypted traffic. Private IP VPN runs IPsec over a transit virtual interface to a transit gateway without public IP addresses.
- AWS Verified Access provides application access without a VPN and evaluates every request with Cedar policies that use data from an identity trust provider (IAM Identity Center or an OIDC IdP) and device providers such as Jamf or CrowdStrike. With no policy defined, everything is denied; endpoints can be internal load balancers, network interfaces, CIDRs or RDS, and each attempt is logged in OCSF format.
- An isolated subnet has no routes outside its VPC. Separate Transit Gateway route tables isolate environments while sharing common services, and centralized east/west and north/south inspection with Network Firewall needs appliance mode so traffic stays symmetric. Network ACLs deny at the subnet level, security groups only allow, and DNS Firewall filters queries to the Resolver.
- Network Access Analyzer performs a static analysis of the configuration and reports as findings the paths that match MatchPaths and no ExcludePaths, for example internet traffic that bypasses a firewall. Amazon Inspector periodically generates network reachability findings, only for EC2 instances. Verified Access replaces the broad network access of a VPN with per-application access evaluated on every request.
4. Identity and Access Management
20–20%Design, implement, and troubleshoot authentication strategies
- IAM Identity Center centralizes workforce access to all accounts with an external IdP (SAML and SCIM) or Active Directory; with an external IdP, the IdP manages MFA. Cognito separates user pools (directory and tokens) from identity pools (temporary credentials per role, also for guests). IAM Roles Anywhere gives temporary credentials to servers outside AWS that use X.509 certificates.
- AWS STS issues temporary credentials through AssumeRole, AssumeRoleWithSAML, AssumeRoleWithWebIdentity or GetSessionToken; the external ID prevents the confused deputy, session policies only restrict, and source identity persists through role chaining. An S3 presigned URL expires when the credentials that signed it expire, and s3:signatureAge limits its age.
- An AccessDenied on AssumeRole usually means the trust policy does not include the caller or lacks sts:TagSession or sts:SetSourceIdentity. In IAM Identity Center the user must exist before signing in and the nameID must match the user name. AD Connector needs ports 88 and 389 and a valid service account, and CloudTrail masks incorrect user names.
Design, implement, and troubleshoot authorization strategies
- Amazon Verified Permissions authorizes inside custom applications with Cedar policies, and IAM Roles Anywhere gives workloads outside AWS temporary credentials for X.509 certificates from a registered CA. Cross-account access needs an allow in the resource or role trust policy and another in the caller's identity policy; sts:ExternalId and aws:SourceAccount prevent the confused deputy problem.
- ABAC grants permissions when the principal's tags match the resource's tags, so new resources and projects need no policy edits, unlike job-function RBAC. It relies on aws:ResourceTag, aws:RequestTag, aws:TagKeys and aws:PrincipalTag; IAM Identity Center and SAML IdPs send user attributes as session tags, and the tag keys that drive access must be protected with Deny statements.
- A permissions boundary sets the maximum that identity-based policies can grant to a user or role, and a session policy limits a single temporary session; effective permissions are the intersection and neither grants anything. To delegate role creation, require iam:PermissionsBoundary and deny changing or removing the boundary; IAM Access Analyzer policy generation starts from CloudTrail activity but leaves out iam:PassRole.
- An access denied message separates an explicit deny (with an explicit deny in) from an implicit one (because no ... allows) and names the policy type to fix. The IAM policy simulator tests identity policies, boundaries, SCPs and supplied resource policies without real requests but does not support RCPs; IAM Access Analyzer policy validation catches errors before deployment.
- IAM Access Analyzer finds unintended access with external access analyzers (resources shared outside the zone of trust, one per Region), internal access analyzers (principals in the organization that can reach critical resources) and unused access analyzers (unused roles, keys and permissions). Fix it by editing the policy that grants the access; archive rules only hide intended access, and after an RCP change the resource should be rescanned.
5. Data Protection
18–18%Design and implement controls for data in transit
- To require encryption in transit, choose the ELB listener security policy (ALBs do not support custom policies) and enforce it across the organization with the elasticloadbalancing:SecurityPolicy key in SCPs. In S3 deny requests where aws:SecureTransport is false; in CloudFront use the viewer and origin protocol policies, and in API Gateway disable the execute-api endpoint.
- Gateway endpoints serve only S3 and DynamoDB, are not billed and cannot be used from on premises; interface endpoints (PrivateLink) use private IP addresses and can. aws:SourceVpce in a bucket policy limits access to one endpoint. Client VPN gives network access through an OpenVPN client; Verified Access gives VPN-less application access that checks identity and device.
- Some Nitro instance types automatically encrypt traffic between instances in the same or peered VPCs when no load balancer or transit gateway is in the path. EMR in-transit encryption is enabled in a reusable security configuration with certificate artifacts (private key without passphrase). SageMaker AI encrypts inter-container traffic with EnableInterContainerTrafficEncryption plus UDP 500 and ESP 50 rules.
Design and implement controls for data at rest
- S3 offers four server-side types: SSE-S3 (default), SSE-KMS (key control and CloudTrail audit), DSSE-KMS (two layers) and SSE-C (key in every request). S3 Bucket Keys cut KMS calls, do not work with DSSE-KMS and do not apply to existing objects until copied. Client-side encryption keeps plaintext away from AWS; a CloudHSM key store gives single-tenant HSMs with KMS integration.
- S3 Object Lock compliance mode stops any user, including root, from deleting a version or shortening retention; governance mode can be bypassed with s3:BypassGovernanceRetention. Only the root bucket owner can enable MFA delete, through the CLI or API. Lambda code signing with Enforce blocks unsigned deployments. CloudTrail file validation uses signed digest files and validate-logs.
- S3 Lifecycle keeps working with Object Lock but cannot delete locked versions, and the lock persists through transitions. NoncurrentVersionExpiration with NewerNoncurrentVersions keeps recent versions and removes older ones. EFS lifecycle policies move files to IA and Archive and can bring them back to Standard on first access. FSx for Lustre automatic backup retention defaults to 0 days; user-initiated backups never expire.
- AWS Backup Vault Lock in compliance mode becomes immutable when the grace time ends; governance mode can be removed with IAM permissions. A logically air-gapped vault comes with that lock and can be shared through RAM, even outside the organization. Cross-account copies need the same organization and shared customer managed keys. DataSync avoids the internet with a VPC service endpoint.
Design and implement controls to protect confidential data, credentials, secrets, and cryptographic key materials
- Secrets Manager rotates secrets with managed rotation (for example the RDS master password with ManageMasterUserPassword) or with a Lambda function that runs createSecret, setSecret, testSecret and finishSecret. The alternating users strategy keeps valid credentials during rotation. Without internet access the function needs a VPC endpoint. Cross-account access needs a resource policy and a customer managed key.
- Imported material can expire and is renewed by reimporting the same material with a new wrapping key and token; if it expires or is deleted the key goes to PendingImport. EXTERNAL-origin symmetric keys rotate on demand by importing NEW_KEY_MATERIAL and calling RotateKeyOnDemand; multi-Region keys import into the primary first. An external key store (XKS) uses your own proxy, reached publicly or through a VPC endpoint service.
- With AWS-generated key material, AWS KMS owns durability and supports automatic rotation, and the material never leaves its HSMs unencrypted. With imported material (EXTERNAL origin), the customer owns durability and the original copy, can set an expiration or delete and reimport it, and only on-demand rotation is available. Imported material cannot be exported and also supports interoperable asymmetric and HMAC keys.
- CloudWatch Logs data protection policies audit and mask sensitive data with managed or custom (regex) data identifiers, per log group or account-wide, including future log groups. Masking happens at ingestion and is not retroactive, and only principals with logs:Unmask see the original values. For Amazon Bedrock prompts and responses, use Guardrails sensitive information filters.
- KMS multi-Region keys share key ID and key material across Regions, so data encrypted in one Region can be decrypted in another without cross-Region calls; existing keys cannot be converted, rotation is managed on the primary and imported material must be imported into each replica. AWS Private CA is Regional, is shared across accounts with AWS RAM, and works best with a protected root and issuing subordinate CAs.
6. Security Foundations and Governance
14–14%Develop a strategy to centrally deploy and manage AWS accounts
- AWS Organizations needs the all features set to use SCPs, RCPs and service integrations; when migrating from consolidated billing, invited accounts must accept. Keep workloads out of the management account, which SCPs do not affect, and use an SCP that stops accounts from leaving the organization. Recommended OUs include Security, Infrastructure, Workloads, Sandbox, Suspended and Policy Staging.
- AWS Control Tower governs OUs and accounts with preventive controls (SCPs, RCPs and declarative policies), detective controls (AWS Config rules) and proactive controls (CloudFormation hooks before provisioning). Existing accounts join by registering their OU or by enrollment, without existing AWS Config resources. Customizations for AWS Control Tower (CfCT) deploys custom templates, SCPs and RCPs to accounts vended by Account Factory.
- SCPs set the maximum permissions of principals in member accounts and RCPs those of their resources, including against external identities; neither grants permissions or affects the management account. Declarative policies enforce a baseline configuration of services such as EC2 in the control plane. AI services opt-out policies stop AWS from using content to improve its AI services.
- Security services such as GuardDuty, Security Hub CSPM, Macie, Inspector and AWS Config are managed from a member account designated as delegated administrator, not from the management account. GuardDuty and Inspector are Regional and require the same administrator in every Region; Security Hub CSPM offers central configuration with configuration policies. SCPs also apply to delegated administrator accounts.
- With centralized root access, the management account or the delegated administrator for IAM removes member account root credentials and performs privileged tasks through short sts:AssumeRoot sessions scoped by a task policy. The management account root user must have MFA, ideally several devices, no access keys, and custody split between two groups for break-glass access.
Implement a secure and consistent deployment strategy for cloud resources
- CloudFormation StackSets with service-managed permissions deploys templates to AWS Organizations OUs and accounts, creates the required roles and adds new accounts automatically, but does not deploy to the management account. CloudFormation Guard validates templates and Terraform JSON with policy-as-code rules and, as a Guard Hook, blocks resources before creation; cfn-lint checks syntax and properties.
- Tags (case-sensitive keys and values) organize resources by department, cost center or environment. Tag policies standardize keys and values and can block noncompliant values, but they do not evaluate untagged resources; to require tags, use SCPs or required tag keys for IaC. Tag-based resource groups are Regional, and Systems Manager can act on targets selected by tag.
- AWS Firewall Manager centrally applies AWS WAF, Shield Advanced, security group, network ACL, Network Firewall and DNS Firewall policies to the organization or to chosen accounts, OUs and tagged resources, and it covers new accounts and resources automatically. It needs AWS Organizations with all features, an administrator account, AWS Config with continuous recording and, for Network Firewall and DNS Firewall, resource sharing through AWS RAM.
- AWS RAM shares a resource created once with accounts, OUs or the whole organization; after sharing is enabled from the management account there are no invitations, and the managed permission of the share is the maximum that consuming accounts grant with IAM policies. AWS Service Catalog shares portfolios as a synchronized reference and uses launch constraints with a role to provision without direct permissions.
Evaluate the compliance of AWS resources
- AWS Config rules evaluate resources in detective or proactive mode, and automatic remediation uses Systems Manager Automation documents. Organization conformance packs deploy rules and remediations that member accounts cannot modify, aggregators give a read-only view, and EventBridge with SNS sends alerts. Security Hub CSPM centralizes findings and uses automation rules and custom actions.
- AWS Artifact provides AWS compliance reports (SOC, PCI, ISO) that may be shared only with auditors and regulators through secure channels, and it lets the management account accept agreements such as the BAA for the whole organization. For the company's own evidence, AWS Config offers conformance packs with history and process checks, and CloudTrail validates log integrity; Audit Manager is closed to new customers.
- The AWS Well-Architected Tool reviews a workload with the AWS Well-Architected Framework lens and its security pillar, identifies high and medium risk issues and builds an improvement plan; milestones record the state to measure progress. Workloads (Read-Only or Contributor), published custom lenses and review templates can be shared with the organization, and Trusted Advisor adds automated checks.