Outpost24 Connector

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

Outpost24 Outscan is an automated vulnerability scanner that enables organizations to diagnose, monitor, and triage external vulnerabilities on your internet-exposed devices as well as verify your PCI Compliance for transactional businesses.

Prerequisites and User Permissions

Before you begin configuring the connector, make sure to:

• Identify your Outpost Outscan Server URL (e.g., https://outscan.outpost24.com)

• Generate Outpost Credentials:

  1. Log in to your Outpost24 portal.

  2. Click your account name in the upper-right corner, then select IAM.

  3. In the Roles tab, click + Add role.

  4. Name the role Exposure Management or Tenable (or another preferred name).

  5. Grant View permissions to:

     • Asset groups

     • Assets

     • Findings

       

  6. Click Add to create the role.

  7. In the Users tab, click + Add user.

  8. Fill in the required details:

     • Provide a unique username.

     • Use a valid email address (a temporary password will be sent here).

  9. Click Add.

  10. Retrieve the password from the email. (Optional: log in and update the password.)

• Assign the Role and Resource Groups:

  1. In the Users tab, select the checkbox of the newly created user.

  2. Click Assign roles and check the role you created earlier.

  3. Click Assign.

  4. Click Assign resource groups, select the relevant resource groups, and click Assign.

• Configure NetSec Permissions (Read only):

  1. In the left navigation panel, click NetSec.

  2. In the bottom-left, click the target icon, then Navigate to: NetSec > Settings > Manage Users.

  3. In Manage User Accounts, navigate to the User Roles tab and click + New.

  4. Enter the role name you greated earlier, check Read Only, and click Save.

     

  5. In the User Accounts tab, right-click the same user and select Edit.

  6. In the Account Settings tab:

     • Check Active.

     • Check the newly created role under Granted User Roles.

       

  7. Navigate to the Granted Targets tab and uncheck Not all Targets Granted.

  8. Navigate to the Attributes tab:

     • Enter a value in the Uri* field (any unique string).

  9. Click Save.

     

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 Server URL section, type the URL for your Outpost24 server.

4. In the Username and Password text boxes, paste the user credentials you generated in Outpost24.

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

   • (Optional) To fetch NetSec assets and vulnerabilities from Outpost24, select the Fetch NetSec assets and vulnerabilities check box.

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

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

     

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

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

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

Outpost 24 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.

Web Application Mapping

Tenable Exposure Management Value	Outpost24 Value
Unique Identifier	id
Asset - Name	name
Asset - First Observation Date	firstSeen or created
Asset - Last Observed At	lastSeen or updated
Asset - External Tags	tags groups
Asset Custom Attributes	source asset_identifiers

Finding Mapping (for Web Application)

Tenable Exposure Management UI Field	Outpost24 Field
Unique Identifier	asset id + match id + Unique Vulnerability id
Finding Name	name
CVEs	cve
CWEs	cwe
Severity Driver	nvdCvssV3Score or cvssV3Severity or nvdCvssV2Score
Description	description
First Seen	firstSeen or created
Last seen (Observed)	lastSeen
Finding Custom Attributes	url source port protocol id softwareComponent cyrating hasExploits exploitProbability nvdCvssV3Vector

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:

Support Limitations and Expected Behavior

This section outlines any irregularities, expected behaviors, or limitations related to integration of the connector and Exposure Management. It also highlights details about ingested and non-ingested data to clarify data handling and functionality within this integration.

API Endpoints in Use

API version: v1.0