Amazon Inspector integration

Overview

Amazon Inspector (formerly AWS Inspector) is a vulnerability management service provided by AWS that automatically scans AWS workloads such as EC2 instances, container images in Amazon ECR, and Lambda functions for known software vulnerabilities and unintended network exposure.

This connector retrieves vulnerability findings using the ListFindings from AWS Inspector2 APIs from Amazon Inspector such as CVEs, affected resources, severity ratings, and descriptions. These findings can be used for monitoring and threat detection on DNIF console.

Prerequisites

• Access to the AWS Console with permissions to create IAM users and assign policies
• AWS Inspector must be enabled in your target region
• Bloo platform access credentials

Configuration Steps

1. Create IAM User and Policy

1. Log in to the AWS Console and go to IAM (Identity and Access Management)
2. Navigate to the IAM (Identity and Access Management) service
3. Create a new IAM user with Programmatic Access enabled
4. Attach the policy: AmazonInspector2ReadOnlyAccess
5. Download the .csv file containing the Access Key ID and Secret Access Key

2. Configure Connector Settings

Use the form fields to provide the following details:

Field	Description
Connector Name	A descriptive name for the connector instance
AWS Region	The AWS region where Inspector is configured (e.g., us-east-1)
AWS Access Key	IAM user's Access Key ID
AWS Secret Key	IAM user's Secret Access Key

3. Test Connection

1. Click Save, then click Test Connection to validate credentials
2. On successful validation, you will receive a confirmation message with timestamp
3. If validation fails, review the credentials or refer to Troubleshooting Connector Validations

Supported AWS Workloads

• EC2 Instances: Vulnerability scanning for Amazon EC2 instances
• ECR Container Images: Container image vulnerability assessment
• Lambda Functions: Serverless function security analysis
• Network Exposure: Detection of unintended network exposure

Security Considerations

• Use IAM policies with minimal required permissions
• Regularly rotate AWS access keys
• Monitor API usage and costs
• Enable AWS CloudTrail for audit logging
• Store credentials securely

Troubleshooting

For additional help, refer to:

• Troubleshooting Connector Validations
• AWS Inspector API documentation
• AWS IAM best practices
• Bloo platform support documentation