Vulnerability Management: OT Connectors

Documentation is now available for OT connector endpoints. If your organization has Vulnerability Management and Tenable OT Security, you can use OT connectors to transmit assets and findings data from Tenable OT Security to Tenable Vulnerability Management. The new endpoints enable users to create, list, update, and delete OT connectors.

The new endpoints are described in the following table:

POST /sensorsCreate OT connectorCreates an OT connector.
GET /sensors/{type}List OT connectorsReturns a list of Tenable OT connectors.
GET /sensors/{type}/{id}Get OT connector detailsReturns details for the specified OT connector.
PUT /sensors/{type}/{id}Update OT connectorUpdates the specified OT connector. This endpoint can also be used to enable or disable an OT connector.
DELETE /sensors/{type}/{id}Delete OT connectorDeletes an OT connector.
POST /sensors/{type}/linking-keyGenerate linking keyGenerates a single-use linking key that is valid for two hours. Additionally, the target site for your account is retrieved (ex. us-2b).

For more information about OT connectors in Vulnerability Management, see OT Connectors in the Tenable Vulnerability Management User Guide. For more information about Tenable OT Security, see the Tenable OT Security User Guide.

Example: Generate a Linking Key

For example, to generate a linking key for use when creating an OT connector, you could use the following cURL request:

curl --request POST \
     --url \
     --header 'X-ApiKeys: accessKey=<YOURKEY>;secretKey=<YOURKEY>' \
     --header 'accept: application/json'

The request returns the x-linking-key and the x-target-site which are required when creating an OT connector.

  "x-linking-key": "8ea677141e65d7c6da2bc1022e69d0b8bf54b973353f78a3cf6063caf62feb32",
  "x-target-site": "us-2b"

Example: Create an OT Connector

To create an OT connector, we can use the generated x-linking-key and x-target-site to create an OT connector with a subType of icp:

curl --request POST \
     --url \
     --header 'X-ApiKeys: accessKey=<YOURKEY>;secretKey=<YOURKEY>' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --header 'x-linking-key: 8ea677141e65d7c6da2bc1022e69d0b8bf54b973353f78a3cf6063caf62feb32' \
     --header 'x-target-site: us-2b' \
     --data '
  "subType": "icp",
  "enabled": true,
  "name": "My OT Connector"