Define the authorization boundary

task australia Updated Sep 10, 2026 1 min read define-auth-boundaries.md

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

Before you begin

Role required: sn_irm_cont_auth.system_owner or sn_irm_cont_auth.admin

Procedure

Navigate to All > Continuous Authorization & Monitoring > All Authorization Boundaries.
Select New and then fill in the form.

The settings are described in Fields on the Authorization Boundary form.
Save the record.

Use the tabs that appear to identify which systems and parts of systems you own and should go through the authorization process.
You can use the Boundary Filters tab to create filters for identifying all of your system elements.

After running the filters, the results appear in the System Elements tab.
If elements appear that should not be included in the authorization process, you can select them, and select Delete from the Actions on selected rows list at the bottom of the screen.
You can select New to include additional assets or systems to the list of system elements in the authorization boundary.

What to do next

Parent Topic:RMF step 0 - Prepare the authorization package

50 lines · 2.7 KB Wrap lines

---
title: Define the authorization boundary
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/australia/governance-risk-compliance/continuous-risk-monitoring/define-auth-boundaries.html
release: australia
product: Continuous Risk Monitoring
classification: continuous-risk-monitoring
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [RMF step 0 - Prepare the authorization package, Use, Continuous Authorization and Monitoring, Governance, Risk, and Compliance]
---

# Define the authorization boundary

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

## Before you begin

Role required: sn\_irm\_cont\_auth.system\_owner or sn\_irm\_cont\_auth.admin

## Procedure

1. Navigate to **All** &gt; **Continuous Authorization &amp; Monitoring** &gt; **All Authorization Boundaries**.

2. Select **New** and then fill in the form.

The settings are described in [Fields on the Authorization Boundary form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/continuous-risk-monitoring/cam-form-authorization-boundary.md).

3. Save the record.

Use the tabs that appear to identify which systems and parts of systems you own and should go through the authorization process.

4. You can use the **Boundary Filters** tab to create filters for identifying all of your system elements.

After running the filters, the results appear in the **System Elements** tab.

5. If elements appear that should not be included in the authorization process, you can select them, and select **Delete** from the **Actions on selected rows** list at the bottom of the screen.

6. You can select **New** to include additional assets or systems to the list of system elements in the authorization boundary.

## What to do next

This completes the procedure for defining the authorization boundary. The next step is to create the authorization package that will be processed through approvals. You can initiate the process by clicking the **Authorization Packages** tab or via the navigation pane. For details, see [Create an authorization package](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/continuous-risk-monitoring/create-auth-package.md).

**Parent Topic:**[RMF step 0 - Prepare the authorization package](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/continuous-risk-monitoring/prepare-auth-pkg.md)