Fields on the Authorization Boundary form

reference brazil Updated Sep 10, 2026 1 min read cam-form-authorization-boundary.md

An authorization boundary defines the scope of a particular system that can be continuously managed and monitored using the CAM application.

Field	Description
Name	A unique and descriptive name for this boundary.
Description	A description for this boundary.
Operational status	Option to set the status of the boundary. The operational status:- Under development Reauthorize Operational Decommissioned
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.

**Parent Topic:**[Reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/governance-risk-compliance/continuous-risk-monitoring/reference-grc-cam.md)

97 lines · 2.1 KB Wrap lines

---
title: Fields on the Authorization Boundary form
description: An authorization boundary defines the scope of a particular system that can be continuously managed and monitored using the CAM application.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/governance-risk-compliance/continuous-risk-monitoring/cam-form-authorization-boundary.html
release: brazil
product: Continuous Risk Monitoring
classification: continuous-risk-monitoring
topic_type: reference
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Reference, Continuous Authorization and Monitoring, Governance, Risk, and Compliance]
---

# Fields on the Authorization Boundary form

An authorization boundary defines the scope of a particular system that can be continuously managed and monitored using the CAM application.

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

Field

</th><th>

Description

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

Name

</td><td>

A unique and descriptive name for this boundary.

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

Description

</td><td>

A description for this boundary.

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

Operational status

</td><td>

Option to set the status of the boundary. The operational status:-   Under development
-   Reauthorize
-   Operational
-   Decommissioned

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

Mission critical

</td><td>

Option to set the boundary as mission-critical.

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

System owner

</td><td>

The individual responsible for procuring, developing, integrating, modifying, operating, and maintaining an information system.

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

Information owners

</td><td>

The individuals responsible for statutory, management, and operational authority.

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

System users

</td><td>

The users responsible for performing the actual work on the system.

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

Diagrams

</td><td>

If needed, or if you do not have a Configuration Management Database \(CMDB\), add data flow, network, and boundary diagrams.

</td></tr></tbody>
</table>**Parent Topic:**[Reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/governance-risk-compliance/continuous-risk-monitoring/reference-grc-cam.md)