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.

Tip: For more information on how third-party integrations work, see Connectors.

Connector Details

Details Description

Supported products

Red Hat® Insights

Category

Endpoint Security

Ingested data

Assets and Findings

Ingested Asset Classes

Devices

Integration type

UNI directional (data is transferred from the Connector to Tenable Exposure Management in one direction)

Supported version and type

SaaS (latest)

Prerequisites and User Permissions

Before you begin configuring the connector, make sure you have the following:

  1. Generate RedHat Credentials (Client ID and Secret)

  2. Create and Configure Group

  3. Assign the Service Account to a Group

Generate RedHat Credentials

  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 and Configure Group

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

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

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

  5. 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
  6. Click Create. Tenable Exposure Management begins syncing the connector. The sync can take some time to complete.

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

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.

API Endpoints in Use

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

API

Use in Tenable Exposure Management

Required Permissions

https://sso.redhat.com/auth/realms/redhat-external/protocol/openid-connect/token

Authentication

-

/api/inventory/v1/hosts

Assets

Inventory Hosts Viewer

/api/vulnerability/v1/vulnerabilities/cves

Detections

Vulnerability viewer
/api/vulnerability/v1/cves/{{cve_id}}/affected_systems

Asset enrichment

Findings

Vulnerability viewer

Data Validation

This section shows how to validate and compare data between Tenable Exposure Management and the RedHat Insights platform.

Asset Data Validation

Objective: Ensure the number of systems (devices) in RedHat Insights aligns with the number of devices displayed in Tenable Exposure Management.

In RedHat Insights:

  1. Navigate to Inventory > Systems.

  2. If the Exposure Management connector is configured to archive assets based on their status, ensure all status types are selected during validation.

In Tenable Exposure Management:

  1. Locate your connector assets.

  2. Compare the total number of assets between RedHat and Tenable Exposure Management.

Expected outcome: All visible systems in Red Hat Insights should be imported into Exposure Management, assuming their status is not filtered out by connector configuration. The total numbers returned in RedHatand Exposure Management should match.

If an asset is not visible in Exposure Management, check the following conditions:

  • The asset status changed to one of the selected statuses defined in theAsset Retention configuration.

  • Archived based on the last observed date (last seen).

Finding Data Validation

Objective: Ensure that the total number of findings between RedHat and Exposure Management is consistent.

In RedHat Insights:

  1. Navigate to Security > Vulnerability > CVEs.

  2. Click on a specific CVE.

  3. Apply the following filters:

    • Systems: Set to “1 or more” (this is the default behavior).

    • Advisory: Ensure no advisory filter is applied (by default, it may be applied).

    • Status: Select the following values: Not reviewed, In review, On-hold, Scheduled for patch.

In Tenable Exposure Management:

  1. Locate your connector findings.

  2. Compare the total number of findings between RedHat Insights and Tenable Exposure Management.

Expected outcome: The total numbers returned in RedHat Insights and Exposure Management should match

If a finding is missing from Exposure Management or no longer active, check the following conditions:

  • The finding is marked as Fixed and appears under the Fixed state on the Findings screen

  • The finding no longer appears because its related asset was archived.