cert-bank

Guides

이 글을 한국어로 읽기

SCS-C03 Study Guide: Learn How AWS Decides One Request, Then Learn Who Is Watching

The AWS Certified Security – Specialty exam (SCS-C03) has six domains, but two questions run through all of them. Will this request be allowed? And if something goes wrong, which service will notice and what happens next? This guide is built on those two questions. First the access decision, layer by layer, because it decides more points than any single service. Then the detection services and what each one can actually see. Then the response and data protection rules that follow from both.

Study guide · AWS Certified Security – Specialty (SCS-C03)

SCS-C03 Study Guide: Learn How AWS Decides One Request, Then Learn Who Is Watching

The exam

65 questions in 170 minutes (50 scored and 15 unscored, which are not marked), passing score 750 on a scale of 100–1,000. Six domains: Detection (16%), Incident Response (14%), Infrastructure Security (18%), Identity and Access Management (20%), Data Protection (18%), Security Foundations and Governance (14%). No domain is small enough to skip.

In the 395 SCS-C03 questions in this question bank, IAM is the most frequent service by a wide margin: it is tagged on 23% of them, ahead of Amazon S3 (16%), AWS Organizations (11%), CloudTrail and KMS (10% each) and GuardDuty (9%). One question in five (20%) is a troubleshooting scenario, usually "this should work, why does it not?", and about 12% ask for two answers.

Part 1: the access decision

Every API call is checked against several kinds of policy at once. Some can grant access; others can only set a ceiling. Most IAM troubleshooting questions are solved by asking which layer is the one saying no.

Policy typeCan it grant?What it does
Service control policy (SCP)NoCaps what principals in member accounts can do, for example "only approved Regions" through aws:RequestedRegion.
Resource control policy (RCP)NoCaps what anyone, including external principals, can do to resources in your member accounts (for the services that support RCPs), even if a resource policy is too open.
Permissions boundaryNoCaps one user or role. The action must be in the identity policy and in the boundary.
Identity policyYesWhat the user or role may do.
Resource policyYesWho may use this bucket, key, queue or secret. aws:PrincipalOrgID limits it to your organisation.
Session policyNoNarrows a single assumed-role session.

Two rules sit above the table. An explicit deny in any of these policies ends the decision; allows only matter when nothing denies. And the ceilings combine: an action must survive every ceiling that applies before any allow counts.

Going deeper: why cross-account access needs both sides, and KMS needs a third

