Skip to main content

​
Amazon Inspector Integration Setup

This guide walks you through integrating Amazon Inspector with RAD Security, enabling you to import code security findings and correlate them with runtime security events. Amazon Inspector is a vulnerability management service that scans Amazon EC2 instances, container images, AWS Lambda functions, and code repositories. This integration imports findings from code repository scans to provide visibility into code-level vulnerabilities.
This integration imports findings from the Code Security tab in Amazon Inspector, which includes resources with the CODE_REPOSITORY resource type.

​
Prerequisites

Before you begin, ensure you have:
  • Amazon Inspector activated in your AWS account
  • Access to an AWS account with the ability to create IAM policies, roles, and users
  • Access to RAD Security workspace with integration permissions
Need to activate Amazon Inspector? See the Amazon Inspector Getting Started documentation.

​
Required IAM Permissions

The following IAM policy actions are required for the integration:

​
Step 1: Create an IAM Policy

1

Open the IAM Console

Log into the AWS Management Console and open the IAM Console
2

Navigate to Policies

Select Policies from the sidebar on the left
3

Create a New Policy

Click Create Policy
4

Select the Inspector2 Service

  1. In the Policy Editor, find the Select a service section
  2. Search for and select Inspector2
5

Select Required Actions

In the Actions allowed section, check the following actions:
  • ListFindingAggregations
  • ListFindings
6

Review and Create

  1. Click Next
  2. Enter a Policy Name (e.g., RADSecurityInspectorReadOnly)
  3. Add an optional Description
  4. Click Create Policy
Save the policy name—you’ll need it when creating the IAM user.
For more information on creating IAM policies, see the AWS IAM Creating Policies documentation.

​
Step 2: Create an IAM User

1

Navigate to Users

In the IAM Console, select Users from the sidebar on the left
2

Create a New User

Click Create user
3

Configure User Details

  1. Enter a User name (e.g., rad-security-inspector)
  2. Leave Provide user access to the AWS Management Console unchecked—this user only needs API access
  3. Click Next
4

Attach the Policy

  1. In the Permissions options section, select Attach policies directly
  2. In the Permissions policies section, search for the policy you created in Step 1
  3. Check the box next to the policy
  4. Click Next
5

Review and Create

  1. Review the user details
  2. Click Create user
For more information on creating IAM users, see the AWS IAM Creating Users documentation.

​
Step 3: Generate Access Keys

1

Open User Details

In the IAM Console, navigate to Users and select the user you created in Step 2
2

Navigate to Security Credentials

Click the Security credentials tab
3

Create Access Key

  1. In the Access keys section, click Create access key
  2. When prompted to select a use case, select Other
  3. Add an optional description tag
  4. Click Create access key
4

Save Your Credentials

Important: Save the Access key ID and Secret access key immediately. The secret access key will not be shown again after you leave this page.
  1. Copy the Access key ID
  2. Copy the Secret access key
  3. Store both values securely—you’ll need them to configure the integration
For more information on managing access keys, see the AWS IAM Access Keys documentation.

​
Step 4: Identify Your AWS Region

To find your Amazon Inspector region:
  1. Navigate to the Amazon Inspector Console
  2. Look at the URL in your browser—the region appears in the format: {region}.console.aws.amazon.com
  3. Note the region code (e.g., us-east-1, us-west-2, eu-west-1)
Common AWS regions include:
  • us-east-1 (N. Virginia)
  • us-west-2 (Oregon)
  • eu-west-1 (Ireland)
  • ap-southeast-1 (Singapore)
For a full list, see AWS Regions and Endpoints.

​
Step 5: Configure in RAD Security

Navigate to your RAD Security workspace and configure the Amazon Inspector integration with the following parameters:

​
Required Parameters

​
Verify Integration

After completing the setup, verify your integration is working:
  1. Navigate to Data Sources > Integrations > Vulnerabilities in RAD Security
  2. Locate your Amazon Inspector integration
  3. Check the connection status shows as Connected
  4. Verify code security findings are being synced
Your Amazon Inspector integration is now configured! RAD Security can now import code security findings and correlate them with runtime security events.

​
What Data is Synced

