RMF step 0 - Prepare the authorization package
concept australia Updated Sep 10, 2026 1 min read prepare-auth-pkg.md
In the Prepare step, you set up authorization boundaries, control overlays, and information types, as well as create the actual authorization package.
Your actions in the Prepare step
-
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. -
Create an authorization package
After you have defined the authorization boundaries for the assets or systems to send through the Authorization to Operate process, you must create an authorization package for that purpose. The package is processed through the seven steps mandated by the RMF.
Parent Topic:Governance, Risk, and Compliance
31 lines · 2.3 KB
--- title: RMF step 0 - Prepare the authorization package description: In the Prepare step, you set up authorization boundaries, control overlays, and information types, as well as create the actual authorization package. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/continuous-risk-monitoring/prepare-auth-pkg.html release: australia product: Continuous Risk Monitoring classification: continuous-risk-monitoring topic_type: concept last_updated: "2026-09-10" reading_time_minutes: 1 breadcrumb: [Use, Continuous Authorization and Monitoring, Governance, Risk, and Compliance] --- # RMF step 0 - Prepare the authorization package In the Prepare step, you set up authorization boundaries, control overlays, and information types, as well as create the actual authorization package. ## Your actions in the Prepare step - [Define the authorization boundary](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/continuous-risk-monitoring/define-auth-boundaries.md) - [Create an authorization package](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/continuous-risk-monitoring/create-auth-package.md) - **[Define the authorization boundary](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/continuous-risk-monitoring/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. - **[Create an authorization package](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/continuous-risk-monitoring/create-auth-package.md)** After you have defined the authorization boundaries for the assets or systems to send through the Authorization to Operate process, you must create an authorization package for that purpose. The package is processed through the seven steps mandated by the RMF. **Parent Topic:**[Governance, Risk, and Compliance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/r_WhatIsGRC.md)
| title | RMF step 0 - Prepare the authorization package |
| description | In the Prepare step, you set up authorization boundaries, control overlays, and information types, as well as create the actual authorization package. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/governance-risk-compliance/continuous-risk-monitoring/prepare-auth-pkg.html |
| release | australia |
| product | Continuous Risk Monitoring |
| classification | continuous-risk-monitoring |
| topic_type | concept |
| last_updated | 2026-09-10 |
| reading_time_minutes | 1 |
| breadcrumb | UseContinuous Authorization and MonitoringGovernanceRiskand Compliance |