State roll-up and roll-down scenarios

---
title: State roll-up and roll-down scenarios
description: State roll-up and roll-down scenarios automatically sync the status of remediation tasks \(RTs\) and vulnerable items \(VITs\), ensuring real-time updates across both. This dynamic interaction reduces manual tracking, enhances accuracy, and provides users with an up-to-date view of progress, making vulnerability management more efficient and helping users make informed decisions quickly.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/security-management/vulnerability-response/vr-state-rollup-rolldown.html
release: brazil
product: Vulnerability Response
classification: vulnerability-response
topic_type: reference
last_updated: "2026-09-10"
reading_time_minutes: 2
breadcrumb: [Vulnerability Response remediation task states, Vulnerability Response reference information, Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# State roll-up and roll-down scenarios

State roll-up and roll-down scenarios automatically sync the status of remediation tasks \(RTs\) and vulnerable items \(VITs\), ensuring real-time updates across both. This dynamic interaction reduces manual tracking, enhances accuracy, and provides users with an up-to-date view of progress, making vulnerability management more efficient and helping users make informed decisions quickly.

## Roll-up behavior

When vulnerable item \(VIT\)states change, these changes may propagate up to the remediation task \(RT\)level. The following table summarizes key roll-up scenarios where changes in vulnerable item \(VIT\) state may influence the associated remediation task \(RT\) state, based on closure conditions, reassignments, and deferrals.

<table id="table_qdx_ryw_2hc"><thead><tr><th>

VITs State

</th><th>

Condition

</th><th>

RT State

</th></tr></thead><tbody><tr><td>

Open → Under Investigation / Awaiting Implementation \(any sub-state\) / In Review

</td><td>

VIT transitions to any non-final or non-actionable state

</td><td>

Remains Open

</td></tr><tr><td>

Open → Closed

</td><td>

All associated VITs have the same sub-state

</td><td>

Closed – &lt;same sub-state as VITs&gt;

</td></tr><tr><td>

Open → Closed

</td><td>

All associated VITs have different sub-states

</td><td>

Closed – &lt;no sub-state&gt;

</td></tr><tr><td>

Open → some Closed VITs and some Deferred VITs

</td><td>

All associated Deferred VITs have the same sub-state

</td><td>

Deferred – &lt;same sub-state as VITs&gt;\(Until date = earliest of all VITs\)

</td></tr><tr><td>

Open → some Closed VITs and some Deferred VITs

</td><td>

All associated Deferred VITs have different sub-states

</td><td>

Deferred – &lt;no sub-state&gt;\(Until date = earliest of all VITs\)

</td></tr><tr><td>

Open → Closed–Fixed \(after next scan\) → Resolved

</td><td>

VITs marked as fixed but pending verification

</td><td>

Remains Open

</td></tr><tr><td>

Closed–Fixed → Open

</td><td>

VIT reopens after being Closed–Fixed

</td><td>

Remains Closed–Fixed

</td></tr><tr><td>

Closed–Stale → Open

</td><td>

VIT reopens after being Closed–Stale

</td><td>

Remains Closed–Cancelled

</td></tr><tr><td>

Under Investigation → Closed–CI Decommissioned

</td><td>

Multiple RTs \(e.g., RT1, RT2\) exist for related VITs

</td><td>

Each RT transitions to Closed–Cancelled

</td></tr><tr><td>

Resolved → Open

</td><td>

If a resolved VIT reopens and the previously associated RT was assigned to a user

</td><td>

Resolved → Under Investigation

</td></tr><tr><td>

Resolved → Open

</td><td>

If a resolved VIT reopens and the previously associated RT was unassigned to a user

</td><td>

Resolved → Open

</td></tr></tbody>
</table>## Roll-down behavior

When the state of a remediation task changes, the state is often propagated to the associated VITs unless overridden by manual updates or specific exceptions. The following table summarizes key roll-down scenarios where changes in remediation task \(RT\) state may affect the associated vulnerable item \(VIT\) state, based on precedence rules and special conditions.

|RT State|Condition|VIT State|
|--------|---------|---------|
|Open → Under Investigation / In Review / Closed–False Positive|RT transitions to a non-final or non-actionable state|Mirrors RT state change \(Open → &lt;same state as RT&gt;\)|
|Open → Deferred \(Sub-state: Reason Given\)|RT deferred with a specified reason|Open → Deferred \(Sub-state: Reason Given\)|
|Open → Resolved|RT marked as resolved|Open → Resolved|
|Open → Closed–Cancelled / Closed–Fixed with Exceptions|RT closed without full resolution|Remains Open|
|RT1: Open → Under Investigation; RT2: Open|One RT moves to Under Investigation while another remains Open|Open → Under Investigation|
|RT1: Open → Under Investigation → Awaiting Implementation; RT2: Under Investigation|One RT progresses to Awaiting Implementation|Open → Under Investigation → Awaiting Implementation|
|RT1: Awaiting Implementation → Deferred; RT2: Awaiting Implementation|One RT deferred while another remains Awaiting Implementation|Awaiting Implementation → Deferred|
|RT1: Awaiting Implementation → Closed–Cancelled; RT2: Under Investigation|One RT cancelled while another is Under Investigation|Awaiting Implementation → Under Investigation|
|Open → Closed–Fixed with Exceptions|Mixed outcome: one VIT closed as fixed with exceptions, another remains open|VIT1: Open → Closed–Fixed; VIT2: Remains Open|
|Open → Resolved|Mixed outcome—one VIT closed as fixed and another resolved|VIT1: Open → Closed–Fixed; VIT2: Open → Resolved|
|Resolved → Open|RT reopens after resolution|VIT2 reopens; VIT1 remains Resolved|