Tenable.sc Asset Discovery
Tenable.sc provides your organization the ability to accurately identify, investigate, and prioritize vulnerabilities. With Tenable.sc you get a real-time, continuous assessment of your security posture so you can find, prioritize, and fix vulnerabilities faster.
Archer Exchange: With the Archer Exchange, the Archer team has created a broad selection of supplemental, value-added offerings to help you get your unique risk management program on the right path, right from the start. You can leverage the Archer Exchange offerings to expand the use of Archer solutions into new business processes and address specific industry, geographic, regulatory, or technical requirements.
For more information see the Archer Exchange on the Archer Community:https://archerirm.exchange/en-US/apps/694903/tenable-security-center-asset-discovery
On this page
Release notes
|
Release Version |
Published Date |
Notes |
|
Archer 6.12 |
July 2024 |
Re-Signed JavaScript file with latest certificate |
|
Release Version |
Published Date |
Notes |
|---|---|---|
|
Archer 6.4 SP1 |
November 2019 |
Initial Release |
|
Archer 6.7 |
December 2021 |
Re-Signed JavaScript file. |
|
Archer 6.12 |
January 2023 |
Authentication and User Agent header update |
Overview of Tenable.sc
The integration of Tenable.sc Asset Discovery with the Devices application in any of the below use cases enables customers to leverage the discovered devices and catalog those network devices within Archer.
Benefits
The Tenable.sc integration with Archer enables organizations to:
-
Catalog network devices on a corporate network.
Requirements
|
Components |
Requirement |
|---|---|
|
Archer Solution |
|
|
Archer Use Case(s) |
The following use cases can take advantage of the information provided by the Tenable.sc integration:
|
|
Archer Applications |
Leverages the Devices application |
|
Uses Custom Application |
No |
|
Requires On-Demand license |
No |
|
Archer requirements |
Please refer “Tenable.sc Integration” page for version details |
|
Tenable.sc Requirements |
Valid Tenable.sc license is required |
Integration diagram
The following diagram provides an overview of the interaction between Tenable.sc and the Archer Tenable.sc Integration offering.
Configure Tenable.sc Host
Important: Review the Tenable documentation for URLs with REST endpoints and other Tenable API best practices.
Configure the data feed
The following data feed is used as part of the Tenable.sc Integration process:
The Tenable.sc Host data feed is a JavaScript transporter data feed that retrieves data (Devices related data) from the Tenable.sc URL and creates and updates the records in the Archer Devices application.
The data feeds must be configured. After setting up the data feed, you can schedule it to run as needed per your organization’s requirements. For more inf.ormation on scheduling the data feed, see the Scheduling Data Feed section.
Before you upload a JavaScript file, you must configure JavaScript Transporter settings in the Archer Control Panel.
-
On the General tab, go to the JavaScript Transporter section.
-
Open the Archer Control Panel.
-
Go to Instance Management and select All Instances.
-
Select the instance you want to use.
-
On the General tab, go to the JavaScript Transporter section.
-
-
In the Max Memory Limit field, set the value to 2048 MB (2 GB).
-
In the Script Timeout field, set the value to 120 minutes (2 hours).
-
(Optional) If you want to allow only digitally signed JavaScript files in the data feed, enable Require Signature.
-
In the JavaScript Transporter Settings section, select the checkbox Require Signature. A new empty cell appears in the Signing Certificate Thumbprints section.
-
In the Signing Certificate Thumbprints section, double-click an empty cell.
-
Enter the digital thumbprint of the trusted certificate used to sign the JavaScript file.
Note: For information on how to obtain digital thumbprints, see ObtainingDigital Thumbprints.
Important: If you enable Require Signature and specify no thumbprints, no JavaScript files will be accepted by the system.
-
(Optional) If you want to add additional thumbprint sources, repeat steps 4b-4c for each thumbprint.
-
-
On the toolbar, click Save.
When running JavaScript data feeds, you can set the Archer instance to only allow digitally signed JavaScript files from trusted sources for security considerations.
For a certificate to be trusted, all the certificates in the chain, including the Root CA Certificate and Intermediate CA certificates, must be trusted on both the Web Server and Services Server machines.
Archer Technologies LLC certificate is not present on every machine’s root by default.
-
On the JavaScript file, right-click and select Properties.
-
Click the Digital Signatures tab.
-
From the Signature List window, select Archer Technologies LLC.
-
Click the Details button.
-
Click View Certificate.
-
Click Install Certificate.
-
Select Local Machine.
-
Click Next.
-
Select Place all certificates in the following store and click Browse.
-
Select Trusted Root Certification Authorities and click OK.
-
Click Next.
-
Click Finish.
-
-
-
Upon successful import, click OK.
-
In the Archer Control Panel environment, open the Manage Computer Certificates program.
-
Click Start.
-
Type: certificate
-
From the search results, click Manage Computer Certificates.
-
-
Ensure that your trusted source certificates are in the Certificates sub-folder of the Trust Root Certification Authorities folder.
-
In the Certificates sub-folder, double-click the Archer Technologies LLC that contains the thumbprint you want to obtain.
-
Verify that the certificate is trusted.
-
In the Certificate window, click the Certification Path tab.
-
Ensure that the Certificate Status windows displays the following message:
This certificate is OK
Note: If the Certificate Status windows displays something different, follow the on-screen instructions.
-
-
Obtain the trusted certificate thumbprint.
-
In the Certificate window, click the Details tab.
-
Select the Thumbprint field.
The certificate's digital thumbprint appears in the window.
-
Copy the thumbprint.
-
Download the Tenable.sc vulnerabilities (hosts) data feed
-
Download the zip file from the Archer Community..
-
Extract the zip file and copy the Tenable.sc Hosts Archer 6.12.dfx5 file.
-
Copy the “signed-TenableSC_1.0.17.js” JavaScript file.
-
Paste both the files into your desired location, which will be used in this integration.
Important: Before you upload a JavaScript file, configure the JavaScript Transporter settings in the Archer Control Panel. For more information, see Configure the JavaScript Transporter Settings. Updates to the API files used in the JavaScript Transporter (signed-TenableSC_1.0.17.js) can only be achieved in a hosted environment with a Professional Services engagement. For more information, contact your account representative.
-
Go to the Manage Data Feeds page.
-
From the menu bar, click
. -
Under Integration, click Data Feeds.
-
-
In the Manage Data Feeds section, click Import.
-
Locate and select the Tenable.sc Hosts Archer 6.12.dfx5 file.
-
Click Open.
-
In the General Information section, in the Status field, select Active.
-
Click the Transport tab.
-
In the Transport Configuration section, do the following:
-
Click Upload.
-
From the Upload JavaScript File dialog, click Add New.
-
Locate and select the signed-TenableSC_1.0.17.js file.
-
Click Open.
-
From the Upload JavaScript File dialog, click OK.
-
-
In the Custom Parameters section, enter key values. The following table describes the value for each key in Custom Parameters.
Key
Value
accessKey
[Valid value]
secretKey
[Valid value]
dataSource
hosts
URL
[Valid value] For example, https://tenablesc.eastus.cloudapp.azure.com
ignoreLastRunTime
false
vulnSeverities
4,3,2,1
vulnDateFilterType
firstSeen
vulnLoadActive
true
vulnLoadPatched
true
verifyCerts
false
userAgent
Optional, Default Value=’ ARCHER DATAFEED CLIENT’
Note: The listed values are in place by default. They can be configured to suit your environment. Important: The keys and values are case-sensitive and cannot include extra spaces at the end of the strings.
-
(Optional) Add startOffset as a new key.
Note: The startOffset parameter specifies the first record in the range you want to retrieve, and the endOffset parameter specifies the last record in the range you want to retrieve. Use these parameters to parse data into consumable sizes. For more information, see the Tenable.sc API Best Practices Guide.
-
Click Add New.
-
Enter startOffset as the key.
-
Define a valid value for the startOffset key.
-
Click Add New.
-
Enter endOffset at the key.
-
Define a valid value for the endOffset key.
-
-
For each key type, determine whether you want it to be Protected or Plain Text. Selecting Protected encrypts the key value for the specified key in the log.
-
Click the Source Definition tab.
-
Click the Tokens subtab.
-
Verify token values. The following table describes token values to verify.
Token
Value
BatchContentSave
1000
LastRunTime
(Populated by feed)
LastFileProcessed
(Populated by feed)
PreviousRunContext
(Populated by feed)
Note: For more information about tokens, see Data Feed Tokens in Archer Help.
-
-
Verify that key field values are not missing from the data feed setup window.
-
Click Save.
When you schedule a data feed, the Data Feed Manager validates the information. If any information is invalid, an error message will display. You can save the data feed and correct the errors later, but that data feed is not processed until the errors are rectified.
Important: A data feed must be active and valid to successfully run.
-
Go to the Schedule tab of the data feed that you want to modify.
-
From the menu bar, click
. -
Under Integration, click Data Feeds.
-
Select the data feed that you want to modify.
-
Click the Schedule tab.
-
-
In the Recurrences section, enter the frequency, start and stop times, and time zone for the data feed.
-
(Optional) In the Run Data Feed Now section, click Start to override the data feed schedule and run the data feed immediately.
-
Click Save. The following table describes the fields in the Recurrences section.
|
Field |
Description |
|---|---|
|
Frequency |
Specifies the interval in which the data feed runs.
|
|
Every |
Specifies the interval of the frequency in which the data feed runs. |
|
Start Time |
Specifies the time the data feed begins running. |
|
Start Date |
Specifies the date on which the data feed schedule begins. |
|
Time Zone |
Specifies the time zone in of the server that runs the data feed. |
-
Test the data feed to ensure that all device details from Tenable.sc were imported into the Devices application. If testing fails, try verifying the data feed and re-run the data feed. If you experience multiple failures, please contact your Archer Partner.
Certification environment
Date tested: July 2024
|
Product Name |
Version Information |
Operating System |
|---|---|---|
|
Archer Suite |
Archer 6.12 |
Virtual Appliance |
|
Tenable.sc |
NA |
NA |