Configure Vulnerability 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 resources. 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 Resource page.
- GuardDuty is currently supported only for AWS standalone and member accounts onboarded on Prisma Cloud.
- Enable EventBridge before you configure vulnerability findings using GuardDuty or Inspector.
- If you are currently using Inspector Classic, you do not need to make any configuration changes and can continue to use it as is.
- Onboard your AWS account.
- Configure near real-time visibility through Amazon EventBridge.
- Configure vulnerability findings.
- Editthe AWS account for which you want to configure vulnerability findings. Make sure that EventBridge is successfully configured for that account.
- On the Account Overview page, scroll toVulnerability Findings.
- ToggleDisabledtoEnabledand clickConfigure Findings.Enableboth GuardDuty and Inspector.
- Download EventBridge CFT.
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. - Log in to your AWS account and follow the steps to create a stack, selectI acknowledge that AWS CloudFormation might create IAM resources with custom names., and clickCreate Stack.
- Wait for status to display CREATE_COMPLETE.
- Return to your Prisma Cloud console and clickNext.
- Once the template is run successfully,Review StatusdisplaysSuccessfulfor each region.
If a Warning status displays for a region(s), clickConfigure Details, download the CFT again, and complete the steps. - ClickSave.
- Once aSuccessfulmessage displays forVulnerability Findingson the account overview page.You can view the vulnerability and malware findings generated by AWS GuardDuty or vulnerabilities generated by AWS Inspector on the Prima CloudInvestigatepage.config from cloud.resource where api.name = 'aws-iam-list-access-keys' AND finding.source = 'AWS GuardDuty'
