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

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Report an Operational vulnerability from the Service record

# Report an operational vulnerability from the Service record {#ariaid-title1}

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

Report an operational vulnerability from the Service record available in the Self-attestations list.

## Before you begin

Role required: sn_oper_res.manager

## Procedure

1. Navigate to WorkspacesOperational Resilience WorkspaceSelf-attestations.  
   A list of the available Self-attestations is displayed.
2. Select and open a Service record from the list.
3. Select More and add the Operational vulnerabilities related list.
4. Select New in the Operational vulnerabilities related list and add an operational vulnerability.
5. On the Vulnerability New record form, fill in the fields.  
   The source of the vulnerability is the selected service. Therefore, the Source field on the form shows the source as Service and the Source table field on the form shows
   the table as Service. The Source table field is auto-filled.

   To view more information on the fields, see the [Create New Operational vulnerability form](https://www.servicenow.com/docs/mA~68_5qJLg1O4XhAueQmw "On the Create New Operational vulnerability form, fill in the fields.").
6. Select Save.  
   The following example shows how the Service record is displayed in the Operational vulnerabilities related list and the related area for the Operational vulnerability is Blackberry service.
7. Select Save.  
   The Service record is saved.
{#report-op-vul-from-service__steps_mqj_mls_tcc}

*[\>]: and then