top of page

ServiceNow VR to USEM Upgrade: What Enterprises Need to Know

Nov 10
13 min read

ServiceNow’s Vulnerability Response (VR) module is becoming Unified Security Exposure Management (USEM), and from the Brazil release onwards the upgrade is being mandated. In this article we look at what changes with USEM, the timelines enterprises are working to, the implications of upgrading, and why the organisations that treat it as opportunity stand to gain the most.


Matt Austin | Client Portfolio Lead | Automiq

Author:

Matt Austin

Client Portfolio Lead



ServiceNow VR to USEM Migration | Automiq

For close to a decade, ServiceNow Vulnerability Response (VR) has been helping to bridge the gap between security and IT operations teams in large enterprises – the module where scanner findings are imported from Nessus, Qualys, Wiz, Rapid7, CrowdStrike and others, matched to configuration items in ServiceNow's CMDB, routed to the right remediation team, and tracked against SLAs. The module provided structure to what was largely a manual handoff between security (who discovered the vulnerability) and IT (who ensured it was patched) - as well as enabling end-to-end visibility and reporting.


In December 2025, ServiceNow released Unified Security Exposure Management (USEM), positioned as the next evolution of Vulnerability Response and delivered as VR version 30.x. [2] On current guidance, USEM becomes the minimum supported version of VR when customers upgrade to the Brazil platform release – and instances that have not migrated by then will be moved onto it automatically. [2][3]


The migration itself is relatively short and straightforward, and for most enterprises will land as a technical task to be scheduled, executed and closed once proven operational. This approach might be the shortest route to maintaining the status quo, but won't take advantage of the new capabilities included with the upgrade.


This article covers how VR evolved, what USEM changes, what the timelines mean in practice, where the difficulty concentrates, and how to approach it.


Contents



Key facts at a glance


  • USEM is the replacement path for VR, not a separate product. It is delivered in Vulnerability Response v30.x, released to the ServiceNow Store on 11 December 2025, and existing VR customers can move to it without a licence change. [2][3]

  • Brazil is the deadline that matters. Upgrading an instance to the Brazil family release automatically trues VR up to v30.x. Brazil reached Early Availability on 24 September 2026, with General Availability expected in November 2026. [3][6]

  • The technical migration is measured in hours; readiness is measured in weeks. ServiceNow cites around four hours for the automated steps in a large environment of roughly 50 million vulnerable items and 600 rules – followed by a customer-specific review of every customisation. [3]

  • An accidental upgrade is possible today. ServiceNow has flagged that Australia Patch 3m and 4m unintentionally trigger an automatic VR-to-USEM upgrade for VR versions below 30, with no ability to roll back. [2][3]

  • The requirement for the capability is stronger than ever. Vulnerability exploitation is now the most common initial access vector for breaches – 31% in Verizon’s 2026 Data Breach Investigations Report, ahead of both phishing and credential abuse. [7]


From VR to USEM: how we got here

ServiceNow entered the security market in February 2016 with Security Operations, launched as two cloud applications: Security Incident Response and Vulnerability Response. [1] The proposition was simple and, at the time, distinctive – apply the workflow, automation and service management capability ServiceNow had built for IT to the response side of security, integrating with the scanners, SIEMs and the US National Vulnerability Database that customers already relied on, rather than competing with them. [1]


ESG research released alongside the launch identified coordination between security and IT teams as the number one incident response challenge, with nine in ten respondents saying manual processes limited their effectiveness. [1] That gap – security finds the problem, IT owns the fix – is the same one we described in An Introduction to VulnOps, and a decade on it remains both a priority and a challenge for many enterprises.


Over the years that followed, VR grew outwards. Certified integrations with the major scanning vendors brought findings in at scale. Configuration Compliance added misconfiguration findings. Application Vulnerability Response and Container Vulnerability Response extended coverage into code and containerised workloads. A dedicated IT Remediation Workspace gave remediation owners their own experience, and Now Assist (recently renamed to Otto for USEM) brought generative AI into vulnerability workflows. [13][4][3]


Each addition was valuable in its own right. The cumulative effect, however, was a suite that had grown by accretion: several exposure types, each with its own records, rules and reporting; configuration spread across modules; and different experiences for different personas. At the same time, the volume of data flowing through it rose dramatically – Verizon recorded around 68.7 million vulnerability instances in 2022 and around 527.3 million in 2025, close to an eight-fold increase. [7]


