> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Demo GuardDuty Alerts

> Guide to enable AWS GuardDuty, generate sample findings, inspect and triage alerts, and apply filters, suppression rules, and remediations for safe threat detection

In this guide you'll learn how to enable AWS GuardDuty, generate sample findings, and inspect resulting alerts in the AWS console. This walkthrough is optimized for clarity and quick reference, with practical tips for safe testing and investigation.

## What is GuardDuty?

AWS GuardDuty is a managed threat detection service that continuously monitors for malicious or unauthorized behavior across your AWS accounts and workloads. When enabled, GuardDuty aggregates telemetry (API logs, VPC flow logs, DNS logs, etc.), applies threat intelligence and machine learning, and surfaces prioritized findings so you can quickly triage and remediate risk.

Enable GuardDuty in non-production accounts if you want to safely explore findings. You can also use GuardDuty’s sample findings feature to practice investigation without generating real attacks.

## Enable GuardDuty

1. Open the AWS Management Console and search for “GuardDuty” (typing “Guard” is sufficient).
2. Click Get started and review required permissions and features.
3. Select Enable GuardDuty to begin a free 30-day trial (if applicable) and start collecting findings.

Once enabled, GuardDuty presents a summary dashboard that prioritizes findings by severity (High, Medium, Low), highlights top threats, shows attack sequences, and lists resources/accounts with the most findings.

