AWS Inspector V2 Connector

The following is not supported in Tenable FedRAMP Moderate environments. For more information, see the Tenable FedRAMP Product Offering.

The AWS Inspector Connector enumerates vulnerabilities from AWS Inspector, ECR, and ECS.

Prerequisites and User Permissions

Before you begin configuring the connector, make sure to:

1. Have a cross-account user with the permission: inspector2:ListFindings

2. Complete one of the following configurations based on your use case:

   • Generate AWS Inspector V2 Access and Secret Keys (for Access and Secret Key authentication method):

     1. Sign in to the AWS Management Console as an IAM user with administrative privileges (not the root account).

     2. Navigate to the IAM Console: https://console.aws.amazon.com/iam

     3. In the left navigation pane, select Users.

     4. Select the cross-account user with the inspector2:ListFindings permission.

     5. Choose the Security credentials tab.

     6. In the Access keys section, click Create access key.

     7. In the Access key best practices and alternatives, select Third-party service as the use case.

        

     8. Click Next.

     9. In the Set description tag, add a description tag (e.g., Exposure Management Intergation).

     10. Click Create access key.

     11. On the confirmation page, copy the:

         • Access Key ID

         • Secret Access Key

           You won’t be able to view the Secret Access Key again after this screen, so save it securely.

   • Create AWS Inspector V2 External ID and ARNs (for ARN and External ID authentication method):

     1. Sign in to the AWS Management Console with an account that has permissions to create IAM policies.

     2. Navigate to the IAM service.

     3. In the left-hand menu, click on Policies, then click Create policy.

     4. In the Create Policy page, select the Visual editor tab.

     5. Under Service, search for and select Inspector2.

     6. Under Actions, select the inspector2:ListFindings permission.

     7. Click Next: Review.

     8. On the Review policy page, enter a Name and (optionally) a Description for the policy.

     9. Review the Summary to ensure the correct permissions are included.

     10. Click Create policy to save.

     11. Navigate to IAM > Roles > Create Role > Another AWS account.

     12. In the Account ID field, paste the following Tenable account ID:012615275169

     13. Check the "Require External ID" box.

     14. Enter your External ID value (maximum 12 characters).

     15. Copy the value and save in a safe place so you can use it later in the connector setup page.

         

     16. Make sure "Require MFA" is unchecked.

     17. Click Next: Permissions.

     18. Attach the policy created in steps 2–8.

         

     19. Continue through the wizard, review the role settings, and create the role.

     20. Copy the generated ARN.

     Important: If you're creating roles for multiple AWS accounts, repeat the steps above for each account. Make sure you use the same External ID for all roles and copy the generated ARN of each role/account.

Add a Connector

To add a new connector:

1. In the left navigation menu, click Connectors.

   The Connectors page appears.

   

2. In the upper-right corner, click Add new connector.

   The Connector Library appears.

   

3. In the search box, type the name of the connector.

4. On the tile for the connector, click Connect.

   The connector configuration options appear.

Configure the Connector

1. (Optional) In the Connector's Name text box, type a descriptive name for the connector.

2. (Optional) To use a preconfigured on-prem connector to connect to this connector, from the Gateway drop-down, select the on-prem connector you want to use for the connector. Otherwise, select Don't use gateway.

   Note: For information about configuring a gateway, see Tenable On-Prem Connector.

3. From the Authentication method drop-down, select the authentication method to use for the connector.

   • If you select the Access Key & Secret Key method, enter the credentials you generated earlier.

   • If you select the ARN & External ID method, enter the credentials you generated earlier.

4. In the Data pulling configuration section, you can configure dynamic settings specific to the connector.

   • (Optional) In the Regions drop-down, select the AWS regions to include for data ingestion.

   • In the Asset Retention text box, type the number of days after which you want assets to be removed from Tenable Exposure Management. If an asset has not been detected or updated within the specified number of days, it is automatically removed from the application, ensuring your asset inventory is current and relevant.

     Tip: For more information, see Asset Retention.

