GuardDuty for threat detection in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does AWS GuardDuty detect threats?

AWS GuardDuty analyzes data from various sources to detect threats. Which data source is NOT used by GuardDuty for threat detection?

A VPC Flow Logs

B AWS CloudTrail event logs

C DNS logs

D Amazon S3 bucket contents

💡 Hint

Think about what GuardDuty monitors automatically without needing to scan stored files.

GuardDuty uses network flow logs, CloudTrail logs, and DNS logs to detect suspicious activity. It does not scan the contents of S3 buckets directly.

❓ service_behavior

intermediate

GuardDuty finding behavior on EC2 instance compromise

Which GuardDuty finding type would most likely indicate that an EC2 instance is compromised and communicating with a known malicious IP?

A Recon:EC2/PortProbeUnprotectedPort

B Backdoor:EC2/C&CActivity

C UnauthorizedAccess:EC2/SSHBruteForce

D CryptoCurrency:EC2/BitcoinTool

💡 Hint

Look for findings that indicate command and control activity.

Backdoor:EC2/C&CActivity indicates that an EC2 instance is communicating with a command and control server, which is a strong sign of compromise.

❓ Architecture

advanced

GuardDuty multi-account architecture

You want to enable GuardDuty across multiple AWS accounts in your organization. What is the recommended architecture to centralize threat findings?

A Use AWS Organizations to designate a GuardDuty master account to manage findings from member accounts.

B Enable GuardDuty independently in each account without a master account.

C Deploy GuardDuty only in the root account and rely on CloudTrail aggregation for others.

D Use AWS Config rules to forward GuardDuty findings to a central S3 bucket.

💡 Hint

Think about how AWS Organizations integrates with GuardDuty for centralized management.

GuardDuty supports a master-member model using AWS Organizations, allowing centralized management and viewing of findings across accounts.

❓ security

advanced

GuardDuty finding suppression and security best practice

You receive frequent GuardDuty findings for a known benign IP address communicating with your environment. What is the best security practice to handle these findings?

A Add the IP address to a trusted IP list in GuardDuty to reduce false positives.

B Disable GuardDuty to stop receiving these findings.

C Create a suppression rule in GuardDuty to ignore findings from that IP.

D Investigate and whitelist the IP address in your firewall to prevent alerts.

💡 Hint

Consider how to reduce noise without disabling threat detection.

GuardDuty allows suppression rules to ignore specific findings temporarily or permanently, reducing noise while maintaining overall security monitoring.

❓ Configuration

expert

GuardDuty finding JSON analysis

Given this GuardDuty finding snippet, what is the value of service.action.actionType?

{
  "service": {
    "action": {
      "actionType": "NETWORK_CONNECTION",
      "networkConnectionAction": {
        "remoteIpDetails": {
          "ipAddressV4": "203.0.113.25",
          "organization": {
            "asn": 12345,
            "asnOrg": "ExampleOrg"
          }
        },
        "protocol": "TCP",
        "localPortDetails": {
          "port": 443
        },
        "remotePortDetails": {
          "port": 8080
        }
      }
    }
  }
}

A "NETWORK_CONNECTION"

B "DNS_REQUEST"

C "PORT_PROBE"

D "API_CALL"

💡 Hint

Look carefully at the JSON key actionType inside service.action.

The JSON shows "actionType": "NETWORK_CONNECTION", indicating the type of action detected by GuardDuty.

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