Tenable APIs

4 APIs332 Endpoints4 Categories

API Catalog

Attack Surface Management

Attack Surface Management API. The API exposes 74 endpoints secured with apiKey authentication.

74 endpoints

Identity Exposure

API to interact with Identity Exposure. The API exposes 131 endpoints secured with apiKey authentication.

131 endpoints

The Tenable Managed Security Service Provider (MSSP) Portal API provides a secure and accessible way for MSSP administrators to manage and maintain multiple customer instances of Tenable products. Endpoints in the Tenable MSSP Portal API enables customers to view and manage your MSSP customer accounts. For more information about the Tenable MSSP Portal, see the [Tenable MSSP Portal User Guide](htt. The API exposes 34 endpoints secured with apiKey authentication.

34 endpoints

Tenable Vulnerability Management API (Nessus)

Jentic publishes the only available OpenAPI specification for Tenable Vulnerability Management API (Nessus), keeping it validated and agent-ready. Configure and execute vulnerability scans, export findings, manage assets, and track remediation progress across 93 endpoints covering scan lifecycle management, plugin-based detection, agent management, and workbench analytics. The API provides programmatic access to Tenable's vulnerability database with severity-scored findings, CVSS ratings, and asset-level risk prioritization for infrastructure spanning on-premise servers, cloud instances, and containerized workloads.

93 endpoints

Connect Your Agent

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.