Within one account, an allow in either the identity policy or the resource policy is usually enough. Across accounts it is not: the caller's own account must allow the action in its identity policy, and the resource's account must allow that caller in its resource policy (or in a role's trust policy, if the caller assumes a role there). Each account controls its own side. AWS KMS adds one more rule: the key policy is the primary control, and IAM policies in the key's account only take effect if the key policy allows the account to delegate to them. That is why the classic question "the bucket policy allows the other account, but reads of SSE-KMS objects still fail" is answered by adding kms:Decrypt for that account to the key policy (the caller's IAM policy must allow it too). It is also why an AWS managed key such as aws/secretsmanager or aws/rds, whose key policy you cannot edit, cannot be used across accounts: use a customer managed key.

Beginner tip: in a sandbox account, create a role with AdministratorAccess and attach a permissions boundary that allows only s3:ListBucket and s3:GetObject. Assume the role and try to upload a file. Then open the IAM policy simulator for the same role and the action s3:PutObject: it shows that the boundary, not the identity policy, is the reason for the denial. Doing this once turns "allowed by the identity policy is not enough" from a sentence into something you have seen.

SCS-C03: how an AWS request is allowed or denied
Explicit deny
A deny in any policy ends the decision
Organization ceilings
SCP caps principals in member accounts · RCP caps what anyone can do to your resources
Principal ceilings
Permissions boundary caps one user or role · Session policy narrows one session
Grants
Identity policy: what the user or role may do · Resource policy: who may use this resource
Read from the top: a request must pass every ceiling that applies before any allow counts.

Part 2: who is watching, and what each one sees

Detection questions offer several monitoring services that all sound relevant. Each sees a different thing; pick the one whose input matches the question.

ServiceAnswers the question
AWS CloudTrailWho called which API, when and from where. Insights flags unusual call volumes or error rates.
AWS ConfigWhat a resource looked like over time and whether it complies with your rules.
Amazon GuardDutyIs something malicious happening? Threat findings from logs and activity. It detects; it does not block.
Amazon DetectiveWhat happened around a finding: related entities and activity over time.
AWS Security Hub CSPMControl checks against standards such as AWS Foundational Security Best Practices and CIS, plus findings from GuardDuty, Inspector and Macie, in one place across accounts. (It was named AWS Security Hub; that name now belongs to a newer service that correlates these findings into exposures.)
Amazon InspectorKnown vulnerabilities in EC2 instances, container images and Lambda functions. Each resource type is enabled separately.
Amazon MacieWhere sensitive data sits in S3.
IAM Access AnalyzerWhich resources are reachable from outside your zone of trust; separately, internal access to selected resources and unused access.

In a multi-account setup, the exam expects a dedicated security tooling account as delegated administrator for GuardDuty and Security Hub, an organisation trail that member accounts cannot stop, and EventBridge rules to route high-severity findings to automation or a chat channel. Logs that must not be altered go to a separate log archive account, with CloudTrail log file integrity validation to detect tampering and S3 Object Lock to prevent it.

Part 3: when something goes wrong

Incident Response questions test order and completeness. A leaked access key is deactivated first; cleaning the code repository does not revoke anything. Deactivating the key also does not end sessions already created with it, so add a deny conditioned on aws:TokenIssueTime (what "revoke active sessions" on a role does). To isolate an instance, even from neighbours in the same subnet, change its security groups, on every network interface it has; network ACLs and routes act on the whole subnet. Preserve evidence before you clean up, and use Object Lock in compliance mode when even the root user must not delete it; governance mode can be bypassed by privileged users.

Part 4: data protection rules that surprise people

  • You cannot encrypt an existing RDS instance or EBS volume in place. Copy a snapshot with encryption, then restore or create from the copy.
  • SSE-S3 already encrypts objects by default. Choose SSE-KMS with a customer managed key when you need to control who can use the key through your own key policy; KMS calls are also recorded in CloudTrail.
  • A KMS key belongs to one Region. Encrypted data copied to another Region needs a key there (or a multi-Region key).
  • Private, internal-only TLS certificates come from AWS Private CA, not public ACM certificates.
Going deeper: why KMS encrypts keys, not files

The KMS Encrypt operation accepts only a small amount of data (up to 4,096 bytes), because KMS keys never leave the service and every byte would have to travel to it. For real data, services use envelope encryption: they call GenerateDataKey, receive a data key in plain text and the same key encrypted under the KMS key, encrypt the data locally with the plain-text key, discard it, and store the encrypted data key next to the data. To decrypt, they send only the small encrypted data key to KMS. This is why a question about encrypting a large file "with KMS" fails if the answer calls Encrypt on the file, and why denying kms:Decrypt on a key locks out everything encrypted under it, however many objects that is.

A study order

  1. IAM policy evaluation, cross-account roles, STS, Identity Center and Organizations policies (SCPs, RCPs, tag policies).
  2. KMS key policies, grants and envelope encryption; S3 encryption options; Secrets Manager.
  3. Network controls: security groups, network ACLs, VPC endpoints and their policies, WAF, Firewall Manager, Shield.
  4. Detection services, then incident response runbooks, then governance (Control Tower, Config conformance packs, delegated administrators).

Practise

Practise in the question bank: every question explains each option, right and wrong. Start with the domain you just studied, then take a timed mock exam.

Exam facts as published in the AWS exam guide and on the exam page for SCS-C03; service shares refer to our own practice bank. Security services gain features often; check the current documentation and the official exam page.