RedHat Insights Connector

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

Red Hat® Insights continuously analyzes platforms and applications to predict risk, recommend actions, and track costs so enterprises can better manage hybrid cloud environments. Insights is included with almost every subscription to Red Hat Enterprise Linux®, Red Hat OpenShift®, and Red Hat Ansible® Automation Platform.

Prerequisites and User Permissions

Before you begin configuring the connector, make sure to:

• Generate RedHat Client ID and Secret:

  1. Navigate to the Red Hat Console at https://console.redhat.com/iam.

  2. Navigate to Service Accounts and click on Create service account.

  3. Type a Service Account Name and provide a Short Description for the account.

  4. Click Create.

  5. Save the Client ID and Client secret, as you won't be able to view them again. Check the box indicating you have done so and click Close.

• Create a Redhat Group with the required access permissions:

  1. Navigate to User Access > Groups and select Create group.

  2. Type a Group Name (e.g. 'em-api-group').

  3. Click Next.

  4. In the roles assignment step, in the search box, type viewer, and select the appropriate API roles:

     • Inventory Host viewer

     • Vulnerability viewer

     • Patch viewer

  5. Click Next.

  6. On the Add members page, click Next.

  7. On the Review details page, click Submit.

  8. Click Exit.

• Assign the Service Account to your Group:

  1. Within the Groups section, click on the newly created group name.

  2. Navigate to the Service Accounts tab > Add service account.

     

  3. Locate the service account you created earlier and select it by checking the box next to its name.

  4. Click Add to group.

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

To 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. In the Client ID and Client Secret text boxes, paste the client credentials you generated in Red Hat.

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

   • 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.

   • (Optional) From the drop-down menu, you can choose to automatically remove assets that reach a certain asset status, for example, Stale.

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.

Red Hat Insights 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.

Device Mapping

Tenable Exposure Management UI Field	RedHat Insights Field
Unique Identifier	id
Asset - Name	display_name
Asset - Operating Systems	system_profile.operating_system.name
Asset - IPv4 Adresses Asset - IPv6 Adresses	ip_addresses
Asset - First Observation Date	created
Asset - Last Observed At	Asset - Last Observed At updated
Asset - Host Fully Qualified DNS	fqdn
Asset - MAC Addresses	mac_addresses
Asset - External Tags	attributes.tags groups.name
Asset Custom Attributes	"redhat_uuid": id "ansible_hostname": "ansible_host or fqdn "system_state": systemd.state, "infrastructure_type": system_profile.infrastructure_type "cloud_provider": system_profile.cloud_provider, "bios_vendor": system_profile.bios_vendor, "system_memory_bytes": system_profile.system_memory_bytes

Finding Mapping

Tenable Exposure Management UI Field	RedHat InsightsField
Unique Identifier	asset id + unique vulnerability id
Finding Name	cve_id
CVEs	cve_id
Severity Driver	cvss3_score
Description	description
First Seen	first_reported
Last seen (Observed)	last_evaluation
Finding Custom Attributes	rule_id rule_description rule_error_key rule_vulnerability public_date impact business_risk

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.

API Endpoints in Use

/api/inventory - v1
/api/vulnerability - v1
/api/patch - v3