Study guide · Domain 2 · 30% of the exam
Security and Compliance: the AWS Certified Cloud Practitioner objectives in plain English
Domain 2 is about who protects what in the cloud, how access is controlled, and which services help you prove that controls are working. It starts with the shared responsibility model from Amazon Web Services, then covers governance and compliance concepts, access management with IAM, and the main security services you need to recognize by name and job. At 30 percent of the exam, this is the second largest domain, and its ideas appear in questions about almost every other service. Help desk work already touches much of it, from password resets to multifactor setup.
What the objectives cover
2.1 Understand the AWS shared responsibility model
The shared responsibility model divides security work between Amazon Web Services and the customer. Security OF the cloud is the AWS side. It includes the physical security of data centers, the buildings, power, and cooling that support them, the hardware for servers, storage, and networking, and the global infrastructure that connects regions and edge locations. AWS also maintains the software that runs its managed services and the virtualization layer. Security IN the cloud is the customer side. It includes your data and how you classify it, who can access your account and resources, how you configure operating systems and applications you control, and how you set network controls such as security groups. A simple test helps on exam questions: if the task concerns the facility, the hardware, or the underlying platform, it belongs to AWS. If it concerns your accounts, your data, your settings, or what you deployed, it belongs to you.
How much stays with you depends on the service type, because managed services shift more work to AWS. With Amazon EC2, AWS handles the physical host and virtualization, but you patch the guest operating system, update your applications, configure security groups, and control user access to the instance. With a managed service such as Amazon RDS, AWS also patches the database software and the operating system underneath it and handles routine maintenance, while you still control who can connect, how data is encrypted, which settings you choose, and how you manage backups and database accounts. With AWS Lambda, the shift goes further: AWS runs and patches the servers, operating system, and runtime environment and scales the platform, while you remain responsible for your function code, its dependencies, the permissions its role receives, and the data it processes. The pattern is consistent: the more managed the service, the more platform work AWS takes, but your data, access decisions, and configuration choices never transfer to AWS.
2.2 Understand AWS Cloud security, governance, and compliance concepts
This objective asks you to recognize how AWS supports regulated and audited work, not to become an auditor. AWS participates in many compliance programs and certifications, and customers can often inherit part of that coverage for their own audits when they build on compliant infrastructure. At this level, recognize common program names when they appear, such as programs that relate to health care, payment cards, government work, and international security standards, and know that a program applying to AWS infrastructure does not by itself make your own application compliant. Encryption is a core control here. Encryption at rest protects data stored on disks, in databases, and in object storage when it is not moving. Encryption in transit protects data as it moves between a user, a service, or systems, commonly through secure connections. AWS Artifact is the place to get compliance reports and agreements you can provide to auditors as evidence of AWS controls. Two services support governance day to day. AWS CloudTrail records API activity in an account, so you can see who made a call, when it happened, and what changed, which makes it the main tool for API auditing and investigations. AWS Config records the configuration history of resources and evaluates it against rules, so you can see how a resource was set up, whether it changed, and whether it still matches the configuration your organization requires.
2.3 Identify AWS access management capabilities
AWS Identity and Access Management, or IAM, controls who can sign in and what they can do in an account. An IAM user is an identity for a person or application that needs long term credentials. An IAM group is a collection of users, so you can attach permissions once to the group and add or remove users as roles change, instead of editing each user alone. An IAM role is an identity with permissions that is assumed for a short time by a user, an application, or a service, and it is the preferred way to give a workload access without embedding permanent credentials in code. An IAM policy is a document that states what actions are allowed or denied on which resources, and policies can be attached to users, groups, and roles. The guiding rule is least privilege: give each identity only the permissions it needs for its job, and nothing more. Start narrow, review access as jobs change, and remove permissions that are no longer used.
Protecting sign in matters as much as granting the right permissions. Multifactor authentication, or MFA, adds a second factor beyond a password, such as a code from an authenticator app or a hardware key, and it should be enabled for privileged users. The root user needs special care. It is the identity created when the account is first opened, it has complete access, and it cannot be limited in the normal way that IAM users can. Enable MFA on the root user, use a strong password, do not create root access keys for routine work, and do not use it for daily tasks. Reserve it only for the few account level tasks that truly require it, and use IAM users and roles for everything else. At recognition level, IAM Access Analyzer helps you find resources shared with external accounts or accessible from outside your account, so unintended access can be reviewed. For companies with many accounts, AWS Organizations lets you manage accounts together, and service control policies, or SCPs, set the maximum permissions that accounts in part of that structure can use. An SCP is a guardrail: it can limit what administrators in a member account can allow, but it does not grant permissions by itself.
2.4 Identify components and resources for security
This objective is a recognition test for the main security services and what each one does. AWS WAF is a web application firewall that filters web requests by rules you set, helping block common web attacks before they reach an application. AWS Shield protects against distributed denial of service attacks that try to overwhelm a site or service with traffic, with a standard level included for supported resources and an advanced level for larger protection needs. Amazon Inspector scans supported workloads, including Amazon EC2 instances, container images, and Lambda functions, for software vulnerabilities and unintended network exposure. AWS Key Management Service, or AWS KMS, creates and controls encryption keys used to protect data at rest and supports auditing of key use. Amazon GuardDuty is a threat detection service that analyzes account and network activity to flag findings that may indicate compromised credentials, unusual behavior, or malicious activity. Amazon Macie focuses on data protection in Amazon S3: it discovers sensitive data, such as personal information, so you can review where it lives and how it is protected. When a question asks where to learn more, look for official security documentation and whitepapers that AWS publishes. Match the service to the job in the stem: filtering web requests points to WAF, denial of service points to Shield, vulnerability scanning points to Inspector, encryption keys point to KMS, threat findings point to GuardDuty, and sensitive data discovery in S3 points to Macie.
Worked example
A help desk technician is learning about the AWS shared responsibility model. Which task is AWS responsible for under security OF the cloud?
AWS is responsible for security OF the cloud, which includes physical facilities, hardware, and global infrastructure. Customers handle security IN the cloud for their own workloads.
Why the other options are wrong
- AConfiguring security groups for an Amazon EC2 instance: Security group configuration is a customer responsibility for their EC2 instances.
- CPatching the guest operating system on an EC2 instance: The customer patches the guest operating system on EC2 because AWS does not manage that layer for IaaS services.
- DManaging user access with IAM policies: Creating and managing IAM users and policies is done by the customer who owns the account.
Acronyms and terms in this domain
| Term | What it means |
|---|---|
| IAM | Identity and Access Management, the service that controls users, groups, roles, and policies in an account |
| MFA | Multifactor Authentication, sign in using two or more factor types to verify identity |
| WAF | Web Application Firewall, a filter for web requests based on rules you define |
| KMS | Key Management Service, the service that creates and controls encryption keys |
| SCP | Service Control Policy, a guardrail in AWS Organizations that sets the maximum permissions for accounts |
| Artifact | AWS Artifact, the portal for compliance reports and agreements from AWS |
| CloudTrail | AWS CloudTrail, the service that records API activity for auditing and investigation |
| Config | AWS Config, the service that records resource configuration history and evaluates it against rules |
| GuardDuty | Amazon GuardDuty, the threat detection service that flags suspicious account and network activity |
| Least privilege | The practice of granting only the permissions an identity needs to do its job, and nothing more |
Where the help desk meets this domain
You meet this domain in access tickets long before you meet it in an exam room. A new hire needs an account, a user changes teams and needs different permissions, a contractor should lose access on a set date, and someone is locked out because MFA was set up on an old phone. Each ticket is IAM in daily form. The lesson behind least privilege is familiar too: you do not give every user administrator rights just because it is faster, and you do not leave shared accounts in place when a named account with the right group membership would do the job with a clear record. When you help a user enroll in MFA, reset a factor after a phone replacement, or explain why a sign in was denied by policy, you are doing the access management work that Domain 2 describes.
Security services also reach the desk as alerts and escalations. A GuardDuty finding or a CloudTrail record may start as a ticket that asks who did something, when it happened, and whether it was expected, and your job is often to gather the account name, time, resource, and requester details before the ticket moves to a security or cloud team. A report about a web site that is slow during an attack, a scan result that lists a server that needs patching, or a warning about sensitive files in the wrong place all connect to the services in objective 2.4. If you practice naming the control behind the ticket, such as access, logging, encryption, or data discovery, the exam choices become easier to sort.
Traps to watch for
The central trap in this domain is shared responsibility, and the most tested form is who patches what. If a question names Amazon EC2, the customer patches the guest operating system and the applications on the instance, even though AWS maintains the physical host underneath it. Do not move that duty to AWS just because the server runs in an AWS data center. If the question names a managed service such as Amazon RDS, AWS patches the database software and the underlying operating system, so an answer that makes the customer patch that managed layer is wrong. With AWS Lambda, AWS patches the runtime environment and the servers as well, while the customer still owns the code and its permissions. A second form of the same trap swaps the two halves of the model. Physical security, hardware replacement, and global infrastructure are always security OF the cloud. Data protection choices, IAM settings, security group rules, and encryption choices are security IN the cloud. When a choice assigns your configuration work to AWS, or assigns facility work to the customer, it is testing this split directly.
The root user creates the other trap you should expect. Questions may describe daily work being done with the root user because it is convenient, because it has all permissions, or because a small team shares it. That is the wrong pattern in every case. The root user has complete access, it should have MFA enabled, it should not have access keys used for routine work, and it should be used only for the limited account tasks that require root. Daily administration belongs to IAM users and roles with least privilege permissions, often through groups so access can be reviewed and removed cleanly. Watch for related traps as well. An SCP does not grant access, it only sets a ceiling for what can be allowed. CloudTrail and Config are also easy to swap: CloudTrail answers who called which API and when, while Config answers how a resource was configured and how it changed. Name the job in the stem before you read the choices, and those pairs are harder to confuse.
Now try it. The 5 free sample questions for this domain are in practice mode, with full explanations.
Practice Domain 2 questions