Ivanti Neurons & Endpoint Manager Mobile Integration
Summary Tenable is pleased to announce its new integration with Ivanti Neurons and Ivanti Endpoint Manager Mobile. Tenable customers can now integrate with Ivanti for enhanced mobile device management (MDM). The Ivanti integration is a rebranded version of MobileIron and operates in a highly analogous manner. Ivanti provides a comprehensive strategy for safeguarding mobile devices and addressing evolving IT requirements. Scope Customers using Tenable Vulnerability Management and Nessus Manager will be able to configure an MDM scan using the Ivanti credential which can be found in the “Mobile Device” category of credentials. Detailed information about the integration and configurations can be found by visiting our integration documentation page in the link for Ivanti. https://docs.tenable.com/Integrations.htm. Plugins The following integration plugins gather the credential settings, collect data from the Ivanti API, and if the integration was successful in collecting the correct credentials. Integration Plugins Ivanti Settings Ivanti Data Collection Integration Status Impact Customers will now see Ivianti and MobileIron credentials for MDM scans. There is no impact to our existing MobileIron MDM Integration. Release Date Tenable Vulnerability Management and Nessus Manager: October 23rd, 2025 Tenable Security Center: TBDFudo Security API v2 Compatibility
Summary Tenable is proud to announce compatibility with Fudo API v2. Customers now have the option to use both the API v2 and API v1 of the Fudo Security Privileged Access Management (PAM) solution. The API v2 uses API key authentication and not username and password, so customers using the integration credential now have a field for API URL and API Key. Further information regarding these changes and other helpful configuration tips for scans can be found by following the provided link to the FUDO section of Tenable's documentation page. Impact Existing scan configurations remain unaffected. Customers utilizing the integration will observe that the integration collects identical information, irrespective of the API version employed. Target Release Date 09/16/2025 for TVM and Nessus, TBD for SCNutanix Prism v4 API Compatibility
Summary Tenable is proud to announce compatibility with the version 4 of the Nutanix Prism Central REST API. This provides compatibility with current and future versions of Nutanix Prism. Change Tenable is adding support for API v4 but preserving support for API v3. Customers for whom API v4 is not available will continue to use v3. For all other customers, Tenable’s Nutanix Prism integration will automatically use API v4. Impact Customers should not see scan results change. The integration collects the same information regardless of the API version in use. Customers with Nutanix Prism Central are encouraged to update plugins to utilize the latest version of the integration. Target Release Date 26 Aug 2025 for T.VM, Nessus, and T.SC.Nutanix Prism Central PAM Support
Summary Tenable is pleased to announce the addition of another authentication method for the Nutanix Prism Central credential. We now offer Privilege Access Manager (PAM) Integration support within the Nutanix Prism Central credential. This feature allows customers to authenticate to Nutanix Prism Central using either username and password credentials or one of our PAM integrations. Scope When configuring credentials for Nutanix Prism Central under Miscellaneous credentials, customers will now find a new dropdown option ‘Nutanix Prism Central Authentication Method’. This allows them to authenticate using a username and password or by selecting a PAM and subsequently inputting the necessary credential fields for the chosen PAM. Supported PAM Integrations in this Release: Arcon BeyondTrust Password Safe CyberArk Delinea Secret Server Fudo HashiCorp Vault QiAnXin SenhaSegura WALLIX Bastion Plugin Impact For any issues related to the use of PAM authentication with Nutanix Prism Central, please refer to the new log located within the Debugging Log Report. Example If using Nutanix Prism Central with Fudo support, the file will display as “nutanix_settings.nasl~Fudo”. Release Date Tenable Vulnerability Management and Nessus Manager: July 21st, 2025 Tenable Security Center: TDBCisco Meraki Integration
Summary Tenable is proud to announce our new integration with Cisco Meraki Dashboard. Cisco Meraki Dashboard is a centralized cloud-based platform used to manage and monitor Cisco Meraki devices. It provides a web-based interface for configuring, troubleshooting, and securing global network and IoT deployments. Tenable’s integration with the Cisco Meraki Dashboard API allows users to leverage our vulnerability management solutions against devices that are managed in their Meraki environment including security appliances, switches, routers, and other supported devices. Scope Customers using Tenable Vulnerability Management and Nessus Manager will be able to configure up to a maximum of five Cisco Meraki credentials in a single scan policy. The Cisco Meraki credential can be found under the "Miscellaneous" category of credentials. Detailed information about the integration and configurations can be found by visiting our integration documentation page in the link for Cisco Meraki. https://docs.tenable.com/Integrations.htm Plugins Plugins related to the integration can be divided into two categories; integration and supporting plugins. The integration plugins gather the credential settings, collect data from the Cisco Meraki API, and store this data for usage by the supporting plugins. Whereas supporting plugins detect the presence of Cisco Meraki devices and perform vulnerability detections against the device attributes; mainly primarily firmware. Integration Plugins Cisco Meraki Settings Cisco Meraki Data Collection Integration Status Supporting Plugins Cisco Meraki Detection Tenable Research will also release 6 initial plugins to detect Cisco Meraki versions vulnerable to several different high-impact CVEs. Please note that these plugins will require a paranoia level of 2 (“Show potential false alarms”). Impact The Nessus Scan Information plugin (plugin ID 19506) will report credentialed checks for Cisco Meraki devices through the use of the Cisco Meraki integration. Customers will see credentialed checks ‘no’ if a Cisco Meraki Device was detected while using the integration and the firmware version that we collected for the device is not configured or absent. Otherwise, customers can expect to see ‘yes, via HTTPS’ if successful. Release Date Tenable Vulnerability Management and Nessus Manager: July 3rd, 2025 Tenable Security Center: TDBIntegration Status Plugin Summary Tenable is announcing the...
Integration Status Plugin Summary Tenable is announcing the release of a new plugin named Integration Status. The purpose of this plugin is to provide users with helpful information regarding the success or failure when using one of Tenable’s currently supported PAM, MDM, and/or Patch Management Integrations. This gives users a simple way to check on the status of the integration success without having to enable plugin debugging on a per-host basis. Additionally, it improves scan review and performance. In the event that integration status failed, the user can enable plugin debugging, re-scan, and review logs associated with a particular integration for more detail. Tenable will release this plugin feature in two separate releases. This is based on user demand. Integrations in the initial release include the following. PAMs Arcon BeyondTrust Password Safe CyberArk (this includes Legacy, non-Legacy, and Dynamic Scanning). Delinea Secret Server HashiCorp Vault QiAnXin SenhaSegura WALLIX Bastion MDMs AirWatch Blackberry UEM IBM MaaS360 Microsoft InTune Workspace ONE Patch Management VMware ESX SOAP API VMware vCenter API Integrations that will be released after the initial release include the following. Nutanix RedHat Satellite Server HCL BigFix Microsoft SCCM Microsoft WSUS Scope This plugin reports the success or failure of an integration, based on the intent of the integration. This varies between PAMs, MDM, and Patch Management integrations. Here is a synopsis of each integration type. Tenable’s PAM integrations retrieve account credentials for one or more targets specified in a scan policy and credential. Tenable determines the success or failure of retrieving the credential from a specific PAM within the scope of the Integration Status plugin. NOTE: This plugin does not include authentication success or failure to the target within scope. There are other plugins in existence for this purpose. Tenable’s MDM integrations retrieve mobile devices and data associated with those devices. Tenable determines success or failure of an MDM integration based on whether devices were retrieved or not. Tenable Patch Management integrations retrieve patch data from a specific host. In Tenable’s initial release, we’ve included our VMware integrations (ESXi and vCenter). Here are some details regarding the scope of our VMware Integrations as it relates to the new plugin. Users that configure one or more VMware vCenter API credentials can expect to see integration success or failure on a per host basis. If the target is a vCenter host, Tenable determines whether or not authentication to the API was successful. By adding a vCenter host to the target list, users can get a better perspective on the status of the integration's success or failure. If the target is an ESX host, Tenable determines success or failure based on our ability to retrieve VIBs for this host based on data we retrieve from the vCenter host that manages it. In addition, we report the associated vCenter host that manages it. Users that configure one or more VMware ESX SOAP API credentials can expect to see success or failure based on Tenable’s ability to gather VIBs directly from the specific ESXi host in the target settings. Impact There is no impact to existing scans. If users encounter issues, please open a ticket with Technical Support. Initial Release Date July 31, 2024 - Tenable Vulnerability Management, Tenable Nessus, and Tenable Security Center Remaining Integrations Release Date 2024 Q3 - Tenable Vulnerability Management, Tenable Nessus, and Tenable Security CenterDelinea Centrify and Thycotic End-of-Support Summary...
Delinea Centrify and Thycotic End-of-Support Summary Effective immediately Tenable has discontinued support for the Delinea Centrify and Delinea Thycotic PAM integrations. These products are End-of-Support. Please note, Tenable still maintains and supports an integration for Delinea Secret Server. Change Discontinued support of the Tenable integrations for Delinea Centrify and Delinea Thycotic PAMs. Impact Customers may continue to use these integrations. However, there will be no support or future updates made to these integrations. Release Date June 3, 2024 - TVM, Nessus, and Security Center
QiAnXin PAM Integration Release Summary We are proud to...
QiAnXin PAM Integration Release Summary We are proud to announce the QiAnXin Privileged Access Management (PAM) integration. The integration can gather credentials from the QiAnXin PAM solution to be used for target authentication. This will be available in Tenable Vulnerability Management and Nessus Manager, with plans to release this feature in Tenable.sc in the near future. The QiAnXin PAM integration supports SSH (with privilege escalation), SMB (Windows), and database target authentication. With this addition, customers will benefit from streamlined privileged access to use in credentialed vulnerability scans, providing a more comprehensive understanding of their cyber exposure. Supported Authentication Types SSH integration includes least privilege, privilege escalation, and SSH key authentication. SMB (Windows) integration includes domain configuration. Database integration includes the following database types: Oracle SQL Server MySQL MongoDB PostgreSQL DB2 Target Release Date 11/20/2023Delinea Integration API Key Support Summary Tenable has...
Delinea Integration API Key Support Summary Tenable has added the ability to authenticate to Delinea Secret Server PAM integration using an API key. Change A new dropdown, “Delinea Authentication Method” has been added for which there are two choices, “Credentials” and “API Key”. Credentials, the default, was previously the only option for Delinea authentication. When the “Credentials” option is selected, you supply a username and password. When “API Key” is selected, you enter an API token instead. An API token can be generated in the Delinea Secret Server web interface, under “User Preferences”. Prior to this change, there is no choice but to use login name and password: With the change, the default behavior remains to enter credentials: When “API Key” is selected, you may enter the API key instead: The Documentation has been updated to refer to the new options for Tenable Vulnerability Management and Nessus (Windows, SSH), and will be for Tenable Security Center (Windows, SSH). Impact It is optional to use an API key to authenticate, and the default authentication method will remain credentials. Existing configurations should not be affected. Release Date Immediate for Nessus and VM TBD for SCWorkspace ONE MDM Integration Summary We are proud to...
Workspace ONE MDM Integration Summary We are proud to announce that Tenable customers can now benefit from the Workspace ONE Mobile Device Management (MDM) Integration, allowing them to seamlessly collect mobile device information into Tenable's platform. With this integration, Tenable can perform vulnerability scans on these devices during an MDM scan in Tenable.io and Nessus Manager. We plan to extend this feature to Tenable.sc in the near future. Workspace ONE replaces the AirWatch MDM integration and offers enhanced performance capabilities by providing users with the flexibility to choose which parts of the data collection process they wish to enable. Target Release Date Already in Production for Nessus and Tenable Vulnerability Management Coming soon for Tenable Security Center
