Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Security / Tenable / Tenable Vulnerability Management API (Nessus)
Tenable Vulnerability Management API (Nessus) logo

Tenable Vulnerability Management API (Nessus)

Browse all Tenable APIs
57
AI ReadinessFoundational (C+)57/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticSecurityVulnerability ManagementapiKey93 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Launch vulnerability scans, export scan results, manage asset inventories, and track remediation progress across network infrastructure through Tenable's Vulnerability Management platform.

Use for: I need to launch a vulnerability scan against a subnet of hosts, Export all critical vulnerabilities found in the latest scan, Check the status of a running scan and retrieve preliminary results, Find all assets with a specific CVE vulnerability

Not supported: Does not handle endpoint detection and response, SIEM correlation, or application code analysis - use for network vulnerability scanning and asset assessment only.

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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Tenable Vulnerability Management API (Nessus) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tenable Vulnerability Management API (Nessus), or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftenable.com%2Ftenable-nessus" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftenable.com%2Ftenable-nessus" | 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.

Capabilities

What an agent can do with Tenable Vulnerability Management API (Nessus) API.

Launch and schedule vulnerability scans with configurable scan templates, targets, and credentials

Export vulnerability findings in bulk with filtering by severity, plugin family, and asset group

Track asset inventory with tagging, network segmentation, and vulnerability history

Query the plugin database for specific CVEs, CWEs, and vulnerability signatures

Manage Nessus agents for distributed scanning across networks without direct connectivity

Organize scans into folders with shared access and configurable retention policies

Generate workbench reports aggregating vulnerability data by asset, severity, or plugin family

Use Cases

Patterns agents use Tenable Vulnerability Management API (Nessus) API for, with concrete tasks.

★ AI Agent Vulnerability Assessment

An AI agent uses the Tenable API through Jentic to orchestrate vulnerability assessments, launching scans against target networks, monitoring scan progress, and exporting findings with severity scores and remediation guidance. The agent identifies critical vulnerabilities by CVSS score, cross-references affected assets, and generates prioritized remediation lists - all without manually configuring API key headers or discovering scan template IDs.

Launch a scan via POST /scans with a basic network scan template targeting a CIDR range, monitor status via GET /scans/{scanId}, then export results via POST /scans/{scanId}/export filtered to critical and high severity

Continuous Vulnerability Monitoring

Schedule recurring vulnerability scans across production infrastructure and track remediation progress over time. The API manages scan schedules, monitors completion status, and provides historical vulnerability data per asset. Security teams use the exports API to feed findings into ticketing systems, while workbench analytics reveal trends in vulnerability density and mean-time-to-remediation across organizational units.

Create a scheduled scan via POST /scans with a weekly recurrence rule, then query GET /scans/{scanId}/history to compare vulnerability counts across the last 4 scan runs

Asset-Based Risk Prioritization

Build a risk-prioritized view of infrastructure by querying the asset inventory with vulnerability enrichment. The API provides per-asset vulnerability counts by severity, tracks which assets have the highest exposure, and enables bulk export of asset data for integration with CMDB systems. Tag-based grouping allows teams to segment risk reporting by business unit, environment, or criticality tier.

Export the full asset inventory via POST /assets/export, check export status via GET /assets/export/{exportUuid}/status, then download chunks via GET /assets/export/{exportUuid}/chunks/{chunkId}

Bulk Vulnerability Data Export

Export large vulnerability datasets for offline analysis, compliance reporting, or SIEM ingestion. The chunked export API handles datasets with millions of findings by splitting results into downloadable chunks with status tracking. Exports can be filtered by date range, severity, plugin family, and asset tags to produce targeted datasets for specific compliance frameworks or audit requirements.

Initiate a vulnerability export via POST /vulns/export with severity filter for 'critical', poll status via GET /vulns/export/{exportUuid}/status until complete, then download each chunk

Key Endpoints

93 endpoints — jentic publishes the only available openapi specification for tenable vulnerability management api (nessus), keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/scans

Create and configure a new vulnerability scan

GET

/scans/{scanId}

Retrieve scan details and current status

POST

/scans/{scanId}/export

Export scan results in specified format

POST

/assets/export

Initiate bulk asset inventory export

GET

/assets/export/{exportUuid}/status

Check asset export job status

GET

/assets/export/{exportUuid}/chunks/{chunkId}

Download a chunk of exported asset data

GET

/plugins

List available vulnerability detection plugins

GET

/workbenches/assets

Query asset workbench with vulnerability summaries

POST

/scans

Create and configure a new vulnerability scan

GET

/scans/{scanId}

Retrieve scan details and current status

POST

/scans/{scanId}/export

Export scan results in specified format

POST

/assets/export

Initiate bulk asset inventory export

GET