Once configured, RAD Security will sync code security findings from Amazon Inspector:
  • Vulnerability identifiers (CVE IDs)
  • Severity levels and CVSS scores
  • Affected code repositories
  • Vulnerable dependencies and packages
  • Remediation recommendations
  • Finding status and detection dates
  • Repository names and identifiers
  • Branch information
  • File paths with vulnerabilities
  • Dependency manifest files
  • Package name and version
  • Fixed version (if available)
  • Vulnerability description
  • Exploit availability indicators
  • Related security advisories

​
Use Cases

Code Vulnerability Correlation

Correlate code repository vulnerabilities with runtime security events to identify exploitable weaknesses.

Dependency Risk Assessment

Prioritize vulnerable dependencies based on severity, exploitability, and usage in production.

Supply Chain Security

Monitor third-party dependencies for known vulnerabilities across your code repositories.

Remediation Tracking

Track vulnerability remediation progress and validate fixes in your development pipeline.

​
Troubleshooting

Possible causes:
  • Incorrect Access Key ID or Secret Access Key
  • Access keys have been deactivated or deleted
  • IAM user has been deleted
Solution:
  • Verify the Access Key ID and Secret Access Key are correct
  • Check the IAM Console to ensure the access keys are active
  • Generate new access keys if necessary
Possible causes:
  • IAM policy doesn’t include required actions
  • Policy not attached to the IAM user
  • Resource restrictions in the policy
Solution:
  • Verify the IAM policy includes inspector2:ListFindings and inspector2:ListFindingAggregations
  • Ensure the policy is attached to the correct IAM user
  • Check that the policy resource is set to * or includes the necessary resources
Possible causes:
  • Amazon Inspector not activated
  • No code repositories configured for scanning
  • No findings exist in the Code Security tab
  • Wrong region configured
Solution:
  • Verify Amazon Inspector is activated in your AWS account
  • Ensure code repository scanning is enabled in Amazon Inspector
  • Check the Code Security tab in the Amazon Inspector Console for existing findings
  • Confirm you’re using the correct AWS region
Possible causes:
  • Region mismatch between configuration and Amazon Inspector
Solution:
  • Navigate to the Amazon Inspector Console and verify the region in the URL
  • Update the region in your RAD Security integration configuration
  • Note that Amazon Inspector findings are region-specific
Possible causes:
  • Access keys were rotated but integration not updated
  • Old access keys were deleted before new ones were configured
Solution:
  • Generate new access keys in the IAM Console
  • Update the integration configuration in RAD Security with the new credentials
  • Delete old access keys only after verifying the new ones work

​
Security Best Practices

Use Dedicated IAM Users

Create a dedicated IAM user for RAD Security integration rather than using existing user credentials.

Least Privilege Access

Only grant the minimum required permissions. The read-only permissions in this guide are sufficient for the integration.

Secure Credential Storage

Store access keys securely. Never commit them to version control or share via unsecured channels.

Regular Key Rotation

Rotate access keys periodically according to your organization’s security policies.

Monitor API Usage

Use AWS CloudTrail to monitor API calls made by the integration user for anomalous activity.

Enable MFA for Admin Accounts

Ensure MFA is enabled for any admin accounts that manage the IAM user and policies.

​
Access Key Rotation

To rotate your access keys without service interruption:
1

Create New Access Keys

  1. Navigate to the IAM user in the AWS Console
  2. Go to Security credentials
  3. Click Create access key
  4. Save the new Access Key ID and Secret Access Key
2

Update RAD Security

  1. Navigate to the Amazon Inspector integration in RAD Security
  2. Update the Access Key ID and Secret Access Key with the new values
  3. Save the configuration
3

Verify the Integration

  1. Confirm the integration status shows Connected
  2. Verify data is still syncing correctly
4

Delete Old Access Keys

  1. Return to the IAM user in the AWS Console
  2. Locate the old access key
  3. Click Actions > Delete
  4. Confirm deletion
Always verify the new access keys are working before deleting the old ones to avoid service interruption.

​
Additional Resources

Amazon Inspector Documentation

Official AWS documentation for Amazon Inspector

IAM Best Practices

AWS IAM security best practices guide

​
Next Steps

Vulnerabilities Overview

Explore other vulnerability integration options

Runtime Security

Learn how RAD correlates vulnerabilities with runtime threats

Alerts & Incidents

Configure alerts for vulnerability-related events

Threat Models

Understand how threats are detected and prioritized