GA Announcement – Tenable App for Microsoft Sentinel v3.1.2
Release Date: April 16, 2026 Hi everyone! We’re excited to announce the general availability (GA) of version 3.1.2 of the Tenable App for Microsoft Sentinel! This release includes minor enhancements and version updates to help you get the most from your integration. Resources Download & Install: Tenable App for Microsoft Sentinel – Azure Marketplace Documentation: Installation & Upgrade Guide What’s New Multiple rsyslog Support: Updated the Tenable IE (TIE) data connector UI to support multiple rsyslog configurations. Schema Updates: Updated the Tenable VM Vulnerability and Tenable WAS Vulnerability table schemas within the ARM Template for the Tenable Vulnerability Management data connector. SDK Optimization: Updated the Tenable Vulnerability SDK method to utilize indexed_at instead of last_found for improved data handling. We recommend you upgrade to v3.1.2 to ensure full support for these latest schema changes and connector enhancements. Questions? We’re here to help! Reach out to us in connect.tenable.com — Ahmad Maruf Principle Product Manager, Tenable Ecosystem[GA] Tenable Patch Management v10.0.971.26 is officially LIVE!
We are pleased to announce the General Availability of Tenable Patch Management (TPM) v10.0.971.26! This quality-focused update delivers critical stability and performance fixes for both On-Premise and SaaS environments. Enhanced Reliability & Precision Reporting This release addresses high-priority issues including strategy corruption, database scaling, and compliance reporting accuracy. Top Fixes to Pitch: Strategy Integrity: Fixes a critical defect where simplified patching strategies could become corrupted or fail to load "How to Patch" configurations. Precision Reporting: Corrects compliance percentage variables to eliminate "over 100%" reporting errors. Improved SaaS Reliability: Resolves "502 Bad Gateway" errors and database deadlocks by optimizing connection pooling and PostgreSQL-specific ports. Patch Filter Conditions: Corrects errors in Patch Filter UI and Tenable.Vpr filter handling. Added a dropdown for true/false boolean fields and updated VPR filters to require the Tenable.VprInteger format. Cloud Compatibility: Fixed the cloud install script (.sh) for successful execution when used in JAMF script payloads. Platform Modernization: Full integration of Java 25 and log4j 2.25.3 for peak security and performance. WSUS Intelligence: Improved WSUS scanning logic to mark patches as "Not Applicable" if a superseding patch is already present. P2P Configuration: New brp2p.minimum_viable_volunteer_count setting to better manage peer-to-peer download sources. Customer-Facing Resources: Release Date: March 5, 2026 Hotfix Version: 10.0.971.26 Changelog: View Release Notes Docs: TPM Complete Documentation Upgrade Path: SaaS/Cloud: Your SaaS Tenants are upgraded to v10.0.971.26 automatically. Please upgrade your clients accordingly. On-Premise: Customers can download the latest version of server and clients from the TPM Downloads portal immediately. Questions? We’re a ping away! Reach us at connect.tenable.com. Happy Upgrading! - Ahmad Maruf Tenable Patch Product Management
Action Required: Preparation for January 2026 Tenable Security Center Feed Update
We are writing to announce an important upcoming change to the Tenable Security Center feed data. Starting in mid-January 2026, the size of Tenable Security Center feeds will increase due to the addition of new Vulnerability Priority Rating (VPR) data; this data will be available in Tenable Security Center 6.8, anticipated for release later in Q1 2026. This update ensures you continue to receive comprehensive vulnerability data, but it requires immediate action to ensure your environment is prepared. What you need to do To prevent the feed size from causing PHP memory exhaustion in your environment, please follow the resolution path for your specific version: Versions 6.5.1 – 6.7.2: Patch 202601.1 is now available. Applying this patch will automatically modify the PHP configuration to increase the memory limit. Versions Prior to 6.5.1: Follow the instructions outlined in this Knowledge Base article to modify the PHP configuration. Note: Tenable Security Center consoles with less than 8 GB RAM may need to have their hardware resources updated. Review Tenable Security Center hardware recommendations Why this matters Taking action now allows you to adopt a proactive approach to this feed expansion, ensuring your nightly updates continue seamlessly. Prevent SC Feed Update Failures: Without this fix, SC Feed updates may fail and log an "Allowed memory size... exhausted" error or terminate abnormally with error status '255'. Protect Disk Space: Failing feed updates can leave behind orphaned files in /opt/sc/data/feed.XXXXX folders, which may build up and cause disk space issues over time. Access our related documentation to learn more: Tenable Security Center Patch 202601.1 (2026-01-06) Knowledge Base: Tenable Security Center Feed Update Failing with "terminated abnormally with error status '255'" Due to PHP Memory Exhaustion