...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Tip | ||
|---|---|---|
| ||
To use data import to alter information already in the application, see Downloading Existing Items For Update. |
| Anchor | ||||
|---|---|---|---|---|
|
To import a spreadsheet, complete the following steps:
- Click Tools | Data Import.
The Data Import page displays.
...
Click Choose CSV file to import.
- In the dialog box,
...
...
...
- click Back to return to the Data Import home page without importing items.
Accessing and Downloading the Template
Unless you already have a template with headings matching ZenGRC application fields, there are a couple of substeps necessary to import new data into ZenGRC. They include the following:
- Downloading a template for population of data.
- Completing the template with new information.
Importing new information into the application.
To download an empty spreadsheet containing data headings and columns that sync with the application, complete the following steps:
- Click Tools | Data Import.
...
The Data Import page displays.
...
| title | NOTE |
|---|
...
Click Create a CSV template.
...
...
Tip title TIP Once a selection is made, it's displayed
...
...
...
...
Tip title TIP The order in which you make selections is the order in which the headings will display in the download.
Info title NOTE To remove object selections, please see Removing Selections from the Template.
- Click Download import template. The file will download in the manner you've specified in the browser.
- Save to your computer as a CSV file.
- When opened, the spreadsheet contains all headings for each of the selections.
...
| Anchor | ||||
|---|---|---|---|---|
|
To remove section headings prior to downloading the template, complete the following:
- Click the
...
...
Continue clicking icons until unwanted selections are removed.
| Anchor | ||||
|---|---|---|---|---|
|
...
Existing information in the application can be altered by conducting the following steps:
...
| Info | ||
|---|---|---|
| ||
To configure a report and download existing information from ZenGRC, see Downloadable Reports. Once the file is downloaded, you can update and import as described in the following sections. |
...
Whether you are altering existing information in a downloaded CSV or uploading new information in a template, the rules for populating the spreadsheet are the same.
Importing Multiple Objects
You can import data for several object types at once. The spreadsheet you download would look similar to the following:
Unique Fields
...
| Tip | ||
|---|---|---|
| ||
As a best practice, we recommend using unique codes across the application. |
...
| Tip | ||
|---|---|---|
| ||
If you're importing new data, the Code* column can be left empty for autogeneration, unless you are also importing mappings to the item. |
Required Fields
Required fields are marked with an asterisk and must have data.
Optional Fields
Fields not marked with an asterisk are not required. If there is no data to import for these columns, they can be deleted to streamline the import. The application fields will be empty but can be updated at a later date.
Check Box
For a checkbox-type custom field, put "yes" (without quotes) if the checkbox should be checked. Leave the cell empty otherwise.
Leaving Fields Blank
If objects already exist, fields you leave empty are ignored. An object's attribute will not be replaced with empty information.
Mapping Items
To map items, complete the following:
...
| Tip | ||
|---|---|---|
| ||
In the following example, the first objective is mapped to an audit and a control. The map:audit column contains the audit code, which is "2017 FedRAMP Audit." And the map:control column contains the control code, which is "CTL-DFA-AC-10." |
...
| Tip | ||
|---|---|---|
| ||
More than one item can be mapped in the cell by separating them with a line break (alt+return) |
...
Existing information in the application can be altered by conducting the following steps:
- Downloading a report showing current attributes and mappings in ZenGRC
- Populating the downloaded template
- Importing updated information back into the application
| Info | ||
|---|---|---|
| ||
To configure a report and download existing information from ZenGRC, see Data Export. Once the file is downloaded, you can update and import as described in the following sections. |
| Anchor | ||||
|---|---|---|---|---|
|
Whether you are altering existing information in a downloaded CSV or uploading new information in a template, the rules for populating the spreadsheet are the same.
Importing Multiple Objects
You can import data for several object types at once. The spreadsheet you download would look similar to the following:
Unique Fields
Information in the Code* and Title* columns must be unique within the object type.
| Tip | ||
|---|---|---|
| ||
As a best practice, we recommend using unique codes across the application. |
In the following screenshot, the highlighted code, "DFA-AC-10," cannot be duplicated as a code for another objective.
| Tip | ||
|---|---|---|
| ||
If you're importing new data, the Code* column can be left empty for autogeneration, unless you are also importing mappings to the item. |
Required Fields
Required fields are marked with an asterisk and must have data.
Optional Fields
Fields not marked with an asterisk are not required. If there is no data to import for these columns, they can be deleted to streamline the import. The application fields will be empty but can be updated at a later date.
Leaving Fields Blank
If objects already exist, fields you leave empty are ignored. An object's attribute will not be replaced with empty information.
Mapping Items
To map items, complete the following:
Populate the cell under
...
...
| title | NOTE |
|---|
...
...
...
...
...
...
Tip title TIP More than one item can be
...
...
...
...
...
...
...
To import a spreadsheet, please see Importing the Template.
Changing the Code
The code of an item cannot be changed. However, you can delete the item and then import the identical information with a new code.
To change the code of an item through import, complete the following steps:
...
| Note | ||
|---|---|---|
| ||
To delete an item in order to change the code, be sure to save the information originally downloaded. This way, all data stays intact with the exception of changing the unique code. |
...
| title | TIP |
|---|
...
The following example uses the same objects mapped in the Mapping Items section. The unmap:audit column contains the code for the audit, which is "2017 FedRAMP Audit." And the unmap:control column contains the code for the control, which is "CTL-DFA-AC-10."
Tip title TIP More than one item can be unmapped in the cell by separating them with a line break (altl+return).
| Anchor | ||||
|---|---|---|---|---|
|
To remove items from the application, complete the following:
In the Delete column for the rows being deleted, put "true" with no quotes. On import, this deletes the object, related data, and related mappings to other items.
| Anchor | ||||
|---|---|---|---|---|
|
To change a user's access through import, complete the following steps:
Download a report with the People object type.
Info title NOTE To
...
...
...
| Info | ||
|---|---|---|
| ||
To configure a report and download existing information from ZenGRC, see Downloadable Reports. |
In the Role column, change the information to one of the following:
...
No Access
...
Creator
...
Reader
...
Editor
...
| Info | ||
|---|---|---|
| ||
A user cannot be deleted. Setting a user's access to No Access instead of deleting it allows all history to remain untouched and retrievable. And it means the user cannot log in to the application. |
...
| Info | ||
|---|---|---|
| ||
To import a spreadsheet, see Importing the Template. |
Importing Values for a Checkbox Attribute
If you have a checkbox-type custom field, enter "yes" without the quotes if the checkbox should be checked. Leave the cell empty otherwise.
Assigning Owners
To assign an owner, complete the following:
...
| Tip | ||
|---|---|---|
| ||
Only email addresses existing in the application will be imported. An address that doesn't exist will prompt an error and be assigned to the person importing the data. A workaround is to create a placeholder account in ZenGRC with an email address to use for import until you decide an owner. |
Import Limit
...
to No Access instead of deleting it allows all history to remain untouched and retrievable. It also means the user can no longer log in to the application.
Importing Values for a Checkbox Attribute
If you have a checkbox-type custom field, enter "yes" without the quotes if the checkbox should be checked. Leave the cell empty otherwise.
Assigning Owners
To assign an owner, complete the following:
Add the person's email address in the Owner* column.
Tip title TIP Only email addresses existing in the application will be imported. An address that doesn't exist will prompt an error and be assigned to the person importing the data. A workaround is to create a placeholder account in ZenGRC with an email address to use for import until you decide on an owner.
Importing Risk Factor Values (Available from October 20th, 2020)
The new risk import templates and the newly exported risk CSVs have editable Factor columns. The top row of each factor column lists out the valid Factor option values(copied from the app instance). An option can be copied and pasted into the Factor column for easier selection.
| Info | ||
|---|---|---|
| ||
|