Templates and Scopes

How to Clone a Scope

In KCM GRC, there are two primary options for creating a scope:

  1. Clone a scope that you have already created
  2. Create a template and convert the template into a scope (you can create multiple scopes from one template)

Cloning a scope may be helpful if you have mapped controls to the requirements in your original scope, you can copy the requirement-to-control mappings into the new scope. 

Note: If you do not want to keep the same requirement-to-control mappings in the new scope, we suggest creating the scope from a template instead. For details, see our How to Create Custom Templates for Scopes article 

See the following sections to learn how to clone a scope and the two options you have under this workflow. 

Note:When you clone a scope, the tasks in the original scope will not be copied to the cloned scope.

Jump to:

Cloning a Scope

Cloning a Scope 

To clone a scope, follow these steps: 

  1. From the navigation panel on the left side of your account, click Compliance > Scopes
  2. From the Name column, click on the name of the scope you would like to clone. 
  3. From the View Scope page, click the Clone button toward the upper right-hand corner of the page. 
  4. A prompt (shown below) will appear with two options for how you'd like the system to handle the controls that are mapped to the requirements in your original scope.
    Tip: If you'd like to review the controls that are mapped to the original scope, click Cancel. Then, from the View Scope page, click the Controls tab.
    You can choose between Option 1: Map the existing controls to the new scope, or Option 2: Duplicate the existing controls and map them to the new scope.

See the following two sections for more information on each of these options.

Important: If you choose Option 2: the original controls' task schedules will not transfer to the duplicated (new) controls. You will need to create new task schedules for the duplicated (new) controls.If you choose either option: The Scope's Self-Assessment Responses will not transfer to the new scope.

Option 1: Map Existing Controls to the New Scope

The first option you have when cloning scopes is to Map Existing Controls to the New Scope.

If you choose the Map Existing option, the controls that are mapped to the requirements under your original scope will be reused. This means, the controls will maintain their existing mappings and the system will also map these controls to the requirements under your cloned scope.For more information on control and requirement mappings, see our How to Map Requirements and Controls article.

After clicking the Map Existing button, you will see the View Scope page for the cloned scope (shown below). The word "Clone" is added to the name of your cloned scope. If you would like to edit the scope name, click the Update button in the upper right-hand area of the page. 

Click the Controls tab to view the controls that are mapped to requirements under your cloned scope. 

Option 2: Duplicate Controls and Map to the New Scope

The second option you have when cloning scopes is to Duplicate Controls and Map to the New Scope.

If you choose the Duplicate option, the system will create a duplicate of each control that is mapped to a requirement under your original scope. Duplicate controls are created with the same Control Name and Control Description. The system maps the duplicate control to the appropriate requirement in your cloned scope.For more information on control and requirement mappings, see our How to Map Requirements and Controls article.

After clicking the Duplicate button, you will see the View Scope page for the cloned scope (shown below). The word "Clone" is added to the name of your cloned scope. If you would like to edit the scope name, click the Update button in the upper right-hand area of the page. 

Click the Controls tab to view the controls that are mapped to requirements under your cloned scope. 

Can't find what you're looking for?

Contact Support