AWS CLOUD CERTIFICATIONS

AWS Security and Compliance Basics: IAM, Encryption & Shared Responsibility

15,000+
Professionals Certified
30% Exam Weightage
on Security & Compliance
2nd-Highest
Weighted Domain

The Security and Compliance section is the second-highest weightage, but is the least secure area for candidates in the CLF-C02 exam. IAM, encryption, compliance programs and the shared responsibility model are explained in a simple manner and this high value domain becomes one of your strongest, not weakest, assets.

Quick Answers

AWS Security and Compliance is a CLF-C02 domain that focuses on identity and access management (IAM), data protection and encryption, AWS's compliance program, and the shared responsibility model that outlines what AWS secures and what you secure. This is the second most important domain with exam weightage of approximately 30% after Cloud Technology and Services. The exam isn't about memorizing all the security services that AWS provides; instead, it's about understanding the concept of security as a shared responsibility and applying IAM and encryption concepts to real-life examples.

Key Takeaways

1

The shared responsibility model is 'of the cloud' for AWS, 'in the cloud' for you.

2

IAM (Identity and Access Management) regulates access to what in your AWS account.

3

AWS provides both encryption at rest and in transit as protection for data.

4

AWS Artifact offers access to compliance reports and certifications on-demand.

5

Exam security questions are scenario based, requiring judgement rather than recall.

IAM and the Shared Responsibility Model Explained

Identity and Access Management (IAM) provides the foundation of AWS security, and is used to govern access to your AWS resources and the actions you can take. IAM is based on the principle of "least privilege" (giving users and services what they need, no more) and leverages users, groups, roles, and policies to grant permissions. Multi-Factor Authentication (MFA) is another layer of security beyond a username and password, and root account best practices state never to use the root user for day-to-day operations, using IAM users with just the right level of permissions instead. It's all about the shared responsibility model: AWS is responsible for the underlying infrastructure (data centers, hardware, networking, etc.), while you are responsible for getting IAM configured properly, managing your data and controlling access. This is one of the most frequent exam pitfalls as students tend to think that AWS takes on more responsibility for security than it actually does.

Encryption and Compliance Programs

Currently, there are two fundamental concepts of data protection on AWS: data at rest (when data resides on S3 or EBS volumes) and data in transit (when data is moving between networks, usually through SSL/TLS). AWS Key Management Service (KMS) is a service that lets you create and manage the encryption keys you use with these services. On the compliance side, AWS has many certifications and attestations, such as ISO standards, SOC reports, and industry-specific certifications like HIPAA and PCI DSS, available and accessible via a self-service portal on AWS called AWS Artifact. As with the other regions of this domain, compliance is a shared responsibility, and AWS makes its infrastructure compliant, but you must configure and use it properly.

Skills Needed to Master Security and Compliance

→

A real security scenario using the shared responsibility model

→

Identifying IAM concepts: users, groups, roles, and policies, MFA

→

The difference between encryption at rest and encryption in transit

→

Understanding how to access AWS compliance documentation (AWS Artifact)

→

Understanding the concept of ‘least privilege' in access control situations.

Key Security Concepts Covered in CLF-C02

IAM users, groups, roles, and policies
Multi-Factor Authentication (MFA)
Root account best practices
Encryption at rest and in transit
AWS Key Management Service (KMS)
AWS Artifact for compliance reports
AWS Shield and AWS WAF (basic awareness level)

Security Responsibilities at a Glance

ResponsibilityOwned ByExample
Physical data center securityAWSFacility access controls, hardware security
Network infrastructureAWSGlobal network, edge locations
Data encryption configurationCustomerEnabling encryption on S3 buckets
Identity and access managementCustomerSetting up IAM users, roles, and policies
Compliance documentation accessAWS (provides), Customer (uses)AWS Artifact reports
Operating system patching (IaaS)CustomerPatching an EC2 instance's OS

Step-by-Step Roadmap to Mastering Security and Compliance

1

Start with the shared responsibility model, it is the basics of this domain.

2

Learn the concepts of IAM - Users, Groups, Roles, Policies and MFA with examples.

3

Know the difference between encryption at rest and encryption in transit, and the role of KMS.

4

Use AWS Artifact to learn how to access compliance documentation.

5

Practice questions with scenarios to determine if a task is AWS or customer driven.

6

Review areas of weakness from AWS's official security documentation prior to final mock exams.

Book Your Free Counselling Session

Still unsure where AWS's responsibility ends and yours begins?

Learn about the shared responsibility model and the fundamentals of IAM clearly and concisely from a cloud expert, through scenarios similar to actual exam questions

and strengthen your weakest domain!

Expert Insights

“

For mentors who closely follow candidate performance, it becomes clear that Security and Compliance errors are rarely a result of not knowing a term; it's a result of incorrect application of the shared responsibility model in the scenario questions. Candidates who read the definitions only, do not usually do well in this domain, but those who practice sorting responsibilities into the AWS and Customer columns repeatedly come out good.

FAQs

It's a model based on the division of security responsibilities between AWS, which protects the underlying cloud infrastructure, and the customer whose data, access parameters and applications are secured.