---
sourceDocument: Yokohama Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/governance-risk-compliance

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Fields on the Authorization Boundary form

# Fields on the Authorization Boundary form {#ariaid-title1}

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

An authorization boundary defines the scope of a particular system that can be continuously managed and monitored using the CAM application.
{#cam-form-authorization-boundary__table_epy_qrq_f5__entry__2}

| Field | Description |
|-|-|
| Name | A unique and descriptive name for this boundary. |
| Description | A description for this boundary. |
| Operational status | The operational status: * Under development * Reauthorize * Operational * Decommissioned {#cam-form-authorization-boundary__ul_l5r_jnr_2nb} |
| Mission critical | Option to set the boundary as mission-critical. |
| System owner | The individual responsible for procuring, developing, integrating, modifying, operating, and maintaining an information system. |
| Information owners | The individuals responsible for statutory, management, and operational authority. |
| System users | The users responsible for performing the actual work on the system. |
| Diagrams | If needed, or if you do not have a Configuration Management Database (CMDB), add data flow, network, and boundary diagrams. |
[Table 1. Authorization Boundary form]

{#cam-form-authorization-boundary__table_epy_qrq_f5}