← Back to Home

Security & Compliance

AWS Security Services, Encryption, Compliance & Threat Detection

AWS Shared Responsibility Model

Security and compliance is a shared responsibility between AWS and the customer.

AWS Responsibility (OF the Cloud)Customer Responsibility (IN the Cloud)
Physical security of data centersIAM users, groups, roles, policies
Hardware & infrastructure maintenanceEncryption of data at rest & in transit
Managed services patching (RDS, Lambda, etc.)OS patching on EC2, firewall config
Network infrastructure, hypervisorSecurity group & NACL rules
Global infrastructure (regions, AZs, edge)Application-level security, customer data

Shared Controls

Exam Tip:

For RDS: AWS manages the underlying OS and database patching. Customer manages the data, query optimization, and security group rules. For EC2: Customer is responsible for everything above the hypervisor (OS, patching, applications).

DDoS Protection

AWS Shield Standard

AWS Shield Advanced

Key Point:

Shield Standard = free, automatic, L3/L4. Shield Advanced = paid, DRT support, cost protection, L7 mitigation.

AWS WAF (Web Application Firewall)

Rule Types

Exam Tip:

WAF = Layer 7 (HTTP). Shield = Layer 3/4 (network). If the question mentions SQL injection, XSS, or rate limiting, choose WAF. If it mentions DDoS, choose Shield.

AWS Network Firewall

Encryption Services

AWS KMS (Key Management Service)

AWS CloudHSM

AWS Certificate Manager (ACM)

Key Point:

KMS = AWS manages hardware, you manage keys. CloudHSM = you manage both the hardware and keys. ACM = free TLS certs with auto-renewal.

AWS Artifact

Exam Tip:

If the exam asks where to find AWS compliance reports or security certifications, the answer is AWS Artifact.

Threat Detection & Security Services

Amazon GuardDuty

Amazon Inspector

AWS Config

Amazon Macie

Amazon Detective

AWS Security Hub

Exam Tip:

GuardDuty = threat detection (analyzes logs). Inspector = vulnerability scanning (EC2/ECR/Lambda). Config = configuration compliance. Macie = sensitive data in S3. Detective = investigate root cause. Security Hub = central dashboard for all findings.

AWS Abuse & Penetration Testing

AWS Abuse

Penetration Testing

Allowed (8 services)Not Allowed
Amazon EC2, NAT Gateways, ELBDNS zone walking via Route 53
Amazon RDSDDoS attacks (or simulated)
Amazon CloudFrontPort flooding
Amazon AuroraProtocol flooding
Amazon API GatewayRequest flooding (login, API)
AWS Lambda & Lambda Edge
Amazon Lightsail
Amazon Elastic Beanstalk
Key Point:

You can pen-test 8 AWS services without prior approval. You can NEVER simulate DDoS, port/protocol flooding, or DNS zone walking.