Security pillar principles in AWS - Mini Project: Build & Apply

Understanding AWS Security Pillar Principles

📖 Scenario: You are starting a new cloud project on AWS. To keep your project safe, you need to understand the basic security principles AWS recommends. These principles help protect your data and control who can access your resources.

🎯 Goal: Build a simple AWS IAM policy document that follows the core security pillar principles: least privilege, strong identity management, and data protection.

📋 What You'll Learn

Create a JSON IAM policy with specific permissions

Add a condition to restrict access by IP address

Use a variable to define allowed actions

Complete the policy with a version and statement structure

💡 Why This Matters

🌍 Real World

AWS IAM policies control who can do what in your cloud environment. Understanding how to write them helps keep your cloud resources safe.

💼 Career

Cloud security roles require knowledge of IAM policies to enforce secure access and protect data.

1

Create the base IAM policy structure

Create a variable called policy and assign it a dictionary with the key Version set to "2012-10-17" and an empty list for the key Statement.

AWS

# Create the base IAM policy structure
# Your code here

Hint

Start by making a dictionary with keys Version and Statement. The version is a fixed date string. The statement is an empty list for now.

2

Define allowed actions for least privilege

Create a list called allowed_actions with the exact strings "s3:GetObject" and "s3:PutObject" to limit permissions to only these actions.

AWS

policy = {
    "Version": "2012-10-17",
    "Statement": []
}
# Define allowed actions for least privilege
# Your code here

Hint

Make a list named allowed_actions with exactly these two strings to follow least privilege.

3

Add a statement with conditions to the policy

Add a dictionary to policy["Statement"] with keys: Effect set to "Allow", Action set to allowed_actions, Resource set to "arn:aws:s3:::example-bucket/*", and Condition that restricts access to IP addresses starting with "203.0.113." using "IpAddress" and "aws:SourceIp".

AWS

policy = {
    "Version": "2012-10-17",
    "Statement": []
}
allowed_actions = ["s3:GetObject", "s3:PutObject"]
# Add a statement with conditions to the policy
# Your code here

Hint

Use append to add a statement dictionary with the keys and values exactly as described. The condition limits access by IP range.

4

Complete the IAM policy with version and statement

Ensure the policy dictionary includes the Version key set to "2012-10-17" and the Statement list with the permission statement you added. This completes the valid IAM policy document.

AWS

policy = {
    "Version": "2012-10-17",
    "Statement": []
}
allowed_actions = ["s3:GetObject", "s3:PutObject"]
policy["Statement"].append({
    "Effect": "Allow",
    "Action": allowed_actions,
    "Resource": "arn:aws:s3:::example-bucket/*",
    "Condition": {
        "IpAddress": {
            "aws:SourceIp": "203.0.113.0/24"
        }
    }
})
# Finalize the policy document
# Your code here

Hint

Check that the policy dictionary has the correct version and the statement list with your permission statement.

Practice

1. Which of the following is a primary goal of the AWS Security Pillar?

easy

A. Protect cloud resources from unauthorized access

B. Increase the speed of data processing

C. Reduce the cost of cloud services

D. Improve user interface design

Solution

1. Step 1: Understand the purpose of the Security Pillar

   The Security Pillar focuses on protecting cloud resources from threats and unauthorized access.

2. Step 2: Match the goal with the options

   Only Protect cloud resources from unauthorized access directly relates to protecting resources from unauthorized access, which is the main goal.

3. Final Answer:

   Protect cloud resources from unauthorized access -> Option A

4. Quick Check:

   Security Pillar = Protect resources [OK]

Hint: Security pillar means protecting resources from threats [OK]

Common Mistakes:

• Confusing security with cost or speed improvements
• Choosing options unrelated to protection
• Mixing security goals with usability goals

2. Which AWS service is primarily used to manage user access and permissions securely?

easy

A. Amazon S3

B. AWS CloudFormation

C. Amazon EC2

D. AWS Identity and Access Management (IAM)

Solution

