Adding and Removing Scoped Requirements

In KCM GRC, working in scopes will help your organization focus on meeting its compliance objectives. As a best practice for creating scopes that contain scoped requirements, we recommend either converting a custom template into a scope or converting a managed template into a scope. For more information about creating scopes from a custom template, please see our How to Create Custom Templates for Scopes article.  

After you convert a template into a scope, you can add additional requirements to the scope without affecting the template. In this article, you will learn how to create new requirements for scopes, map existing requirements to scopes, and remove requirements from scopes. 

Jump to:

Creating Requirements for Scopes

Mapping Requirements to Scopes

Unmapping Requirements from Scopes

Creating Requirements for Scopes

After you create a scope, you can create new requirements from the View Scope page. The requirements will automatically map to that scope. Then, these requirements will also appear in your requirement repository. To access your requirement repository, navigate to Compliance > Requirements.

Please follow the instructions below to create a new requirement for a scope.

1. Navigate to Compliance > Scopes from the navigation panel. 
2. Select a scope from the Name column. 
3. Click the Requirements tab on the View Scope page. 
4. Click the Create Requirement button. 
5. In the Create Requirement window, enter information into each of the fields by following the instructions below.
   Note: We recommend that you avoid including the < and > special characters in these fields.
   
   • Name: Enter a descriptive title for the requirement. 
   • Description: Enter a description for the requirement. Describe the purpose of the requirement, such as a compliance objective, audit finding, best practice, or any other obligation that your organization is striving to achieve. 
   • Primary ID: Enter a unique identifier to specify where this requirement will appear in your requirement repository. To learn more about how to use the Primary ID in KCM GRC, please see the Import Requirements in Bulk section of our How to Create Custom Templates for Scopes article. 
   • Sub ID: Enter a unique identifier that will attach to the Primary ID. To learn more about how to use the Sub ID in KCM GRC, please see the Import Requirements in Bulk section of our How to Create Custom Templates for Scopes article.  
   • ID Separator: (Optional) Select the character that will separate the Primary ID and the Sub ID.
     • If you do not select a character and your identifiers only contain numbers, the separator will default to a period.
     • If you do not select a character and your identifiers contain both numbers and letters, the separator will default to a space.
   • Tags: (Optional) Select one or more tags if you want to group this requirement with other requirements that have the same tags. 
     • To create a new tag, type one or more words in the field, and press the Enter key on your keyboard to save the tag. Tags have a maximum of 25 characters, including spaces.
     • To select an existing tag, click the drop-down menu to view existing tags. Click a tag to add it to the template.
   • Click the Create button in the bottom-left corner of the window. 

Back to top

Mapping Requirements to Scopes

After you create a scope, you can map one or more of the requirements that exist in your requirement repository to that scope. For example, if you created a scope with a  managed template and a new version of that managed template becomes available, you may want to map new requirements to the scope. To view an updated list of the managed templates we offer, see our Managed Templates article. 

Please follow the instructions below to map existing requirements to a scope. 

1. Navigate to Compliance > Scopes from the navigation panel. 
2. Select a scope from the Name column. 
3. Click the Requirements tab on the View Scope page. 
4. Click the Map Requirements to Scope button. 
5. In the Map Requirements to Scope window, select the check boxes next to one or more requirements.
   Note: The Map Requirements to Scope window contains all of the requirements in your requirement repository that are not currently mapped to the scope.
6. Click the Map button in the bottom-left corner of the window. 

Back to top

Unmapping Requirements from Scopes

You can unmap requirements to remove them from a scope. For example, if you created a scope with a managed template and a new version of that managed template becomes available, you may want to unmap requirements from the scope. To view an updated list of the managed templates we offer, see our Managed Templates article. 

Please follow the instructions below to unmap a requirement from a scope. 

1. Navigate to Compliance > Scopes from the navigation panel. 
2. Select a scope from the Name column. 
3. Click the Requirements tab on the View Scope page.
4. Identify the requirement that you want to unmap from the scope. 
5. Click the Unmap button in the Actions column.

Back to top