Vulnerability Response Integration with Tenable
Integrate your Tenable deployment developed by ServiceNow with Vulnerability Response
Install Trend
View Install Data
| Date | Install Count | Change |
|---|---|---|
| 2026-09-09 | 0 | - |
| 134 days of no change | ||
| 2026-04-27 | 482 | -482 |
| 149 days of no change | ||
| 2025-11-28 | 481 | +1 |
| 2 days of no change | ||
| 2025-11-25 | 480 | +1 |
| 3 days of no change | ||
| 2025-11-21 | 479 | +1 |
| 3 days of no change | ||
| 2025-11-17 | 478 | +1 |
| 4 days of no change | ||
| 2025-11-12 | 476 | +2 |
| 1 days of no change | ||
| 2025-11-10 | 475 | +1 |
| 3 days of no change | ||
| 2025-11-06 | 474 | +1 |
| 2 days of no change | ||
| 2025-11-03 | 473 | +1 |
| 2025-11-02 | 472 | +1 |
| 3 days of no change | ||
| 2025-10-29 | 470 | +2 |
| 4 days of no change | ||
| 2025-10-24 | 469 | +1 |
| 2025-10-23 | 468 | +1 |
| 1 days of no change | ||
| 2025-10-21 | 467 | +1 |
| 2025-10-20 | 466 | +1 |
| 2025-10-19 | 465 | +1 |
| 3 days of no change | ||
| 2025-10-15 | 464 | +1 |
| 2025-10-14 | 463 | +1 |
| 2025-10-13 | 462 | +1 |
| 2 days of no change | ||
| 2025-10-10 | 461 | +1 |
| 4 days of no change | ||
| 2025-10-05 | 460 | +1 |
| 2 days of no change | ||
| 2025-10-02 | 459 | +1 |
| 1 days of no change | ||
| 2025-09-30 | 458 | +1 |
| 4 days of no change | ||
| 2025-09-25 | 457 | +1 |
| 1 days of no change | ||
| 2025-09-23 | 456 | +1 |
| 2025-09-22 | 455 | +1 |
| 4 days of no change | ||
| 2025-09-17 | 452 | +3 |
| 7 days of no change | ||
| 2025-09-09 | 451 | +1 |
| 2025-09-08 | 450 | +1 |
| 2025-09-07 | 449 | +1 |
| 4 days of no change | ||
| 2025-09-02 | 448 | +1 |
| 2025-09-01 | 447 | +1 |
| 2025-08-31 | 446 | +1 |
| 6 days of no change | ||
| 2025-08-24 | 445 | +1 |
| 3 days of no change | ||
| 2025-08-20 | 444 | +1 |
| 6 days of no change | ||
| 2025-08-13 | 443 | +1 |
| 1 days of no change | ||
| 2025-08-11 | 441 | +2 |
| 13 days of no change | ||
| 2025-07-28 | 440 | +1 |
| 5 days of no change | ||
| 2025-07-22 | 439 | +1 |
| 2025-07-21 | 437 | +2 |
| 3 days of no change | ||
| 2025-07-17 | 436 | +1 |
| 2025-07-16 | 435 | +1 |
| 2025-07-15 | 434 | +1 |
| 3 days of no change | ||
| 2025-07-11 | 433 | +1 |
| 4 days of no change | ||
| 2025-07-06 | 432 | +1 |
| 9 days of no change | ||
| 2025-06-26 | 431 | +1 |
| 1 days of no change | ||
| 2025-06-24 | 430 | +1 |
| 4 days of no change | ||
| 2025-06-19 | 429 | +1 |
| 9 days of no change | ||
| 2025-06-09 | 428 | +1 |
| 4 days of no change | ||
| 2025-06-04 | 427 | +1 |
| 7 days of no change | ||
| 2025-05-27 | 426 | +1 |
| 3 days of no change | ||
| 2025-05-23 | 425 | +1 |
| 2 days of no change | ||
| 2025-05-20 | 424 | +1 |
| 2025-05-19 | 423 | +1 |
| 3 days of no change | ||
| 2025-05-15 | 422 | +1 |
| 16 days of no change | ||
| 2025-04-28 | 420 | +2 |
| 3 days of no change | ||
| 2025-04-24 | 419 | +1 |
| 7 days of no change | ||
| 2025-04-16 | 418 | +1 |
| 9 days of no change | ||
| 2025-04-06 | 417 | +1 |
| 3 days of no change | ||
| 2025-04-02 | 415 | +2 |
| 6 days of no change | ||
| 2025-03-26 | 414 | +1 |
| 2025-03-25 | 413 | +1 |
| 2025-03-24 | 412 | +1 |
| 5 days of no change | ||
| 2025-03-18 | 409 | +3 |
| 1 days of no change | ||
| 2025-03-16 | 408 | +1 |
| 9 days of no change | ||
| 2025-03-06 | 407 | +1 |
| 2025-03-05 | 406 | +1 |
| 1 days of no change | ||
| 2025-03-03 | 405 | +1 |
| 3 days of no change | ||
| 2025-02-27 | 404 | +1 |
| 3 days of no change | ||
| 2025-02-23 | 402 | +2 |
| 2 days of no change | ||
| 2025-02-20 | 401 | +1 |
| 2025-02-19 | 398 | +3 |
| 2025-02-18 | 397 | +1 |
| 6 days of no change | ||
| 2025-02-11 | 396 | +1 |
| 2025-02-10 | 394 | +2 |
| 3 days of no change | ||
| 2025-02-06 | 392 | +2 |
| 7 days of no change | ||
| 2025-01-29 | 391 | +1 |
| 11 days of no change | ||
| 2025-01-17 | 387 | +4 |
| 7 days of no change | ||
| 2025-01-09 | 386 | +1 |
| 6 days of no change | ||
| 2025-01-02 | 385 | +1 |
| 63 days of no change | ||
| 2024-10-30 | 378 | +7 |
About
**Note:**
**This app version is intended for Unified Security Exposure Management (USEM), a significant architectural upgrade to the Vulnerability Response applications.**
**If you are currently using Vulnerability Response and upgrading to USEM for the first time, you must use the Migration assistant for Unified Security Exposure Management to ensure a safe and successful upgrade. For full details, please refer to the [KB2556844](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2556844) and [documentation](https://www.servicenow.com/docs/bundle/zurich-security-management/page/product/security-exposure-management-workspace/concept/unified-security-exposure-management-landing-page.html) before proceeding.**
**If you do not intend to upgrade to USEM, please select a version below 30.x when installing or upgrading.**
The Vulnerability Response Integration with Tenable built by ServiceNow imports data from the Tenable.io, Tenable.sc, and Tenable.cs products. The integrations can help you prioritize and remediate Tenable vulnerabilities and identify and fix misconfigured assets found by the Tenable.io product.
Key Features
- The Vulnerability Response Integration with Tenable application is built by ServiceNow and designed specifically to integrate the Tenable.io and Tenable.sc products seamlessly with Vulnerability Response.
- Using the Tenable.io integration with Configuration Compliance, identify configuration-related vulnerabilities on your assets and verify that your assets are in compliance with your policies and controls.
- Use the Setup Assistant in Vulnerability Response to configure the integration credentials and application parameters.
- Compare imported data from the Tenable platform with the existing assets (configuration items) listed in the CMDB in your Now Platform instance.
- Create vulnerable items (VIs) when third-party vulnerabilities are matched with existing configuration items.
- Schedule jobs to run automatically for all the Tenable.io and Tenable.sc integrations. You can also execute any scheduled jobs on-demand.
- Set import filters on the Tenable.io and Tenable.sc vulnerabilities so that you import only the vulnerabilities you want.
- Verify VIs for specific vulnerabilities and configuration items that have been remediated by initiating rescans in Tenable.sc and Tenable.io on-demand directly from VI, remediation task, discovered item, and third-party vulnerability records in your instance.
**Key Capabilities **
- Automatically import vulnerabilities discovered by Tenable.cs in cloud hosts and container images into ServiceNow.
- Enable remediation workflows to triage, assign, and resolve the most critical vulnerabilities across cloud-native and containerized environments.
- Use the Setup Assistant to easily configure credentials and integration parameters—get started with minimal manual setup.
- Scheduled jobs periodically run to:
- Import findings from Tenable.cs
- Create Vulnerable Items (for cloud hosts)
- Create Container Vulnerable Items
Version History (15)
+ 5 more versions