Meanwhile, the market had moved from vulnerability management towards exposure management. Gartner named Continuous Threat Exposure Management (CTEM) one of its top strategic technology trends for 2024, describing a continual evaluation of how accessible, exposed and exploitable an enterprise’s digital and physical assets are – with assessment scopes aligned to threat vectors or business projects, rather than to individual infrastructure components. [8] The question shifts from “how many vulnerabilities have we patched?” to “which exposures matter most to the business – and are we reducing them?”


What's new in USEM?

Unified Security Exposure Management is ServiceNow’s consolidation of its vulnerability and misconfiguration capabilities into a single exposure management experience. It brings host vulnerabilities, application vulnerabilities, container vulnerabilities, misconfigurations and cloud exposures together in the Security Exposure Management (SEM) Workspace, mapped to assets in the CMDB. [3][5] Despite the new name, it is not a new product to procure: USEM features ship in Vulnerability Response v30.x, and customers entitled to VR can upgrade without a licence change. [2][3]


The changes that matter most to enterprises fall into five areas:

Area

What changes

Why it matters

One workspace for every exposure type

The SEM Workspace unifies host (VIT), application (AVIT), container (CVIT) and configuration compliance (CTR) findings, with reporting across all of them. [3][4]

A single view of exposure per asset or business service, rather than separate queues and separate scores.

A new configuration framework

Assignment, CI lookup and auto-close rules now live in the SEM Workspace; classification rules drive risk scoring, SLA management and prioritisation. [3]

Configuration becomes consistent across exposure types – and every existing rule has to be migrated and validated.

A better remediation owner experience

Remediation tasks gain a structured flow that captures a commitment date and remediation plan as work moves to implementation. [4]

Accountability is recorded at the point of commitment, rather than reconstructed after an SLA breach.

AI-assisted correlation (Otto)

Otto for USEM (previously Now Assist) can correlate and deduplicate findings across different scanners, and remediation task grouping rules consolidate related work. [3]

Fewer duplicate tickets for the same underlying issue – although the AI features require additional entitlements.

A connected risk picture

USEM integrates with IRM Continuous Monitoring, carries forward GRC policy exception configuration, and supports Security Posture Control’s “toxic combination” insights. [3]

Exposure data can feed risk assessments and audit evidence, rather than sitting in a security silo.

It's worth noting that ServiceNow is not restructuring the underlying data: the existing VR table architecture remains, with a new configuration and reporting framework layered on top. [3] That makes the migration considerably less disruptive than the name change implies.


Additionally, the Classic UI remains available, but all new features and enhancements will be built for the SEM Workspace only. [3] In practice, staying on the old experience means opting out of the roadmap.


Key dates to be aware of

USEM (VR v30.x) becomes the minimum supported version of Vulnerability Response from the Brazil platform family release. If an instance running an earlier version of VR is upgraded to Brazil, VR is automatically forced up to v30.x, and the migration then has to be completed retrospectively using the USEM Migration Assistant. [2] ServiceNow itself describes that route as “not an ideal path”, because it rarely leaves enough time for testing, validation, communication and enablement. [2]


Brazil being the trigger does not mean every enterprise can wait until it chooses to upgrade. ServiceNow operates an N-1 support model, under which customers are supported on the current family release and the one before it. [11] With two family releases a year, that means once Canada reaches General Availability – planned for Q2 2027 – instances still on Australia will need to move to Brazil or later, and the USEM true-up will follow automatically. [11][12]


For most customers, the window to migrate to USEM on their own terms runs from now until their Brazil upgrade – and for very few will that be later than H2 2027. Allowing for platform upgrade lead times, regression testing and change freezes, the planning should be happening in Q4 2026 and Q1 2027.


The other risk is the inadvertent upgrade: applying Australia Patch 3m and 4m will trigger the USEM upgrade automatically - something organisations must factor in if looking to apply these patches.


