Identification Files

Sensor Proxy has two identification files:

• UUID — Sensor Proxy creates the UUID and saves it to /etc/sensor-proxy-uuid when you start the Sensor Proxy service for the first time. You can also find the UUID in /opt/sensor_proxy/logs/sidecar.log:

  2023/12/11 05:47:00.331866 [info] [service] Sensor Proxy is identified by <UUID>

  2023/12/11 05:47:00.920269 [info] [link] Linked successfully to http://sensor.cloud.tenable.com

• Authorization token — Sensor Proxy obtains the authorization token from Tenable Vulnerability Management or Tenable Security Center when Sensor Proxy successfully links to it and saves the token to /etc/sensor-proxy-token.

  Note: Whether a Tenable Nessus Agent or Tenable Nessus scanner links directly to Tenable Vulnerability Management or to a Sensor Proxy, they similarly obtain and store an authorization token in the secure preferences database (nessus-fetch.db). When linking to a Sensor Proxy, they obtain the token from the Sensor Proxy.