> For the complete documentation index, see [llms.txt](https://notebook.iuriioapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notebook.iuriioapps.com/cloud/aws/security_and_compliance/guardduty.md).

# GuardDuty

* It is a managed threat detection service
* Continuously monitors multiple AWS accounts for malicious activity or unusual behavior
* Detection types
  * Reconnaissance attacks - brute force, port scans, port probes, etc
  * Instance compromises - malicious communications, spambot activities, outbound SSH brute force attacks, EC2 credential exfiltration, etc
  * Account compromises - malicious API calls, disabled CloudTrail, password compromises
* Simple dashboard view
* CloudWatch event triggers, with further partner integrations: Splunk, CrowdStrike, SumoLogic, etc.
* Behavioral anomalies
* Monitors CloudTrail, VPC flow logs and more
* Continually updated
  * Public Security intelligence feeds
  * Malicious IP addresses
  * Partner intelligence feeds
  * Machine learning models
  * Abnormal behavior


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://notebook.iuriioapps.com/cloud/aws/security_and_compliance/guardduty.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
