Importing scope assignments

Roles and permissions

Only administrators can import scope assignments

Note

Currently, it's only possible to edit existing scope assignments via CSV import. Additionally, Hyperproof supports one scope per control in the CSV import. Improvements to the scope assignment import process are ongoing.

If your organization has a large number of scope assignments to link to controls, you can import them into Hyperproof via CSV.

Note

The steps on this page walk you through importing scope assignments that are linked to controls. If you want to import just scopes, refer to Importing scopes.

Tip

Adding additional information does not overwrite existing data. During the import, Hyperproof searches for any exact data identifiers. If it doesn’t find any, it treats the data as new. If it finds a match, it updates the existing data.

Step One: Downloading the example CSV

The easiest way to start importing scope assignments is by downloading Hyperproof’s example CSV. The example CSV file provides the exact template for successfully importing scope assignments into Hyperproof.

From the left menu, select Controls.
Note
Be sure to import via the Controls module.
Importing scope assignments via the Controls tab within a program causes errors as Hyperproof reads the import file as trying to connect the scope controls directly to the requirements.
Click Import.
The Import controls window opens.
Click Download the example CSV.

Step Two: Editing the CSV

Replace the contents of the example CSV file with your own scope assignments. Be sure to follow the format of the example file, as well as the instructions on the page, to ensure that your scope assignments can be successfully imported.

Note

The CSV must contain ALL headings listed below even if they are optional. Keep in mind that headings are case-sensitive!

Heading
ID	Should contain a control ID that's unique to your organization. This field is required. Tip: Control IDs play an important role in the import process and must be unique across your Hyperproof organization. If the control ID is not unique, this row is skipped.
Name	This is the name of the control. This is an optional field.
Description	This is the full definition of the control. It can be a multi-line string. This field is required. The multi-line text limit for the description field is 65,535 characters. However, if you have a field with over 10,000 characters, it's highly recommended that you save the data in a document and link it as proof.
Domain	Used to group related controls, e.g. Change management, PeopleOps, etc. This is an optional field.
Owner	Must be formatted as FirstName LastName (email address), i.e. Jennifer Cook (jcook@lunabtechnologies.org). This is an optional field. Tip: If no control owner is provided, the control is assigned to the individual who imports the CSV. Additional tip: The owner's email address must match the email address they use to sign in to Hyperproof.
Notes	A field for any notes related to the control. This is an optional field.
Implementation	A field for tracking the implementation of the control. This is an optional field. Tip: Hyperproof recognizes the following implementation statuses: Unknown, Not started, In progress, and Completed.
Testing status	Used to track where the control is in terms of testing. This is an optional field. Tip: Hyperproof recognizes the following testing statuses: Not tested, In progress, Effective, and Ineffective.
Scopes	Used to link a scope assignment to a control. Scope assignments can be linked to existing controls or to new controls. Additionally, scope assignments can be imported in bulk via the main control or individually via the scope assignment control. This is an optional field. Tip: Make sure the heading is Scopes and the scope name matches the name in Hyperproof.
Custom fields	A space for any custom fields your organization uses to track activity related to a specific object, e.g. a control. Tip: The custom field(s) must already exist in your organization. Additional tip: Ensure custom field names are spelled exactly as they are in Hyperproof. For example, if a custom field is called Security (with a capital 'S'), the CSV heading needs also to have a capital 'S'. If a custom field is called Risks, and the CSV heading is Risk, the import fails.

Below is a snippet of a sample import file.

Step Three: Importing the CSV

After you’ve made the necessary changes to the CSV, it can be imported into Hyperproof.

Drag and drop the CSV file into the Upload CSV File field, or click Select file to upload to upload it manually.
Click Import.
Hyperproof checks the CSV to ensure that there are no errors. You’ll be alerted if Hyperproof encounters any errors.
If Hyperproof didn’t detect any errors, click Next. If Hyperproof detected errors, do one or both of the following:
1. First, use the Error viewer to identify the errors. Second, correct the errors directly in the CSV. This ensures that the CSV is up-to-date should you need to re-import in the future.
  Tip
  Use the forward and backward arrows to cycle through the errors. The Error viewer gives specific information on what needs to be corrected.
2. Remove rows that contain errors by clicking Remove all rows with errors. Note that this doesn't remove any data in the actual CSV.
Click Next.
The CSV is imported.

In this section:

Importing scope assignments

Roles and permissions

Note

Note

Tip

Step One: Downloading the example CSV

Note

Step Two: Editing the CSV

Note

Step Three: Importing the CSV

Tip

Search results