![Screenshot of an AWS GuardDuty Summary console. The left column lists several critical findings (e.g., potential S3 and credential compromises) and the right shows a pie chart of threat categories.](https://mintcdn.com/kodekloud-c4ac6d9a/pbGljLCZ83hel575/images/AWS-Certified-DevOps-Engineer-Professional/Domain-6-Security-and-Compliance/Demo-GuardDuty-Alerts/aws-guardduty-summary-findings-pie-chart.jpg?fit=max\&auto=format\&n=pbGljLCZ83hel575\&q=85\&s=23cc867188f789c3a2088a9c00e6bfa2)

The dashboard gives a quick overview of:

* Counts (attack sequences, total findings, resource findings, account findings)
* Visual breakdown of common finding types and categories
* Prioritized list of high-severity findings for immediate triage

You can filter the dashboard by severity or resource type (for example, show only EC2-related findings to focus on compute compromises).

![Screenshot of the AWS GuardDuty Summary page showing multiple critical findings on the left and a "Resources with most findings" list on the right with instance and cluster entries. The left column shows repeated "Potential EC2 instance group compromise" alerts marked Critical.](https://mintcdn.com/kodekloud-c4ac6d9a/pbGljLCZ83hel575/images/AWS-Certified-DevOps-Engineer-Professional/Domain-6-Security-and-Compliance/Demo-GuardDuty-Alerts/guardduty-summary-critical-ec2-findings.jpg?fit=max\&auto=format\&n=pbGljLCZ83hel575\&q=85\&s=36d1b6114ab928e5354773d570c4538f)

GuardDuty supports multi-account aggregation (via AWS Organizations) and timestamps each finding so you can track when suspicious activity first and last occurred.

## Inspect Findings

Open the Findings list to see individual entries. Use built-in filters to narrow results by severity, resource type, finding ID, region, or other fields. Filters help you scope investigations or create suppression rules for noisy, low-value signals.

Selecting a finding opens a detailed pane with:

* First and last seen timestamps
* A narrative describing observed activity and attack sequence
* Signals used to generate the finding (API calls, network connections, referenced IPs)
* Indicators of technique and actors involved (principal IDs, usernames, IP addresses)
* Affected region, account, finding ID, and specific resource(s) such as an instance ID or access key

![A screenshot of the AWS GuardDuty "Finding details" page showing an account-discovery/account-manipulation finding with a finding ID, region and account. It also shows details like a connected Tor exit node, sensitive API calls, and the principal ID/username.](https://mintcdn.com/kodekloud-c4ac6d9a/pbGljLCZ83hel575/images/AWS-Certified-DevOps-Engineer-Professional/Domain-6-Security-and-Compliance/Demo-GuardDuty-Alerts/aws-guardduty-account-manipulation-tor.jpg?fit=max\&auto=format\&n=pbGljLCZ83hel575\&q=85\&s=ab560863b9c9fbf9765ca0381c9dcf34)

Example signals you might see:

* `CreateRole` requests from unusual IP ranges (e.g., Tor exit nodes)
* `AttachRolePolicy` calls originating from compromised endpoints
* `DeleteTrail` used to evade logging and detection

![A screenshot of the AWS GuardDuty console showing a critical finding titled "Potential credential compromise of IAMUser/john\_doe" with an Actions button. The page displays finding details and tabs for Signals and Resources, and the account/organization name in the header.](https://mintcdn.com/kodekloud-c4ac6d9a/pbGljLCZ83hel575/images/AWS-Certified-DevOps-Engineer-Professional/Domain-6-Security-and-Compliance/Demo-GuardDuty-Alerts/aws-guardduty-credential-compromise-iamuser.jpg?fit=max\&auto=format\&n=pbGljLCZ83hel575\&q=85\&s=2a9fc8e4326923ffde4e7edc3ac633e7)

## Generate Sample Findings (safe testing)

If you prefer not to perform real-world attacks in your environment, use GuardDuty’s Sample findings to populate the Findings list with representative alerts for UI exploration and playbooks.

Steps:

1. In GuardDuty, open Settings.
2. Scroll to the Sample findings section.
3. Click Generate sample findings and confirm.

GuardDuty will create sample findings across severities and categories. These populate the dashboard and Findings list so you can practice investigation, filtering, suppression rules, and export workflows.

![A screenshot of the AWS GuardDuty console showing the "Findings" page with 434 findings and an open filter dropdown listing options like "Kubernetes API caller IPv4 address" and "Network connection." The page also shows buttons for "Create suppression rule" and "Actions."](https://mintcdn.com/kodekloud-c4ac6d9a/pbGljLCZ83hel575/images/AWS-Certified-DevOps-Engineer-Professional/Domain-6-Security-and-Compliance/Demo-GuardDuty-Alerts/guardduty-findings-434-filter-dropdown.jpg?fit=max\&auto=format\&n=pbGljLCZ83hel575\&q=85\&s=fbeba836d782269a04376220248d0ae4)

Use filters such as "Kubernetes API caller IPv4 address" or "Network connection" to pinpoint specific telemetry sources. You can also:

* Create suppression rules for known harmless noise
* Export findings for SIEM ingestion or further analysis
* Trigger automated remediation (via Lambda, Systems Manager, etc.)

Do not run offensive tests (actual attacks) in production. Use sample findings or dedicated test accounts to avoid accidental disruption and preserve audit trails.

## Common Finding Types and Suggested Remediations

| Finding Category | Typical Signals | Example Remediation |
| - | -: | - |
| Credential compromise | `ConsoleLogin`, `CreateAccessKey`, unusual source IPs | Rotate keys, revoke sessions, enable MFA |
| EC2 compromise / Suspicious runtime | Unusual network connections, known malicious IPs | Isolate instance, snapshot for forensics, rebuild |
| Privilege escalation / IAM abuse | `CreateRole`, `AttachRolePolicy` | Review and remove malicious roles/policies, tighten IAM policies |
| Account enumeration / reconnaissance | `ListBuckets`, `DescribeInstances` from foreign IPs | Enforce least privilege, restrict access from risky IPs |

## Quick Links and References

* GuardDuty product docs: [https://docs.aws.amazon.com/guardduty/](https://docs.aws.amazon.com/guardduty/)
* AWS Security best practices: [https://aws.amazon.com/architecture/security-identity-compliance/](https://aws.amazon.com/architecture/security-identity-compliance/)

## Summary / Key Takeaways

* GuardDuty offers prioritized, account-wide threat detection and correlates telemetry into meaningful findings.
* Use the dashboard for rapid triage and the Findings list for deep investigation.
* Generate sample findings to practice safely.
* Apply filters, suppression rules, and automated remediation as part of your incident response process (rotate keys, isolate instances, update IAM policies, etc.).

That covers enabling GuardDuty, creating sample findings, and inspecting alerts in the console.

> **[Watch Video](https://learn.kodekloud.com/user/courses/aws-certified-devops-engineer-professional/module/d51f4260-d612-4dcb-9a91-4eeb6540c6c7/lesson/437a69e3-2a94-4af1-8bf8-510088faa88c)**


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.