GuardDuty for threat detection in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is AWS GuardDuty?

AWS GuardDuty is a security service that continuously monitors your AWS accounts and workloads for malicious or unauthorized behavior to help protect your AWS environment.

intermediate

How does GuardDuty detect threats?

GuardDuty analyzes data from AWS CloudTrail logs, VPC Flow Logs, and DNS logs using machine learning, anomaly detection, and integrated threat intelligence to identify suspicious activity.

intermediate

What types of findings can GuardDuty generate?

GuardDuty findings include unauthorized access attempts, reconnaissance activities, compromised instances, and unusual API calls, helping you quickly identify potential security issues.

intermediate

Can GuardDuty be enabled across multiple AWS accounts?

Yes, GuardDuty supports multi-account management where a master account can manage and view findings from multiple member accounts for centralized threat detection.

beginner

What should you do after GuardDuty generates a finding?

After a finding, review the details in the GuardDuty console, investigate the source, and take appropriate actions such as isolating resources, updating security groups, or rotating credentials.

Which data sources does GuardDuty use to detect threats?

A IAM user passwords

B S3 bucket contents only

C EC2 instance logs only

D CloudTrail logs, VPC Flow Logs, DNS logs

GuardDuty analyzes CloudTrail logs, VPC Flow Logs, and DNS logs to detect suspicious activity.

What is the main benefit of enabling GuardDuty in your AWS account?

A Free data backup service

B Automatic patching of EC2 instances

C Continuous threat detection and alerting

D Cost optimization recommendations

GuardDuty provides continuous monitoring and alerts for potential security threats.

Can GuardDuty findings be shared across multiple AWS accounts?

A Only if accounts are in different regions

B Yes, using a master and member account setup

C No, findings are isolated per account

D Only for accounts with the same billing

GuardDuty supports multi-account management with a master account viewing findings from member accounts.

Which of the following is NOT a type of GuardDuty finding?

A EC2 instance CPU usage spikes

B Unauthorized access attempts

C Unusual API calls

D Reconnaissance activities

GuardDuty does not monitor CPU usage; it focuses on security-related findings.

What is the first step after receiving a GuardDuty finding?

A Review the finding details and investigate

B Delete the affected EC2 instance immediately

C Ignore if the finding is from a trusted IP

D Disable GuardDuty to stop alerts

You should review and investigate findings before taking further action.

Explain how AWS GuardDuty helps protect your cloud environment.

Think about what data GuardDuty looks at and what it does with that data.

Describe the process to respond to a GuardDuty threat detection finding.

Focus on steps after GuardDuty alerts you.

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