1. Step 1: Identify the service for managing access

   AWS IAM is designed to control who can access AWS resources and what actions they can perform.

2. Step 2: Compare with other services

   Amazon S3 stores data, EC2 runs servers, CloudFormation manages infrastructure as code, but none manage user permissions directly.

3. Final Answer:

   AWS Identity and Access Management (IAM) -> Option D

4. Quick Check:

   Access control service = IAM [OK]

Hint: IAM controls user access and permissions in AWS [OK]

Common Mistakes:

• Confusing storage or compute services with access control
• Selecting services that do not handle permissions
• Ignoring the role of IAM in security

3. Consider this AWS CloudTrail configuration snippet:

{
  "TrailName": "MyTrail",
  "IsLogging": true,
  "IncludeGlobalServiceEvents": false
}

What is the effect of setting IncludeGlobalServiceEvents to false?

medium

A. Logging will be disabled for the trail

B. Global service events like IAM changes will not be logged

C. All AWS service events will be logged globally

D. Only global service events will be logged

Solution

1. Step 1: Understand the IncludeGlobalServiceEvents setting

   This setting controls whether global AWS service events (like IAM or AWS STS) are included in the logs.

2. Step 2: Interpret the false value

   Setting it to false means these global events will NOT be logged by this trail.

3. Final Answer:

   Global service events like IAM changes will not be logged -> Option B

4. Quick Check:

   IncludeGlobalServiceEvents false = no global logs [OK]

Hint: False means global events are excluded from logging [OK]

Common Mistakes:

• Assuming false disables all logging
• Confusing global events with regional events
• Thinking false means logging only global events

4. You wrote this IAM policy snippet but it does not restrict access as expected:

{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Action": "s3:*",
    "Resource": "arn:aws:s3:::example-bucket"
  }]
}

What is the main issue causing the policy to not restrict access properly?

medium

A. The Action "s3:*" is invalid syntax

B. The Effect should be Deny instead of Allow

C. The Resource ARN is missing the bucket objects path

D. The Version date is incorrect

Solution

1. Step 1: Check the Resource ARN format

   The ARN "arn:aws:s3:::example-bucket" refers only to the bucket itself, not the objects inside it.

2. Step 2: Understand access scope

   To allow or restrict access to objects, the ARN must include "/*" to cover all objects, e.g., "arn:aws:s3:::example-bucket/*".

3. Final Answer:

   The Resource ARN is missing the bucket objects path -> Option C

4. Quick Check:

   Bucket ARN needs /* for objects [OK]

Hint: Bucket ARN must include /* to cover objects [OK]

Common Mistakes:

• Using Allow instead of Deny incorrectly
• Assuming s3:* is invalid
• Ignoring the need for object path in ARN

5. You want to design a secure AWS environment that automatically detects unusual activity and isolates affected resources. Which combination of AWS services best supports this Security Pillar principle?

hard

A. AWS CloudTrail, Amazon GuardDuty, AWS Systems Manager

B. AWS Config, Amazon S3, AWS Lambda

C. Amazon EC2, AWS IAM, AWS CloudFormation

D. AWS Trusted Advisor, Amazon RDS, AWS SNS

Solution

1. Step 1: Identify services for detecting unusual activity

   Amazon GuardDuty analyzes logs and detects suspicious behavior automatically.

2. Step 2: Identify services for logging and managing resources

   AWS CloudTrail records API activity for auditing, and AWS Systems Manager helps isolate and manage affected resources.

3. Step 3: Evaluate other options

   Other options lack the combination of detection, logging, and automated management needed for this security goal.

4. Final Answer:

   AWS CloudTrail, Amazon GuardDuty, AWS Systems Manager -> Option A

5. Quick Check:

   Detect + log + isolate = CloudTrail + GuardDuty + Systems Manager [OK]

Hint: Detect threats with GuardDuty, log with CloudTrail, manage with Systems Manager [OK]

Common Mistakes:

• Choosing services that do not detect threats automatically
• Ignoring the need for logging and management together
• Confusing monitoring with storage or compute services