GuardDuty for threat detection in AWS - Mini Project: Build & Apply

GuardDuty for threat detection

📖 Scenario: You are a cloud security engineer setting up threat detection for your AWS environment. You want to enable GuardDuty, a service that continuously monitors for malicious or unauthorized behavior to protect your AWS accounts and workloads.

🎯 Goal: Enable AWS GuardDuty in your AWS account and configure it to monitor your environment for potential security threats.

📋 What You'll Learn

Create a GuardDuty detector

Enable GuardDuty with default settings

Verify the detector is active

💡 Why This Matters

🌍 Real World

GuardDuty helps detect threats like unusual API calls or unauthorized access in your AWS environment, improving security.

💼 Career

Cloud security engineers and AWS administrators use GuardDuty to monitor and protect cloud resources from attacks and vulnerabilities.

1

Create a GuardDuty detector

Write the AWS CLI command to create a GuardDuty detector and save the output to a variable called detector. Use the command aws guardduty create-detector --enable.

AWS

# Use AWS CLI to create GuardDuty detector and assign to detector
# Your code here

Hint

Use the AWS CLI command aws guardduty create-detector --enable and capture the DetectorId output.

2

Check GuardDuty detector status

Write the AWS CLI command to get the status of the GuardDuty detector using the variable detector. Use aws guardduty get-detector --detector-id $detector.

AWS

detector=$(aws guardduty create-detector --enable --query 'DetectorId' --output text)
# Check the status of the GuardDuty detector
# Your code here

Hint

Use the AWS CLI command aws guardduty get-detector --detector-id $detector to check the detector status.

3

Enable GuardDuty findings publishing

Write the AWS CLI command to enable publishing of GuardDuty findings to CloudWatch Logs for the detector stored in detector. Use aws guardduty create-publishing-destination with appropriate parameters.

AWS

detector=$(aws guardduty create-detector --enable --query 'DetectorId' --output text)
aws guardduty get-detector --detector-id $detector
# Enable publishing of findings to CloudWatch Logs
# Your code here

Hint

Use aws guardduty create-publishing-destination with --detector-id $detector and --destination-type CLOUDWATCH_LOGS.

4

Verify GuardDuty is active and monitoring

Write the AWS CLI command to list all active GuardDuty detectors and confirm your detector $detector is listed. Use aws guardduty list-detectors.

AWS

detector=$(aws guardduty create-detector --enable --query 'DetectorId' --output text)
aws guardduty get-detector --detector-id $detector
aws guardduty create-publishing-destination --detector-id $detector --destination-type CLOUDWATCH_LOGS --destination-properties logGroupArn=arn:aws:logs:us-east-1:123456789012:log-group:GuardDutyLogs
# List all active GuardDuty detectors
# Your code here

Hint

Use aws guardduty list-detectors to see all active detectors.

Practice

1. What is the main purpose of AWS GuardDuty?

easy

A. To manage user permissions and access control

B. To automatically detect threats and suspicious activity in your AWS environment

C. To store and backup data securely

D. To deploy applications automatically

Solution

1. Step 1: Understand GuardDuty's role

   GuardDuty is a security service that watches your AWS environment for threats.

2. Step 2: Compare options

   Only To automatically detect threats and suspicious activity in your AWS environment describes threat detection, which is GuardDuty's main function.

3. Final Answer:

   To automatically detect threats and suspicious activity in your AWS environment -> Option B

4. Quick Check:

   GuardDuty = Threat detection [OK]

Hint: GuardDuty = automatic threat detection service [OK]

Common Mistakes:

• Confusing GuardDuty with access management
• Thinking GuardDuty stores data
• Assuming GuardDuty deploys apps

2. Which AWS service must be enabled to start using GuardDuty?

easy

A. AWS CloudTrail

B. AWS IAM

C. AWS Config

D. Amazon GuardDuty

Solution

1. Step 1: Identify the service to enable

   GuardDuty is a separate AWS service that must be enabled to start threat detection.

2. Step 2: Check other services' roles

   CloudTrail logs events, Config tracks resource changes, IAM manages permissions, but none start GuardDuty.

3. Final Answer:

   Amazon GuardDuty -> Option D

4. Quick Check:

   Enable GuardDuty service to start detection [OK]

Hint: Enable GuardDuty service itself to start detection [OK]

Common Mistakes:

• Confusing CloudTrail with GuardDuty
• Thinking IAM enables GuardDuty
• Assuming Config starts GuardDuty

3. After enabling GuardDuty, which of the following best describes what happens next?

medium

A. GuardDuty disables CloudTrail to reduce noise

B. You must manually upload logs for GuardDuty to analyze

C. GuardDuty immediately starts analyzing AWS logs and network activity for threats

D. GuardDuty automatically deletes suspicious resources

Solution

1. Step 1: Understand GuardDuty's automatic behavior

   GuardDuty automatically analyzes AWS logs and network data once enabled.

2. Step 2: Evaluate other options

   Manual log upload is not needed, CloudTrail is not disabled, and GuardDuty does not delete resources.

3. Final Answer:

   GuardDuty immediately starts analyzing AWS logs and network activity for threats -> Option C

4. Quick Check:

   GuardDuty auto-analyzes logs after enablement [OK]

Hint: GuardDuty auto-analyzes logs; no manual upload needed [OK]

Common Mistakes:

• Thinking manual log upload is required
• Believing GuardDuty disables CloudTrail
• Assuming GuardDuty deletes resources

4. You enabled GuardDuty but are not receiving any findings. What is a likely cause?

medium

A. GuardDuty is not enabled in the correct AWS region

B. You forgot to create an IAM user

C. CloudTrail is disabled globally

D. GuardDuty requires manual log uploads

Solution

1. Step 1: Check GuardDuty regional enablement

   GuardDuty must be enabled in each AWS region to detect threats there.

2. Step 2: Review other options

   IAM user creation is unrelated to findings, CloudTrail is enabled by default in most regions, and GuardDuty does not require manual uploads.

3. Final Answer:

   GuardDuty is not enabled in the correct AWS region -> Option A

4. Quick Check:

   GuardDuty region enablement affects findings [OK]

Hint: Enable GuardDuty in the right region to get findings [OK]

Common Mistakes:

• Assuming IAM user creation triggers findings
• Believing CloudTrail must be manually enabled everywhere
• Thinking GuardDuty needs manual log uploads

5. You want to monitor multiple AWS accounts for threats centrally using GuardDuty. What is the best approach?

hard

A. Use GuardDuty's multi-account feature with a master account to manage findings centrally

B. Enable GuardDuty separately in each account and region, then aggregate findings manually

C. Create IAM roles in each account to share logs with a central S3 bucket for GuardDuty analysis

D. Disable GuardDuty in member accounts and rely on CloudTrail logs only

Solution

1. Step 1: Understand GuardDuty multi-account setup

   GuardDuty supports a master account that can manage and view findings from member accounts centrally.

2. Step 2: Evaluate other options

   Manual aggregation is inefficient, sharing logs via S3 is not how GuardDuty works, and disabling GuardDuty loses threat detection.

3. Final Answer:

   Use GuardDuty's multi-account feature with a master account to manage findings centrally -> Option A

4. Quick Check:

   GuardDuty multi-account = master account management [OK]

Hint: Use GuardDuty master account for multi-account threat management [OK]

Common Mistakes:

• Trying manual aggregation of findings
• Using S3 buckets for GuardDuty log sharing
• Disabling GuardDuty in member accounts