ServiceNow's own advice on sequencing


  • Migrate before Brazil, not alongside it. ServiceNow recommends keeping the USEM migration separate from a family release upgrade, as combining them may not leave enough time for regression testing, customisation review, documentation and training. USEM is compatible with current platform releases, so it can be done first. [3]

  • Use the Migration Assistant, not the Application Manager. Existing VR customers should upgrade through the dedicated USEM Migration Assistant, which handles both the Store app upgrades and the data migration. [2]

  • Run it in every environment. The Migration Assistant needs to be run in each instance – sandbox, development, test and production – even where configuration is promoted between them. [3]

  • Start in a sandbox and benchmark. ServiceNow suggests a sandbox first, not least because development instances are usually busy with other changes heading for production. [3]


How to plan the upgrade to USEM

On paper, this is a straightforward exercise. ServiceNow’s own example is a large customer with around 50 million vulnerable items and 600 rules, for whom the initial automated steps took around four hours; for a small environment with no customisations, the minimum is around two. [3]


In our experience, no two enterprises are the same in terms of their configuration and customisation of SecOps VR - and therefore the catch lies in understanding those differences, and whether they are likely to impact the upgrade:


  1. Customisations & Technical Debt: The Migration Assistant migrates existing rules as-is, and surfaces every customisation as a conflict or skipped file to be reviewed and resolved. [3] For an implementation that has been running for five years or more, that list can be long – and every item demands a decision: replicate it, replace it with out-of-the-box functionality, or retire it.

  2. Integrations: ServiceNow has released USEM-compatible v30.x versions of its own scanner integrations – Qualys, Rapid7, Tenable and others – and the Migration Assistant will prompt for their upgrade. Custom integrations built on the integration framework should continue to work unchanged - but both standard and custom integrations require planning, testing, and validating as part of the upgrade.

  3. Reports and Dashboards: Reports and dashboards built on the standard tables should largely continue to work, but a small number of columns have changed and each needs validating. [3] If the board-level vulnerability dashboard breaks or silently changes meaning, confidence in the programme can be eroded.

  4. People & Ways of Working: Analysts move to a new workspace. Remediation owners – often hundreds of people across infrastructure, application and third-party teams who do not think of themselves as security staff – are encouraged to transition from the IT Remediation Workspace to the USEM experience. Changing how that population receives, commits to and closes remediation work is an organisational change management (OCM) exercise, not a straightforward email communication.


Why the upgrade is an opportunity

Every enterprise running VR will (eventually) migrate to USEM. The difference between those that follow the technical steps and those that emerge materially more resilient lies in how the work is approached:


Move from vulnerability lists to exposure management

USEM gives organisations the platform construct to manage exposure the way CTEM describes it: scoped to the business services that matter, prioritised by exploitability and business impact, and spanning every exposure type. Gartner predicted that by 2026, organisations prioritising security investment based on a CTEM programme would realise a two-thirds reduction in breaches. [8]


The migration is a natural point to agree what “exposure” means for your organisation – and how its reduction will be reported to the board.


Reduce or remove technical debt

ServiceNow itself positions the migration as “a good opportunity to re-evaluate and simplify rules”. [3] Reviewing and reducing or removing prior customisations - rather than carrying hundreds of them forward unexamined – reduces the effort requirements of every future upgrade, and ensures new capabilities will be accessible out of the box.


Add service context to vulnerability prioritisation

If your CMDB is not yet service mapped, leverage the USEM upgrade as (another!) reason to revisit the value that service context would bring. For USEM specificially, it's the ability to understand which vulnerabilities impact your Important Business Services (IBS), and to prioritise them accordingly.


The benefits of service mapping are not limited to security: the capability simplifies regulatory compliance, enhances operational processes, and reduces business disruption - as we outlined in a prior article: What is Service Mapping, and why does it matter to enterprises?


Align reporting and ways of working with regulations

Remediation SLAs combined with exception management produce the evidence regulators increasingly expect. As we set out in The UK Cyber Security & Resilience Bill: What it Means for Vulnerability Operations (VulnOps), the NCSC’s Cyber Assessment Framework assesses demonstrated outcomes, not the existence of a policy.


Build a foundation for Vulnerability Operations (VulnOps) and AI-speed response

Frontier AI has compressed the window between disclosure and exploitation, as we covered in Patching Vulnerabilities in the Age of Frontier AI. USEM provides a stronger intake, prioritisation and assignment layer – but the loop still needs to close with controlled execution and independent verification. A migration designed with the VulnOps loop in mind will deliver far more than one designed simply to reach v30.x.


