Ctrlk
BlogSupport
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Configure Findings

Prisma Cloud ingests findings and vulnerability data from AWS GuardDuty and Inspector, which you can use to build more meaningful insights and for vulnerability management of potentially compromised assets. Once you enable malware protection and configure it on Prisma Cloud, if malware is detected during a scan, an additional finding is generated that you can view on Prisma Cloud.

  • GuardDuty is currently supported only for AWS standalone and member accounts onboarded on Prisma Cloud.

  • Enable EventBridge before you configure findings using GuardDuty or Inspector.

  • You can use Inspector only for accounts that were onboarded as standalone accounts.

  • If you are currently using Inspector Classic, you do not need to make any configuration changes and can continue to use it as is.

  1. After you Onboard Your AWS Account, select Settings > Providers > Cloud Account.

  2. Select the View icon next to the AWS account for which you want to configure findings. Make sure that EventBridge is successfully configured for that account.

  3. Select Misconfigurations.

  4. Under Findings, toggle the Disabled button to Enabled for both GuardDuty and Inspector.

  5. Select Configure Findings.

    configure vul findings 1

  6. Configure Details.

    aws guardduty 3

    1. Select Download EventBridge Cloud Formation Template.

      As part of the initial onboarding when you deploy the EventBridge CFT, Prisma Cloud creates 2 separate rules on AWS, one each for GuardDuty and Inspector. Depending on your selection the corresponding rule is enabled.

    2. Log in to your AWS account and follow the steps to create a stack.

      • Select I acknowledge that AWS CloudFormation might create IAM resources with custom names.

      • Click Create Stack.

      • Wait for status to display CREATE_COMPLETE.

  7. Return to your Prisma Cloud console.

  8. Next.

  9. Review Status.

    Once the template is run successfully, a Successful message displays for each region.

    If a Warning status displays for a region(s), select Configure Details, download the CFT again, and complete the steps listed above.

    aws guardduty status 1

  10. Save.

    Verify that a Successful message displays for Findings on the account overview page.

    You can view the vulnerability and malware findings generated by AWS GuardDuty or vulnerabilities generated by AWS Inspector by running the following query on Investigate:

    config from cloud.resource where api.name = 'aws-iam-list-access-keys' AND finding.source = 'AWS GuardDuty'

    aws guardduty findings 1
PreviousConfigure DNS LogsNextUpdate an Onboarded AWS Organization

Last updated

Was this helpful?