List scans visible to the authenticated API key, optionally filtered by folder ID. Returns id, name, status, and last run time per scan.

Get the latest results for a single scan by ID: hosts scanned, per-plugin findings, and vulnerability counts by severity.

List assets known to Tenable.io / Tenable One (hostname, IPs, UUID, last seen, sources). Capped at limit records to keep responses small.

Get full detail for a single asset by UUID: network interfaces, installed software, tags, and exposure scores (ACR/AES) if licensed.

Search current findings across the tenant via the vulnerability workbench. Filter by CVSS severity (any of "info", "low", "medium", "high", "critical" — case-insensitive) and/or plugin family (e.g. ["Windows", "Web Servers"]). Returns per-plugin aggregate records including CVSS severity, VPR score, and affected asset count. Capped at limit records.

Get full plugin detail: description, solution, CVSS vectors, CVEs, and VPR drivers for a given Tenable plugin ID.

List all asset tag categories and values configured in the tenant.

List Nessus Agents linked to the tenant with status, platform, and last connect / last scanned timestamps. Capped at limit records.

Build a before/after re-prioritization table for live findings: CVSS-based severity vs. VPR-based severity, per plugin, with a 'rerating' flag (escalated / downgraded / unchanged / unrated) and affected asset count. Designed for POC/assessment deliverables that need to show clients how VPR re-ranks their existing scan data (e.g. a Tenable One CTEM engagement). Escalated findings are sorted first since they represent the highest-priority remediation gap a CVSS-only view would have missed.

Optionally filter the underlying findings by CVSS severity and/or plugin_family before comparison, same as search_vulnerabilities.

Cross-reference live findings against two independent, publicly sourced exploitation signals (not Tenable's proprietary VPR):

• CISA KEV: CVEs with confirmed real-world exploitation

• FIRST.org EPSS: probability of exploitation in the next 30 days

Useful alongside compare_vpr_reprioritization to back a re-prioritization argument with vendor-independent evidence. Each finding gets a signal: confirmed_exploited > high_probability > low_signal > no_cve_data, sorted most urgent first.

limit bounds how many distinct plugins get a CVE lookup (one extra Tenable API call per plugin), so keep it modest for interactive use. Filter the underlying findings by CVSS severity and/or plugin_family first, same as search_vulnerabilities.

Compare a baseline scan against a re-test scan by plugin ID and return three buckets: fixed (present in baseline, gone in re-test), still_open (present in both), and new_since_baseline. Includes a remediation-rate percentage. Built for pentest/assessment re-test reporting where a client needs proof of what got remediated between engagement rounds.