What enterprises should do now – and how Automiq can help

We work at the intersection of cyber, risk, IT operations and automation – the seam where vulnerability response has always been hardest to get right. A VR to USEM migration sits squarely in that space, and leveraged in the right manner, can deliver significant improvements in security, resilience and operational efficiency:



The bottom line

The move from Vulnerability Response to USEM is not a question of if, but when – and for most enterprises, Brazil sets the outer limit on how much choice they have over the when.


The automated migration takes hours. The decisions around it – what to carry forward, what to retire, who owns what, and how exposure is measured and reported – are where the value is won or lost.


Organisations that wait for the platform upgrade to force the issue will complete a version change under time pressure, with customisations migrated as-is and remediation owners learning a new workspace on the fly.


Those that plan now can use a mandatory upgrade to build a vulnerability management capability fit for how exposure works today. The deadline might be fixed, but the outcome isn’t.


Frequently asked questions


What is ServiceNow USEM?

Unified Security Exposure Management (USEM) is the next evolution of ServiceNow Vulnerability Response. It brings host, application and container vulnerabilities, misconfigurations and cloud exposures into a single Security Exposure Management (SEM) Workspace, with a common configuration and reporting framework. It is delivered in Vulnerability Response v30.x, which was released on 11 December 2025. [2][3]


What is the difference between vulnerability management and exposure management?

Vulnerability management focuses on finding, scoring and remediating software vulnerabilities. Exposure management takes a wider view, covering any condition an attacker could exploit – including misconfigurations, cloud and container exposures, and weaknesses that cannot be patched – and prioritises them by business impact and exploitability. Gartner’s Continuous Threat Exposure Management (CTEM) approach, which evaluates the accessibility, exposure and exploitability of an enterprise’s digital and physical assets, is a widely referenced model. [8]


Is the move from Vulnerability Response to USEM mandatory?

Yes. ServiceNow’s current guidance is that USEM (VR v30.x) becomes the minimum supported version of Vulnerability Response from the Brazil platform release. Brazil reached Early Availability on 24 September 2026, with General Availability expected in November 2026. Under ServiceNow’s N-1 support model, most customers should expect to be on Brazil or later during 2027. [2][6][11]


What happens if we upgrade to Brazil without migrating to USEM first?

Vulnerability Response is automatically trued up to v30.x, which installs USEM as a dependency. The migration steps then have to be completed after the platform upgrade using the USEM Migration Assistant – a route ServiceNow does not recommend, because it leaves little time for testing, validation and user enablement. [2][3]


Does USEM require a new licence / SKU, or cost more?

Customers currently licensed for Vulnerability Response can upgrade to USEM without a licence change, and are also entitled to the Central Vulnerability Database store application it relies on. The existing licence tier determines which exposure types and features are available, and AI capabilities such as cross-scanner deduplication require Otto for USEM entitlements. [2][3]


How long does a VR to USEM migration take?

The automated steps are quick: ServiceNow cites around four hours for a large environment with roughly 50 million vulnerable items and 600 rules, and around two hours for a small, uncustomised one. The overall programme takes considerably longer, because customisations, integrations, reports and remediation workflows must be reviewed, tested and communicated across every environment. [3]


Will our scanner integrations, such as Qualys, Tenable and Rapid7, still work after migrating?

ServiceNow has released USEM-compatible v30.x versions of its own integrations, and the Migration Assistant prompts for those upgrades during migration. Custom integrations built on the integration framework should continue to work without changes; ServiceNow documents the data model and column changes for teams that want to review them. [3]


What happens to the IT Remediation Workspace and the Classic UI?

The Classic UI remains available, but all new features will be developed for the SEM Workspace only. ServiceNow recommends that remediation owners begin transitioning from the IT Remediation Workspace to the USEM experience, although no retirement date has yet been set. [3]


Should we combine the USEM migration with our Brazil platform upgrade?

Generally, no. ServiceNow recommends keeping the two separate where possible, as combining them may not leave enough time for regression testing, customisation review, documentation and training. Because USEM is compatible with current platform releases, the cleaner approach is to migrate to USEM first and upgrade the platform afterwards. [3]


Sources & further reading


Automiq logo light
bottom of page