---
sourceDocument: Zurich Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/governance-risk-compliance

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Add the impacted area

# Add the impacted area {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Add an impacted area or an object to the operational vulnerability record in the Operational Resilience Workspace.

## Before you begin

Role required: sn_oper_res.manager

## About this task

When an impacted area is added for the vulnerability, its state is updated to New (In progress) as shown on the Overview tab of the vulnerability record.

Beginning with Release 20.1.x, the Operational Resilience application supports the latest Common Service Data Model (CSDM). The enhanced functionality supports the roll up of the dependencies.

## Procedure

1. Navigate to WorkspacesOperational Resilience WorkspaceAll Operational Vulnerabilities.
2. Open the vulnerability for which you want to add an impacted area.
3. Select New.
4. On the Impacted area form, fill in the fields.  
   To view more information on the fields, see the [Impacted area form](https://www.servicenow.com/docs/6u6yeUBFOITwEXzPxdQmXg "On the Impacted area form, fill in the fields.").
5. Select Save.  
   Note:  
   The operational administrator can view the progress of adding impacted assets to the operational vulnerabilities and they can also change the order of the dependencies.

   When you
   add the primary origin of the operational vulnerability, its impacted areas with upstream entities are updated on the Impacted areas tab.

   When the scheduled job is executed, the updated impacted areas and the overall operational vulnerability count are reflected in the dashboard.

   For example, when the impacted areas in the operational vulnerability are updated, the operational vulnerability count on the overview page of SO1 remains at 0 before the scheduled job runs.

   After running the scheduled job, the operational vulnerability count on the overview page of SO1 is updated to 1. This ensures that the updated data is promptly reflected on the Operational Resilience dashboard.
{#add-impacted-area-to-vul__steps_yhm_hky_scc}

*[\>]: and then