[GA] Tenable Patch Management 10.0 is officially LIVE! Experience the magic of simplicity.
Today, we are thrilled to unveil the latest evolution of Tenable Patch Management (TPM): The General Availability (GA) of TPM v10.0. This update represents a significant transformation of our product, designed to deliver on the promise of modern, frictionless, and autonomous patching. Big News: One Product, One Experience We have officially unified our product experience by retiring the "Express" vs. "Enterprise" distinction in favor of a Single SKU model. Whether you require high-speed simplicity or deep granular control, you no longer have to choose, every customer now has access to the full power of the Tenable patching engine. Experience the Magic of Simplicity TPM 10.0 reduces operational complexity by focusing on the daily workflow of the administrator. Here is what you will find inside: Administrator-first interface: Our new homepage prioritizes "Blind Spots" and "Delta Numbers," giving you an instant view of unpatched gaps and real-time changes in your environment. 6-step guided setup: A new interactive onboarding wizard replaces hours of manual setup, covering integration and device verification in minutes. "What, When, & How" strategy builder: Build complex patching strategies using a guided process focused on three simple questions: What are we patching? When is it happening? How should it behave? Deployment rings: We have evolved "Waves" into Deployment Rings with automated Transitions (Success, Approval, or Delay) to control exactly how patches move through your environment safely. The emergency kit: Access a "Global Pause" button, instant rollbacks, and exception controls directly from your dashboard for moments when you need to act fast. Advanced settings hub: We haven't removed the deep customization you love; we've just organized it. Features like Intent Schema and Flex Controls have moved to this hub to keep your main workspace clean. Enhanced RBAC (on-premise): We have introduced new built-in security roles for scoped access and security audits. Release details On-premise version: v10.0.971.19 (Server & Client) SaaS version: v10.0.971.18 (Server) | v10.0.971.15 (Client) Technical update: Both Server and Client have been updated to use Java 25 for peak performance and security. Migration & licensing: what it means for you Note: Your existing patching strategies and product configurations remain completely untouched by this upgrade and will continue to function exactly as designed. Customer type What happens today? Action required SaaS / Cloud Server: Your Console is updated to v10 automatically. Clients: Please follow the instructions here to upgrade your clients to v10. None. You have immediate access to v10 features. Your subscription transitions to the new model at your next renewal. On-premise Your choice. You remain on your current version until you choose to upgrade. Recommended: Contact us for a Zero-Dollar Exchange Order to unlock v10 features today, then download the update below. Transition to single SKU will be mandatory during renewal. Get started with these resources Explore these resources to hit the ground running: Download: Get TPM On-Premise v10.0 Changelog: View Release Notes At a Glance: What's New in TPM 10.0 Guide Release Demo: TPM 10.0 Video Walkthrough New User Guide: Single, Consolidated User Guide Docs: TPM Complete Documentation Log in now to experience the magic of simplicity combined with deep control. Happy Patching! — Ahmad Maruf Principal Product Manager, Tenable Patch Product Management
Tenable Core Account Expiry
APPLIES TO Tenable Core OPERATING SYSTEM(S) TenableCore DESCRIPTION Tenable Core, a lightly customized version of Oracle Linux 8, is hardened in accordance with security best practices including some elements of the CIS Level 1 benchmarks. One benchmark in particular has the potential to lock users out and expire their account: Default Security Configuration Standards 5.4.1.4 Ensure inactive password lock is 30 days or less This requirement means that user accounts will be automatically disabled after a period of 30 days of inactivity following password expiration. In order to prevent this, Tenable Core users should log into the cockpit (8000) or SSH at least once every 365 days and update their account password to prevent it from expiring, which in turn prevents the account from becoming locked out. INFORMATION Please log into Tenable Connect to view the following additional resources and access more support. If your account has already expired due to the above requirement, the following knowledge base article will help to resolve it: Unable to Sign Into Tenable Core "Authentication failed: internal-error" For a physical hardware hosted Tenable Core instance, this may require a keyboard and monitor hooked up or serial access. If needed, steps 10-15 of the following article can be used to attach to the serial console for direct interaction: Installing a new platform via USB for Tenable OT Security Hardware Appliances For Tenable OT Security environments, please see Leveraging the Remote Unlock Feature in Tenable Core for instructions on how to remotely unlock administrative accounts on Tenable Core machines.