/assets/export/{exportUuid}/status

Check asset export job status

GET

/assets/export/{exportUuid}/chunks/{chunkId}

Download a chunk of exported asset data

GET

/plugins

List available vulnerability detection plugins

GET

/workbenches/assets

Query asset workbench with vulnerability summaries

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

T

Tenable Vulnerability Management API (Nessus)

- Foundational (C+)
57/100
74
Foundational Compliance
63
Developer Experience & Jentic Compatibility
54
AI-Readiness & Agent Experience
86
Agent Usability
50
Security
30
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

0%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

54

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4
54%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

61%

Summary Coverage

Coverage of summaries across operations/tags/info.

86

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1
86%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

50

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

30

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1
30%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Tenable Vulnerability Management API by hand means learning its X-ApiKeys header auth (access key plus secret key) against the cloud.tenable.com host and handling scan, export, and chunked-download calls yourself. Through Jentic you install once, import the Tenable Vulnerability Management API from the API Directory, store the key pair once, and your agent calls it.

Permission scoping

This API puts the scan id in the URL path (/scans/{scanId}), so a rule can pin your agent to one scan: it can read and export that scan and nothing else. You choose the operations it may call, so launching new scans is not included unless you add it.

Credential isolation

Your Tenable access key and secret key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'scan hosts for vulnerabilities' or 'export scan results', and Jentic returns the matching Tenable operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Snyk API

Application dependency vulnerability scanning that complements Tenable's infrastructure scanning

Choose Snyk when the task involves software dependency and container image vulnerabilities rather than network-level infrastructure scanning

Complementary

CrowdStrike Falcon API

→

Endpoint threat detection that complements Tenable's vulnerability assessment

Choose CrowdStrike when you need real-time threat detection and incident response rather than periodic vulnerability scanning and asset assessment

Alternative

Rapid7 API

→

Competing vulnerability management platform with similar scanning and asset tracking capabilities

Choose Rapid7 when the organization uses InsightVM/Nexpose rather than Tenable for vulnerability management

FAQs

Specific to using Tenable Vulnerability Management API (Nessus) API through Jentic.

Why is there no official OpenAPI spec for Tenable Vulnerability Management API?

Tenable does not publish an OpenAPI specification for their Vulnerability Management platform. Jentic generates and maintains this spec so that AI agents and developers can call Tenable's API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Tenable Vulnerability Management API use?

The Tenable API uses API key authentication with two headers: X-ApiKeys containing both an accessKey and secretKey in the format 'accessKey={access_key};secretKey={secret_key}'. Through Jentic, both keys are stored encrypted in your Jentic One instance and agents receive properly formatted auth headers without raw keys entering context.

Can I launch a vulnerability scan programmatically with the Tenable API?

Yes. Use POST /scans to create a scan with a template UUID, target list (IPs, hostnames, or CIDR ranges), and optional credentials. Then launch it via POST /scans/{scanId}/launch. Monitor progress with GET /scans/{scanId} until status shows 'completed', then export results via POST /scans/{scanId}/export.

What are the rate limits for the Tenable Vulnerability Management API?

Tenable enforces rate limits based on your license tier. Standard accounts allow approximately 500 requests per minute for most endpoints. Export operations have separate concurrency limits (typically 2-3 concurrent exports). The API returns 429 status codes with Retry-After headers when limits are exceeded.

How do I export vulnerability findings in bulk through Jentic?

Search Jentic for 'export vulnerability scan results', which returns the POST /assets/export and related chunk download operations. Initiate an export with severity filters, poll the status endpoint until complete, then download each chunk sequentially. Install with pip install jentic and run it through Jentic One, the self-hosted execution layer.

Can I manage Nessus agents through the API?

Yes. The agent management endpoints let you list agents, create agent groups, assign agents to groups, and configure scan policies for agent-based scanning. Agent groups are useful for scanning hosts in network segments that lack direct connectivity from the scanner, such as DMZ or air-gapped environments.

Does the API support querying by specific CVE?

Yes. Use the GET /plugins endpoint to search for plugins by CVE ID, which returns the detection plugin details. The workbench endpoints also support filtering scan results by plugin ID or CVE to find all affected assets for a specific vulnerability across your infrastructure.

Can I limit what my agent is allowed to do with the Tenable Nessus API?

Yes. Because you run Jentic One yourself, your own rules decide which Tenable operations and credentials the agent may use. Since the scan id sits in the URL path, such as GET /scans/{scanId} and POST /scans/{scanId}/export, you can pin the agent to a single scan so it reads and exports that scan and nothing else. You pick the operations it may call, so launching new scans via POST /scans stays off unless you grant it.

GET STARTED

Start building with Tenable Vulnerability Management API (Nessus) API

Explore with Jentic One
View OpenAPI Document