> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/administration/configure-external-integrations-on-prisma-cloud/integrate-prisma-cloud-with-amazon-guardduty.md).

# Integrate Prisma Cloud with Amazon GuardDuty

Learn how to integrate Prisma® Cloud with Amazon GuardDuty.

Amazon GuardDuty is a continuous security monitoring service that analyzes and processes Virtual Private Cloud (VPC) Flow Logs and AWS CloudTrail event logs. GuardDuty uses security logic and AWS usage statistics techniques to identify unexpected and potentially unauthorized and malicious activity.

Prisma® Cloud integrates with GuardDuty and extends its threat visualization capabilities. Prisma Cloud starts ingesting GuardDuty data, correlates it with the other information that Prisma Cloud already collects, and presents contextualized and actionable information through the Prisma Cloud app.

1. Enable Amazon GuardDuty on your AWS instances (see [Amazon Documentation](https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_settingup.html)).
2. Enable read-access permissions to Amazon GuardDuty on the IAM Role policy.

   The Prisma Cloud IAM Role policy you use to onboard your AWS setup needs to include these permissions:

   * `guardduty:List`
   * `guardduty:Get`

     tt:\[NOTE] If you used the CFT templates to onboard your AWS account, the Prisma Cloud IAM Role policy already has the permissions required for Amazon GuardDuty.
3. After Prisma Cloud has access to the Amazon GuardDuty findings, use RQL queries for visibility into the information collected from Amazon GuardDuty.
   1. Navigate to **Investigate > Search** page.
   2. To search for **Config Query**, enter the following RQL query.

      ```
      config from cloud.resource where cloud.type = 'aws' AND finding.type = 'AWS GuardDuty Host'
      ```

      The query returns a list of affected assets for further investigation. Select an asset to view the **Finding Types** side panel. The panel lists threats or security issues associated with the asset.

      tt:\[NOTE] Prisma Cloud supports only EC2 and IAM finding types for GuardDuty.

      <figure><img src="/files/Pz2N0UDXTdmqlWUOHzgl" alt="guardduty audit trail"><figcaption></figcaption></figure>

      Click **Findings** for information related to vulnerabilities. Select **AWS GuardDuty Host** or **AWS GuardDuty IAM** in the filter to view vulnerabilities detected by AWS GuardDuty.

      <figure><img src="/files/7HDgELH8ga7ielAFZDTK" alt="guardduty host findings"><figcaption></figcaption></figure>

      ```
      config from cloud.resource where api.name = 'aws-iam-list-access-keys' AND finding.source = 'AWS Guard Duty'
      ```
   3. To search for **Network Query**, enter the following RQL query.

      ```
      network from vpc.flow_record where dest.resource IN ( resource where finding.type = 'AWS GuardDuty Host' )
      ```

      The query returns a visual representation of the assets for further investigation.

      <figure><img src="/files/EAHrep3pHSCwff3Cqqru" alt="guardduty network query"><figcaption></figcaption></figure>


---

# 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://docs.prismacloud.io/content-collections/administration/configure-external-integrations-on-prisma-cloud/integrate-prisma-cloud-with-amazon-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.