tenable vulnerability management
81 TopicsTenable VM API Change - Coming Jan 19, 2027
The “list_scans” API endpoint will be updated to enforce pagination on January 19, 2027. When this change occurs customers will need to be aware of the following: By default the number of returned scans will be limited to 200 The maximum number of returned scans will be limited to 5000 These are set by the “limit” integer in the API query Please see the attached announcement for full details.11Views0likes0CommentsTenable Product Update Newsletter - October 2026
Welcome to your monthly round-up of the latest Tenable product updates, platform enhancements, and community news. This month, we’re expanding visibility into AI agent identities, bringing OT assets into Tenable One, and adding enterprise-grade security vetting to the CyberAgents Exchange. Tenable One - Platform Updates Claude Mythos 5 is available in Tenable One with Adversary View Tenable One Adversary View, powered by Claude Mythos 5, helps you detect previously unseen vulnerability chains based on adversarial reasoning to help you take decisive action faster than ever. Available for Tenable One customers with Tenable Hexa AI, Adversary View helps you: Reveal hidden attack paths by connecting non-obvious relationships between vulnerabilities that create real, exploitable chains — the kind no single rule can catch. Get evidence-backed recommendations with ranked remediation actions and the supporting evidence behind them, so your team knows exactly what to fix first. Act immediately with Tenable Hexa AI to turn Adversary View's recommendations directly into automated remediation workflows. You can enable Adversary View in your Tenable One account by turning on Frontier AI models in Tenable Hexa AI settings. Check out the technical documentation Explore the guided demo Two new connectors bring Invicti and Chrome OS into Tenable One Tenable One combines your third-party security tools with Tenable’s native sensor data for one view of risk across the entire attack surface. Two new connectors extend that reach to web application scanning and endpoint inventory: Invicti and Chrome OS. Invicti Connector: Brings Invicti’s dynamic application security testing (DAST) findings into Tenable One, ingesting scanned web applications along with their vulnerabilities and misconfigurations, complete with severity, Common Vulnerabilities and Exposures (CVE), and Common Vulnerability Scoring System (CVSS) data. Chrome OS Connector: Pulls managed Chrome OS device inventory straight from Google Workspace into Tenable One, including hardware identity, OS version, network identifiers, org-unit placement, enrollment lifecycle, and security hardware details. Learn more about the Invicti Connector Learn more about the Chrome OS Connector CyberAgents Exchange Build open-source security agents at SWARM Global, Nov. 2-6 SWARM Global is a free, virtual agentic AI build event, sponsored by Tenable with support from Anthropic, where security practitioners build open-source AI agents, skills, and MCP servers for real security workflows. Build solutions for workflows like alert triage, remediation orchestration, and executive reporting. Teams are one to three people, all skill levels are welcome, and there’s no travel or entry fee. Kickoff is on Nov. 2, followed by tutorials and office hours with Tenable engineers. Selected teams pitch live to Tenable and Anthropic judges on Nov. 5. $10,000 in Claude credits is split among first-, second-, and third-place teams. Winners also get a free pass to EXPOSURE 2027 and publication to the CyberAgents Exchange. Winners are announced in a live awards broadcast on Nov. 6, open to everyone, even if you don’t build. Registration closes Nov. 1. Teams bring their own large language model (LLM) subscriptions, and all code must be open-sourced (MIT preferred), per the SWARM Global November 2026 Contest Official Rules. Register today Join the Discord Open-source AI agents, now with enterprise-grade security review The CyberAgents Exchange AI Inspector now reviews select community-built listings on the CyberAgents Exchange and awards those that pass an “Exchange Inspector vetted” tag, further accelerating enterprise security adoption of open-source AI agents, skills, and Model Context Protocol (MCP) servers. Three-step review: Automated screening with Tenable One AI Exposure, frontier assessment by OpenAI GPT cyber models, and hands-on verification by Tenable security researchers. First vetted listings: SOC-Hunter, the Splunk Tenable Cloud Security Skill, and the Remediation Priority & Impact Agent Built through Tenable’s participation in the OpenAI Daybreak Defense Network, the Exchange Inspector is the first major release from that collaboration. Everything on the Exchange stays free and open source. Browse vetted listings Read the blog Read the full security review process Tenable One Vulnerability Management Prioritize what matters: Top 25 Exploitable and Unsupported Exposures dashboard When every finding feels critical, deciding where to focus your remediation is tough. The Top 25 Exploitable and Unsupported Exposures dashboard helps you pinpoint active threats across your environment by organizing your highest-risk vulnerabilities, affected systems, and exact fix paths into a single view. Check out the new dashboard today. Learn more Streamlined integration: OAuth support for Jira and ServiceNow You can now connect to Jira and ServiceNow using OAuth authentication. This eliminates the requirement for admin-level accounts in your target tools, making it easier to comply with internal least-privilege policies and speed up integration sign-offs. OAuth is an optional connection type. Your current integrations will continue working with zero disruption, allowing you to update your setup whenever your team is ready. Read the release notes Tenable One Cloud Exposure Get visibility into Microsoft Entra Agent ID identities AI agents are being developed at a rapid pace and are becoming a new class of identities, giving security teams a way to see and govern them before they become a blind spot. Tenable One Cloud Exposure now supports Microsoft Entra Agent ID identities by automatically discovering and tagging agent identity blueprints, their principals, agent identities, and agent users. Security teams can discover more, catch more excessive privileges, and examine blueprints. Now, you can see these identities next to your other non-human identities in Tenable One Cloud Exposure. Why it’s important: Discovery and inventory: Auto-discovering and tagging each of the four object types, then listing them in the inventory, gives you a baseline of which agents exist and how they relate to each other. Permission and configuration auditing: Agents are often over-permissioned because it’s easier to grant broad access than to scope it tightly. Being able to inspect properties lets you catch excessive privileges, risky configurations, and ownerless agents. Hierarchy analysis and supply chain risk: Explorer queries let you trace blueprints to their agents (top-down) or agents back to their blueprints (bottom-up). That matters because one compromised or misconfigured blueprint, including one shared across tenants, passes the problem to every agent built from it. Read the blog Read the product documentation Tenable One OT Exposure Your OT and IT assets, one unified view Our latest Tenable One OT Exposure release brings OT assets, findings, and policy violations into the Tenable One platform through an updated data pipeline. You get one place to see and manage exposure across your converged environment. View OT assets alongside IT assets in a single, unified view, with no need to switch between tools to understand your full attack surface. Apply asset tags and role-based access control to OT assets, so the right teams see the right data and can organize and prioritize work the way you already do for IT. Connect OT findings and policy violations with data from other Tenable products to get context to understand risk that spans IT and OT. Assets, findings, and policy violations now flow through the updated Tenable One data format and APIs, replacing the legacy pipeline. Fixes and performance improvements: A range of bug fixes and performance enhancements make day-to-day use smoother. Update today to put these new capabilities to work in your environment. Explore the release notes Tenable Security Center Simplified deployment for shared database environments Our latest release delivers an enhanced database installer to ensure installation succeeds in environments with existing PostgreSQL schemas, reducing deployment complexity in shared database environments. Flexible PostgreSQL installation: The installer now handles non-empty public schemas that contain non-Tenable Security Center tables. This reduces deployment complexity and removes a common roadblock in shared database environments. Fixes for upgrades, scanning, and more: This release also includes bug fixes that improve upgrade reliability, scan accuracy, scan result cleanup, and query performance with certain HTTPS certificate configurations. Update today to apply these new improvements to your environment. Explore the release notes Tenable Nessus Tenable Nessus 10.12.5 focuses on plugin update security Tenable Nessus 10.12.5 was released on Oct. 1, with a focus on strengthening how Tenable Nessus handles plugin updates. Here are the highlights: Stronger plugin security: Multiple conditions related to memory-safety and denial-of-service conditions in plugins have been addressed. Plugin archives pushed through the legacy update channel now require a valid Tenable signature before they are extracted or loaded. Scan policy import fix: An SQL injection vulnerability in the scan policy import functionality has been resolved. Signature file required for manual plugin updates: Manual plugin updates for Tenable Nessus and Tenable Nessus Manager now require the signature file. Tenable Security Center plugin updates, Tenable Nessus Manager’s agent plugin updates, and Tenable Nessus application updates are not affected. If you update plugins manually, such as in air-gapped environments, please ensure the signature file is a part of your process. New platform support: Tenable Nessus now supports AlmaLinux 10. And much more. You can upgrade directly from any previously supported version. We recommend reviewing the notes for any versions you skip. Read the release notes Review the Tenable Product Security Advisory (TNS-2026-17) Tenable Patch Management Intelligent rollbacks, expanded Linux coverage, and hardened platform security You shouldn’t have to risk breaking critical applications just to keep your fleet secure. Rollbacks exist to restore stability, not rip out host applications and force a manual cleanup. The latest release includes: Smarter rollbacks: Real-time client checks prevent destructive application removals during patch uninstalls. Expanded fleet support: Complete native coverage for Fedora 44 and Ubuntu 26.04 Long-Term Support (LTS). Hardened core infrastructure: Upgraded libraries (Tomcat, Log4j, Java Runtime Environment) and fortified client MSIs to secure token use and file access. Read the Connect post View the release notes Tenable events and webinars Customer office hours These are recurring ask-me-anything sessions for Tenable Security Center, Tenable One Vulnerability Management, Tenable One Cloud Exposure, Tenable One Identity Exposure, and Tenable One OT Exposure. Time-zone-appropriate sessions are available for the Americas, Europe (including the Middle East and Africa), and Asia-Pacific. Learn more and register Virtual events Tenable customer update - October 2026: Watch the quarterly customer update session - now on demand! This informative, fast-paced overview will explore how to better secure your expanding attack surface and consolidate critical security data. Products covered include Tenable One, Tenable One Vulnerability Management, and Tenable Patch Management. Watch on demand See all upcoming live and on-demand webinars Vetting open-source AI agents with OpenAI GPT cyber models: Join us at 11:30 a.m. ET, Wed., Oct. 28, on LinkedIn to learn how to review open-source AI agents, skills and MCP servers before you put them to work in real security workflows. Attend on LinkedIn Read Tenable documentation.370Views0likes0CommentsResearch Release Highlight: New Keeper Commander PAM Integration
Summary Tenable is proud to announce a new integration with Keeper Commander for use with Keeper Security providing streamlined privileged access in credentialed vulnerability scans. This integration is available in Tenable One Vulnerability Management and Tenable Nessus. Change Supported Credential Types: SSH, including privilege escalation (e.g., sudo) and SSH key-based authentication (with optional passphrase) SMB (Windows), including domain and Kerberos authentication Database: Oracle, SQL Server, MySQL, PostgreSQL, MongoDB, DB2, Cassandra, Sybase ASE ESXi: VMware vSphere hypervisor credentials vCenter: VMware vCenter Server credentials Nutanix: Nutanix Prism Central credentials For comprehensive details regarding this integration, please refer to the Tenable user https://docs.tenable.com/Integrations.htm. Impact There is no disruption to existing scan configurations. Customers using Keeper Security for privileged access management are encouraged to adopt this integration for credentialed scanning to consolidate credential management and reduce risk from static credentials stored in scan policies. Release Date 8 October 2026 for Tenable One Vulnerability Management and Tenable Nessus TDB for Tenable Security CenterImprovement To Plugin 142960 “HSTS Missing From HTTPS Server (RFC 6797)”
Summary Plugin 142960 now validates the identity of an HTTPS service in line with the current RFC 9525 as opposed to the obsolete RFC 6125. When a service's TLS certificate contains Subject Alternative Name (SAN) entries, the plugin compares the target hostname against those SANs only and no longer considers the certificate's Common Name (CN). If the certificate has no SANs, the plugin falls back to using the CN, so coverage for legacy certificates is unchanged. Background Plugin 142960 checks whether a detected web server supports HTTP Strict Transport Security (HSTS). Before it evaluates the service, the plugin must confirm that the service's TLS certificate covers the identity of the host. This confirms that the server is authorized to answer for that host, and that the finding describes the target host and not whichever service happened to respond on its behalf. If the identity check fails, the plugin cannot evaluate the service. Until now, the plugin performed this check by comparing the resolvable hostname against the CN of the certificate presented on the relevant port. If the CN covered the hostname, the service was evaluated for HSTS. RFC 9525, which supersedes the identity-matching guidance in RFC 6125 (which allowed for the checking of CNs) states that when a certificate carries one or more SAN entries, hostname identity must be validated against those SANs only. The CN must not be used for this purpose, even if it matches the hostname. The RFC gives several reasons: the CN is ambiguous, it cannot hold multiple identifiers, and its use leads to security and parsing inconsistencies. This change was prompted by a case in which a host's service could only be identified through the SAN of its certificate and not through the CN. Research into that case led to RFC 9525, and the update follows its guidance. Changes Service identity validation in plugin 142960 now works as follows: If SANs were enumerated from the service's TLS certificate, the hostname is compared against the SANs only. The CN is not used, even when it matches the hostname. If no SANs were enumerated from the certificate, the plugin uses the CN to validate the service identity, as it did before. Impact For services whose certificates include SANs, the outcome of the identity check depends only on the SAN values. A service whose SANs cover the hostname but whose CN does not will now be validated and evaluated for HSTS. A service whose CN matches the hostname but whose SANs do not will no longer pass validation, so the plugin will not evaluate it. Services with certificates that have no SANs are evaluated as before. Affected Plugins 142960 - HSTS Missing From HTTPS Server (RFC 6797) Targeted Release Date Monday, October 12, 2026Tenable Product Update Newsletter - September 2026
Welcome to your monthly round-up of the latest Tenable product updates, platform enhancements, and community news. This month, we’re bringing frontier AI reasoning into exposure management, deepening cloud and vulnerability visibility, and expanding how the community vets AI agents before deployment. Tenable One - Platform updates Claude Mythos 5 is coming to Tenable One with Adversary View Attackers don’t exploit systems in isolation. They chain together scattered, low-signal evidence like netstat entries, cached accounts, and active connections that traditional rules engines can’t connect, and that your team doesn’t have time to piece together manually. This is where frontier AI models shine. Tenable One Adversary View, launching this September, brings the power of Anthropic’s Claude Mythos 5 directly into the Tenable One Exposure Management Platform. Built on the Project Glasswing collaboration between Tenable and Anthropic, Adversary View applies advanced cyber reasoning to your existing exposure data, uncovering hidden vulnerability chains, visualizing how an attacker would actually move through your environment, and surfacing evidence-backed fixes to break those chains before attackers exploit them — all within an agentic harness that keeps the AI’s reasoning controlled and auditable. Take advantage of Claude Mythos 5 to tackle complex exposure management challenges. Cut through the noise with a ranked, prioritized list of the vulnerability chains that matter most, backed by evidence and specific remediation guidance. Move at the speed of adversaries by pairing Claude Mythos 5’s advanced reasoning with the exposure intelligence you already have in Tenable One — no new tools required. Read the blog post Explore the guided demo 3 new connectors bring GitHub and GitLab findings into Tenable One Tenable One connectors combine your third-party security tools with Tenable’s native sensor data for one view of risk across your attack surface. Three new connectors extend that coverage, pulling static application security testing (SAST), software composition analysis (SCA), and secret scanning findings straight into Tenable One. GitHub Code Scanning: Consolidates SAST and secret scanning findings, covering both vulnerable code and exposed credentials, into the same risk view as every other exposure you track. GitHub Dependabot: Brings SCA alerts on vulnerable dependencies, so a flawed package deep in your supply chain gets prioritized against everything else exposing you. GitLab Connector: Covers SAST, SCA, and Secret Detection findings in one connector, consolidating what’s otherwise split across multiple tools into a single risk view. Requires GitLab Ultimate to ingest findings. All three are native connectors; add the connector, and findings start showing up in Tenable One. Set up GitHub Code Scanning Set up GitHub Dependabot Set up GitLab Connector CyberAgents Exchange Exchange Inspector vets AI agents before they reach your environment Tenable and OpenAI unveiled the CyberAgents Exchange AI Inspector, which pairs OpenAI’s GPT cyber models with Tenable One AI Exposure and expert researcher review to screen AI agents, skills, MCP servers, and multi-agent playbooks for prompt injection, PII exposure, and supply-chain risks before they’re deployed. Combines OpenAI GPT cyber models, Tenable One AI Exposure, and expert researcher review to vet AI agents before deployment. Screens AI agents, skills, MCP servers, and multi-agent playbooks for prompt injection, PII exposure, and supply-chain risks. Gives practitioners insight into production-ready AI agents and CISOs the confidence to approve their use. The Exchange Inspector builds on the CyberAgents Exchange registry, which has already drawn more than 100 AI listings. Exchange Inspector is expected to be available in September. Read the technical blog Read the press release Tenable One Vulnerability Management Visualize your security trends over time You can finally see exactly where your security metrics are heading, not just where they stand today. With newly added Trending Widgets, you can track your asset data and findings as daily line charts, giving you the historical context you need to accurately monitor your progress. Data collection begins the moment you set up a widget. To get started, you can: Build custom views: Add up to five unique trend lines per widget, tailoring the dataset, entity type, and filters for each. Deploy pre-built charts: Search trending in the widget library to drop ready-to-use visualizations right onto your dashboard. Check out the Trending Widget documentation Release notes for the full details Tenable One Cloud Exposure Expanded Kubernetes and container topology in Tenable One Cloud Exposure A comprehensive overview of Kubernetes and container topology is essential for risk-based prioritization because you have to see the whole picture of the resources, workloads, and clusters a vulnerability touches to know what’s actually risky. Now, the “graph” tab in Tenable One Cloud Exposure gives you the full structural layout of a Kubernetes cluster, all the way down to a vulnerable container image, in one interactive view. What’s new: Guided relationship picker: By expanding any node in the graph, it now surfaces a categorized menu (Compute, IAM, Kubernetes, Containers, Management, Network, Risk) so you can choose which connection to explore next. Full Kubernetes depth: Namespaces, roles, role bindings, service accounts, configuration maps, and workloads all surface as first-class nodes, whether the cluster is EKS, AKS, GKE, or self-managed. The Kubernetes graph provides a holistic view of cluster contents, namespaces, and resource relationships, while allowing you to effortlessly navigate from clusters to underlying virtual machines and specific workloads, such as business-critical services. It also enables you to explore vulnerability instances linked to container images, ensuring they have complete context for risk prioritization and informed decision-making. View the demo Check out the product documentation Tenable Nessus Nessus reliability and performance updates We have released several Tenable Nessus updates recently, with a mix of new capabilities as well as improvements related to performance and security. Scanner reliability fixes: Resolved SSL connection issues that could cause scanners to appear offline and stop receiving plugin updates. Kerberos authentication fix: Corrected an issue blocking plugins from retrieving host FQDNs, causing authentication failures. Tenable Security Center performance: Fixed timeout errors when processing large volumes of Tenable Nessus agent reports. Certificate handling: Resolved an issue in PostgreSQL client authentication. Review Nessus documentation Read the Plugin Release Notes Take Tenable University training Training and product education Tenable Patch Management training Upgrade your skills with the refreshed, free on-demand Introduction to Tenable Patch Management course in Tenable University. Modernized with interactive elements, real-time knowledge checks, and step-by-step video demonstrations, this self-paced web training gives you hands-on practice to efficiently secure both your SaaS and on-premises environments. Through this updated course, you will learn to: Understand core architecture: Master essential server and client components, operating system coverage, and fundamental patching logic. Optimize configuration and strategy: Configure locations and business units while implementing proven patching strategies across your enterprise. Execute global operations: Swiftly respond to critical threats using the Emergency Kit. Eliminate blind spots: Monitor real-time compliance health and identify hidden vulnerabilities using dynamic performance widgets and interactive dashboards. Access this free course today in Tenable University to strengthen your remediation workflows and keep your organization secure. Learn more Tenable events and webinars Customer office hours Customer office hours are recurring ask-me-anything sessions for Tenable Security Center, Tenable One Vulnerability Management, Tenable One Cloud Exposure, Tenable One Identity Exposure, and Tenable One OT Exposure. Time-zone-appropriate sessions are available for the Americas, Europe (including the Middle East and Africa), and Asia-Pacific. Learn more and register Virtual events Tenable customer update - October 2026: Join the next quarterly customer update session at 11 a.m. ET / 4 p.m. BST / 5 p.m. CEST Oct. 20. This informative, fast-paced overview will explore how to better secure your expanding attack surface and consolidate critical security data. Products covered include Tenable One, Tenable One Vulnerability Management, Tenable Security Center, and Tenable Patch Management. Register here See all upcoming live and on-demand webinars TenableTalk Live: How Mythos will change cyber defenses forever: Join us at 11 a.m. ET, Thursday, Sept. 24, on LinkedIn as we dive into what happens when frontier AI reasoning gets built directly into the tools defenders use, and how teams can prepare for these new capabilities. Attend on LinkedIn Tenable Professional Services Tenable Hexa AI enablement workshop Confidently adopt Tenable Hexa AI and the Tenable Hexa AI Model Context Protocol (MCP) Server with expert, hands-on guidance tailored to your environment. Delivered by Tenable Professional Services as a custom Statement of Work (SOW) engagement, this new workshop equips your team with practical skills to maximize your AI-driven exposure management capabilities. Through this custom engagement, you will: Explore enterprise AI capabilities: Analyze your internal AI tool usage and complete a technical overview of Tenable Hexa AI. Build practical expertise: Receive hands-on instruction to effectively operate Tenable Hexa AI and integrate the Tenable MCP Server into your tech stack. Design custom workflows: Develop tailored operational workflows and implement proven best practices to accelerate risk reduction. To scope a custom workshop for your organization, contact your Tenable representative or email [email protected]. Read Tenable documentation.829Views0likes0CommentsTenable product update: Standardizing Tenable risk scoring
At Tenable, we are committed to providing the most accurate, defensible, and actionable view of organizational risk. To achieve this, we must continually refine the intelligence that powers your prioritization. On July 1, 2026, we are implementing a series of foundational updates to our risk scoring engines. As part of this update, you may see changes to your risk scores, depending on the Tenable product(s) you own. These changes simplify your workflow by standardizing scoring on a single, high-fidelity model for vulnerability and asset risk. The new standard for VPR For the past several months, many of you have utilized VPR (Beta) to gain deeper insights into exploitability. We are excited to announce that on July 1, this model will be promoted to the primary Vulnerability Priority Rating (VPR) across the Tenable platform. By standardizing on this advanced model, we are retiring legacy VPR scoring to ensure every customer benefits from our most sophisticated threat intelligence. The new version of VPR incorporates more threat intelligence and vulnerability metadata so that you can focus on the 1.6% of vulnerabilities that actually matter. Better context through enhanced asset classification Alongside the VPR update, we are enhancing our asset classification engine. This update improves how we identify the function and importance of assets across your entire attack surface, including Cloud, OT, and third-party devices. As a result, customers with access to Asset Criticality Ratings (ACR) for VM assets will see these scores more accurately reflect real-world business risk. What this means for you These are backend enhancements designed to provide immediate value with zero manual configuration. On July 1, your dashboards, reports, and APIs will automatically reflect these updated metrics. Because both VPR and ACR serve as inputs to Cyber Exposure Score (CES) and Asset Exposure Score (AES), customers using these scores may see changes that reflect a more accurate understanding of exposure. Customer FAQ What happens to the VPR (Beta) score in the Tenable UI? The Beta label will be removed. The high-fidelity model you’ve been previewing will become the standard VPR. The legacy version of VPR will be retired to ensure a single, unified source or truth. Do I need to rewrite my custom API scripts using VPR? No. For customers using APIs, updated values will be mapped into legacy VPR fields on the back end to ensure compatibility and a smooth transition for your scripts and third-party tools. How does this affect my SLAs? Because many organizations use VPR as their operational prioritization layer, your SLA statistics and remediation tracking will now reflect the more precise scoring model. This helps ensure your team is meeting response goals for the vulnerabilities that pose the highest actual risk. How does Enhanced Asset Classification affect my scores? The system now automatically identifies the function and criticality of assets across Cloud, OT, and third-party sources. This improved context leads to more accurate Asset Criticality Rating (ACR) adjustments. For customers with access to ACR, this ensures your most critical business assets are effectively prioritized. What actions does my team need to take, and when will the changes be reflected in my container? These updates will occur automatically within your Tenable console. Depending on the size of your environment, it may take time for score recalculations to be fully reflected across your console. For a detailed guide on our enhanced VPR, check out this FAQ. Want to see the why behind our scoring? View our scoring explained.7KViews9likes13CommentsArcon Converged Identity (CI) Platform
Summary Tenable One Vulnerability Management and Tenable Security Center now fully support the Arcon Converged Identity (CI) PAM solution. Using the existing Arcon PAM authentication type alongside Digital Vault API configuration, customers with Arcon CI-PAM can seamlessly retrieve credentials during scans. Change No new scan configuration fields or credential types are required. Customers using Arcon CI-PAM should configure the Authentication URL and Engine URL to point to the Digital Vault API base path (e.g. dv/api/sdk), as with Arcon DV deployments. Impact No changes to existing scan configurations are required. Customers currently using the legacy Arcon PAM API path are unaffected. Release Date 8 September 2026 for Tenable One Vulnerability Management, Nessus and Tenable Security CenterNew Microsoft Azure Key Vault Integration
Summary We are pleased to announce that Tenable's credentialed scanning now supports Microsoft Azure Key Vault as a Privileged Access Management (PAM) integration. This will be available in Tenable One Vulnerability Management and Tenable Nessus Immediately. Change Tenable's credentialed scanning has been updated to include Microsoft Azure Key Vault as a new authentication method. Security teams can now store privileged credentials in Azure Key Vault and have Tenable retrieve them automatically at scan time using OAuth2 client-credentials authentication with a Microsoft Entra ID service principal. Credentials such as sensitive passwords and SSH private keys are maintained centrally inside the vault, they are never stored in Tenable scan policies and can be rotated seamlessly without requiring manual policy updates. The Azure Key Vault integration supports the following credential types: SSH Windows (SMB) Database (Oracle, SQL Server, MySQL, PostgreSQL, DB2, MongoDB) VMware ESXi SOAP API VMware vCenter API Nutanix Prism Central Each Key Vault secret is expected to hold a JSON object containing one or more of the fields username, password, ssh_key, ssh_keyphrase, and domain, so a single secret can drive both password and SSH private-key-based target authentication. For SSH targets, privilege escalation may optionally reference a separate Key Vault secret whose password field is used as the sudo/su password. For more information see our Microsoft Azure Key Vault Integration user documentation: https://docs.tenable.com/Integrations.htm Impact No impact to current scans are expected; If customers encounter issues with this integration, please open a ticket with Technical Support. Release Date September 3, 2026 for Tenable One Vulnerability Management and Nessus TBD for Tenable Security CenterArcon PAM New Digital Vault API Support
Summary Tenable is proud to announce expanded support for the Arcon Privileged Access Management (PAM) integration in Nessus. The integration now supports the Arcon PAM Digital Vault (DV) API. Customers who have migrated to Arcon DV deployments can now retrieve credentials through Nessus scans without requiring new credential types or additional scan configuration fields. This integration automatically selects the correct API path based on the Authentication URL and Engine URL configured in the scan credential. If the configured URLs contain dv/api/sdk, the Digital Vault path is used; otherwise the legacy path is used. No new scan configuration fields are required. Further information regarding these changes and configuration guidance for both API paths can be found in the Arcon section of Tenable's Integrations documentation page. Change The Arcon PAM credential now supports the Digital Vault API path alongside the existing legacy API. The DV path uses a distinct authentication endpoint and credential retrieval endpoint. These differences are handled automatically by the integration based on the URLs the user configures. Customers on DV deployments should set the Authentication URL and Engine URL to point to the DV base path (e.g. dv/api/sdk). Impact Existing scan configurations using the legacy API path remain unaffected. No changes to existing scan configurations or credentials are required for customers already using the legacy API. Release Date August 25, 2026 for Tenable One Vulnerability Management and Nessus TBD for Tenable Security CenterVMware Integration vSphere 9.0 Compatibility
Summary We are pleased to announce that Tenable's VMware integration for vulnerability scanning now supports VMware vSphere 9.0 (ESXi 9.0 and vCenter Server 9.0). These updates will be available in Tenable Vulnerability Management, Nessus, and Tenable Security Center. Change Tenable has updated its VMware integration to support VMware ESXi 9.0 and VMware vCenter Server 9.0. Authenticated vulnerability scans can now be performed on these targets without the need for additional credential setup. VMware vSphere 9.0 compatibility covers the following scenarios: VMware ESX SOAP API authenticated scans against ESXi 9.0 hosts VMware vCenter API authenticated scans against vCenter Server 9.0 VMware vCenter auto-discovery flows for 9.0 hosts For more information see our user documentation: Welcome to Tenable for VMware Impact No impact to current scans are expected; existing ESXi 8.x and earlier vCenter scans continue to work as before. If customers encounter issues with this integration, please open a ticket with Technical Support. Tenable will engage with VMware as needed to identify and resolve any issues. Release Date Available Immediately (May 27, 2026) for Tenable Vulnerability Management, Nessus, and Tenable Security Center Note: TDB for updates to enable VMware ESXi 9.0 and VMware vCenter Server 9.0 compatibility with Compliance and Audit scanning.