5. In the Test connectivity section, click the Test Connectivity button to verify that Tenable Exposure Management can connect to your connector instance.
   

   • A successful connectivity test confirms that the platform can connect to the connector instance. It does not, however, guarantee that the synchronization process will succeed, as additional syncing or processing issues may arise.
     

   • If the connectivity test fails, an error message with details about the issue appears. Click Show tests for more information about the exact error.
     

     

6. In the Connector scheduling section, configure the time and day(s) on which you want connector syncs to occur.

   Tip: For more information, see Connector Scheduling.

7. Click Create. Tenable Exposure Management begins syncing the connector. The sync can take some time to complete.
   

8. To confirm the sync is complete, do the following:

   • Navigate to the Connectors page and monitor the connector's status. Sync is complete once the connector status is Connected.

   • View the sync logs for the connector to monitor the logs for a successful connection.

AWS in Tenable Exposure Management

Locate Connector Assets in Tenable Exposure Management

As the connector discovers assets, Tenable Exposure Management ingests those devices for reporting.

To view assets by connector:

1. In Tenable Exposure Management, navigate to the Assets page.

2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view assets.

   

   The asset list updates to show only assets from the selected connector.

3. Click on any asset to view Asset Details.

Locate Connector Weaknesses in Tenable Exposure Management

As the connector discovers weaknesses, Tenable Exposure Management ingests those weaknesses for reporting.

To view weaknesses by connector: 

1. In Tenable Exposure Management, navigate to the Weaknesses page.

2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view weaknesses.

   

   The weaknesses list updates to show only weaknesses from the selected connector.

3. Click on any weakness to view Weakness Details.

Locate Connector Findings in Tenable Exposure Management

As the connector discovers individual findings, Tenable Exposure Management ingests those findings for reporting.

To view findings by connector:

1. In Tenable Exposure Management, navigate to the Findings page.

2. In the Filters section, under 3rd Party Connectors, click the connector name for which you want to view findings

   

   The findings list updates to show only assets from the selected connector.

3. Click on any asset to view Finding Details.

Data Mapping

Exposure Management integrates with the connector via API to retrieve relevant weakness and asset data, which is then mapped into the Exposure Management system. The following tables outline how fields and their values are mapped from the connector to Exposure Management.

Container Mapping

Tenable Exposure Management UI Field	AWS Inspector V2 Field
Unique Identifier	id
Asset - Name	tags.Name
Asset - Operating Systems	Platform
Asset - Container Image Tags	imageTags
Asset - Image Digest	imageHash
Asset - External Tags	Tags
Asset Custom Attributes	region repositoryName

Finding Mapping

Tenable Exposure Management UI Field	AWS Inspector V2 Field
Unique Identifier	finding_arn
Finding Name	title
CVEs	vulnerabilityId
Severity Driver	inspectorScore
Description	description
First Seen	firstObservedAt
Last seen (Observed)	lastObservedAt
Port	openPortRange.begin
Protocol	protocol
Finding Custom Attributes	networkPath (only for Device and Resource) severity type vulnerablePackages.name vulnerablePackages.version source sourceUrl remediation scoringVector

Finding Status Mapping

Finding Severity Mapping

Status Update Mechanisms

Every day, Tenable Exposure Management syncs with the vendor's platform to receive updates on existing findings and assets and to retrieve new ones (if any were added).

The table below describes how the status update mechanism works in the connector for findings and assets ingested into Tenable Exposure Management.

Uniqueness Criteria

Tenable Exposure Management uses defined uniqueness criteria to determine whether an ingested asset or finding should be recognized as a distinct record. These criteria help define how assets and findings are identified and counted from each connector.

Tip:  Read all about Third-Party Data Deduplication in Tenable Exposure Management

The uniqueness criteria for this connector are as follows:

API Endpoints in Use

API version: 11.3.0 aioboto3