Orca Connector

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

The following steps allow you to configure this connector for use with Tenable Exposure Management from start to finish.

Connector Details

Prerequisites and User Permissions

Before you begin configuring the connector, make sure to:

1. Create an Orca Security business unit.

2. Generate an Orca Security API token.

Create an Orca Security Business Unit

1. Log in to the Orca Security platform.

2. Navigate to Select Unit > Configure Business Units.

3. Click Create Business Unit.

4. In the Unit Name box, type a descriptive name for the business unit.

5. Select the data source from which you want to fetch data: Provider (AWS, Azure, GCP, etc.) or Accounts.

   

   
   

   Note: Tenable Exposure Management does not currently support AppSec data from Cloud Providers.

6. Click Create.

Generate an Orca Security API Token

1. Log in to the Orca Security platform.

2. Navigate to Settings > Users & Permissions > API.

3. Click Add API Token.

4. In the Name box, type a descriptive name for the token.

5. In the Expiration Date section, select an expiration date or select the Never Expire checkbox.

6. Select the Service Token checkbox.

7. From the Roles list, select Contributor.

8. Select the Scope access to specific resources checkbox.

9. Select Business units, and then select the business unit you created.

10. Click Add.

11. Copy the API Token to a safe location. You need it to configure the connector.

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 page 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 Server URL drop down, select the region of your Orca server.

3. In the API Keytext box, paste the API key you generated earlier.

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

   • In the Inventory Resources drop-down box, select the resources you want to ingest into Tenable Exposure Management.

   • 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) In the "Immediately remove assets when their status is:" section, select more statuses when detected the asset should be archived.

     

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.

Orca 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	Orca Field
Asset Name	data[].name
Asset Provider ID External Identifier	data[].data.InstanceId/Arn/ VmId / AzureId/ asset_unique_id
Cloud Provider	data[].data.CloudAccount.data.CloudProvider.value
Cloud Resource Type	data[].data.NewSubCategory
Cloud Resource > Service	data[].data.type
Cloud Resource > Billing ID	data[].data.CloudAccount.name
Host Fully Qualified DNS	data[].data.PublicDnss.value[0]
Last Observed At	data[].data.LastSeen.value
First Observation Date	data[].data.FirstSeen.value
External Tags	data[].data.Tags.value
Operating Systems	data[].data.DistributionName.value
OS Version	data[].data.DistributionVersion.value
IPv4 Addresses	data[].data.PrivateIps.value
Device System Type	data[].data.Type.value

Container Mapping

Tenable Exposure Management UI Field	Orca Field
Asset Name	data[].name
Asset Provider ID External Identifier	data[].data.InstanceId/Arn/ VmId / AzureId/ asset_unique_id
Cloud Provider	data[].data.CloudAccount.data.CloudProvider.value
Cloud Resource Type	data[].data.NewSubCategory
Cloud Resource > Service	data[].data.type
Cloud Resource > Billing ID	data[].data.CloudAccount.name
Host Fully Qualified DNS	data[].data.PublicDnss.value[0]
Last Observed At	data[].data.LastSeen.value
First Observation Date	data[].data.FirstSeen.value
External Tags	data[].data.Tags.value
Operating Systems	DistributionName
OS Version	DistributionVersion
Container Image Tags	ImageTags.value (single value)
Image Digest	ImageLayersDigest.value (single value)

Resource Mapping

Tenable Exposure Management UI Field	Orca Field
Asset Name	data[].name
Asset Provider ID External Identifier	data[].data.InstanceId/Arn/ VmId / AzureId/ asset_unique_id
Cloud Provider	data[].data.CloudAccount.data.CloudProvider.value
Cloud Resource Type	data[].data.NewSubCategory
Cloud Resource > Service	data[].data.type
Cloud Resource > Billing ID	data[].data.CloudAccount.name
Region	data[].data.Region.value
Host Fully Qualified DNS	data[].data.PublicDnss.value[0]
Last Observed At	data[].data.LastSeen.value
First Observation Date	data[].data.FirstSeen.value
External Tags	data[].data.Tags.value

Finding Mapping

Tenable Exposure Management UI Field	Orca Field
Finding Name	vulnerability_name
CVEs	data[].data.CveIds.value
CVSSv3 Base Score	MaxCvssScore
Severity	data[].data.RiskLevel.value Severity
State	data[].data.Status.value
MITRE Category	data[].data.MitreCategory.value
Description	data.description
Solution	vulnerability_recommendations
Finding Custom Attributes	port protocol package Package Version
First Seen	device_vulnerability_detection_date
Last seen (Observed)	vulnerability_last_updated

Finding Status Mapping

Note:For Orca, Tenable Exposure Management bases the findings status on the Status field.

Finding Severity Mapping

Note:For Orca data, Tenable uses the Severity field to determine severity.

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: 1.0

Data Validation

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

Asset Data Validation

Objective: Ensure the number of assets in Orca aligns with the number of assets in Tenable Exposure Management.

In Orca:

1. Navigate to the Inventory page.

2. Click + Add Filter.

3. Search for and select SubCategory.

4. Select the following filters:

   • Virtual Instances

   • Image

   • Containers

   • Serverless

   • Services

   • Groups

   • Kubernetes Clusters

   

5. Click Apply.

6. Hover over the Assets count to view the total number of filtered assets.

   

In Tenable Exposure Management:

1. Locate your connector assets.

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

Expected outcome: The total numbers returned in Orca and Tenable Exposure Management should match.

Note: The counts may differ slightly if Orca Security is actively scanning and discovering new assets during the comparison.

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

• Asset not seen for X days according to "Last Seen". See Asset Retention

• Asset status changes to one of the selected statuses defined in the Asset Retention configuration

  Tip: To learn more on how assets are archived and findings change status, see Orca Connector.

Finding Data Validation

Objective: Ensure the number of findings in Orca aligns with the number of findings in Tenable Exposure Management.

In Orca:

1. Navigate to the Alertspage.
   

2. Clear all filters and ungroup any Group By fields.

3. Click + Add Filter.

4. Search for and select Asset Sub Category.

5. Select the following filters:

   • Virtual Instances

   • Image

   • Containers

   • Serverless

   • Services

   • Groups

   • Kubernetes Clusters

6. Click Apply.

7. Note the total number of Alerts.

   

In Tenable Exposure Management:

1. Locate your connector findings.

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

Expected outcome: The total numbers returned in Orca and Tenable Exposure Management should match.

If a finding is missing from Tenable 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.

  Tip: To learn more on how assets are archived and findings change status, see Orca Connector.