Exporting Data in the Compliance Management Module
In the Compliance Management module, you can export data about your scoped requirements, controls, and tasks. Then, you can download this export as a CSV file to review your data and keep records of data you may need in the future.
When you export data from the Compliance Management module, the CSV exports will be available on the Data Exports page. From the Data Exports page, you can download data exports to your device. To learn about all of the data exports available in your account, see our Data Exports Guide.
See the sections below for information about the data exports available in the Compliance Management module. each of these data exports.
Jump to:
Exporting Scoped Requirements
You can export a CSV file of all requirements that are included in a scope. This CSV file will include information such as the requirement self-assessment responses and requirement notes.
To export and download a CSV file of scoped requirements, follow the steps below.
- Navigate to Compliance > Scopes from the navigation panel.
- Click on the name of the scope that contains the requirements that you would like to export.
- Click the Requirements tab.
- Click the Export CSV button.
Tip: If you apply filters or perform a search in the requirements table before clicking the Export CSV button, only the filtered results will be included in your export.
- In the Name of Export field, enter a name for your data export.
- Click the Create Export button.
- Navigate to Data Exports from the navigation panel.
- Find the data export that you created.
Note: In the Type column of the Data Exports page, scoped requirement exports are labeled Scoped Requirements.
- In the Actions column, click the Download button.
After you download your scoped requirements export, you can open the CSV file in your preferred spreadsheet program. See the table below to learn about the types of data that the scoped requirement export will include.
| Column Header | Description |
| Requirement ID | The requirement's ID. Note: If you are viewing your CSV file in Microsoft Excel, auto-formatting features may cause certain requirement IDs to display inaccurately. For example, if your requirement ID is "1 a", Microsoft Excel may auto-format this as "1:00 AM".
|
| Name | The name of the requirement. |
| Description | The requirement's description. |
| Self-Assessment Response | The response that was selected for the requirement when you completed the Scope Self-Assessment.
|
| Number of Controls | The number of controls that are mapped to the requirement. |
| Tags | The tags you have added to the requirement, if applicable. |
| Notes | The notes that users have left on the requirement. Each note entry includes the first and last name of the user who left the note and the date and time that they left the note. The date and time are in Coordinated Universal Time, or UTC, format.
Note: If your notes for a requirement exceed 2,500 characters, some of the notes will not be included in your export.
|
Exporting Controls
You can export a CSV file of the controls in your account. This CSV file will include information such as the number of mapped requirements and the number of task schedules for a control.
To export and download a CSV file of controls, follow the steps below.
- Navigate to Controls from the navigation panel.
- Click the Export CSV button.
Tip: If you perform a search in the controls table before clicking the Export CSV button, only the filtered results will be included in your export.
- In the Name of Export field, enter a name for your data export.
- Click the Create Export button.
- Navigate to Data Exports from the navigation panel.
- Find the data export you created.
Note: In the Type column of the Data Exports page, control exports are labeled Controls.
- In the Actions column, click the Download button.
After you download your controls export, you can open the CSV file in your preferred spreadsheet program. See the table below to learn about the types of data that the controls export will include.
| Column Header | Description |
| Name | The name of the control. |
| Description | The control description. |
| User Assigned | The name of the user who is assigned to the control, if applicable. |
| Group Assigned | The name of the user group who is assigned to the control, if applicable.
|
| Group Lead | If a user group is assigned to the control, this column displays the name of the person who is the group lead for the group. |
| Approving Manager | The Approving Manager's name, if one is assigned to the control. |
| Second Level Approving Manager | The Second-level Approving Manager's name, if one is assigned to the control. |
| Number of Mapped Risks | The number of risks that are mapped to the control.
|
| Number of Schedules | The number of task schedules that have been created for the control.
|
| Number of Requirements | The number of scoped requirements that are mapped to the control.
Note: If you are a Scope Administrator who does not have access to all of the scopes in your account, this column shows the number of scoped requirements under your allowed scopes that are mapped to this control.
|
| Control Health | The control's Control Health percentage. |
| Tags | The tags that you have added to this control, if applicable. |
| Treatment Score | If the control's treatment score, if applicable.
|
| Notes | The notes that users have left on this control. Each note entry includes the first and last name of the user who left the note and the date and time that they left the note. The date and time will be in Coordinated Universal Time, or UTC, format.
Note: If your notes for a control exceed 2,500 characters, some of the notes will not be included in your export.
|
| Number of One-Time Tasks | The number of one-time tasks that have been created for this control.
|
View Control Page: Control Notes
Exporting Tasks
You can export a CSV file of the tasks in your platform. This export will include information such as the user assigned, the task status, the date the task was satisfied.
To export and download a CSV file of tasks, follow the steps below.
- Navigate to Tasks from the navigation panel.
- Click the Export CSV button.
Tip: If you apply filters or perform a search in the tasks table before clicking the Export CSV button, only the filtered results will be included in your export.
- In the Name of Export field, enter a name for your data export.
- Click the Create Export button.
- Navigate to Data Exports from the navigation panel.
- Find the data export you created.
Note: In the Type column of the Data Exports page, task exports are labeled Tasks.
- In the Actions column, click the Download button.
After you download your tasks export, you can open the CSV file in your preferred spreadsheet program. See the table below to learn about the types of data that CSV file will include.
| Column Header | Description |
| Task Name | The name of the task. |
| User Assigned | The first and last name of the user who is assigned to the task. |
| Approving Manager | The Approving Manager's name, if one is assigned to the task. |
| Second-Level Approving Manager | The Second-level Approving Manager's name, if one is assigned to the task. |
| Status | This is the Current Task Status that is shown on the Task Status area of the View Task page (click to view example).
|
| Stage | This is the Task Stage that is shown on the Task Status area of the View Task page (click to view example).
|
| Satisfied Date | The date that the User Assigned marked the task as complete.
|
| Due Date | The task's due date.
|
| Notes | The notes that users have left on this task. Each note entry includes the first and last name of the user who left the note and the date and time that they left the note. The date and time will be in Coordinated Universal Time, or UTC, format.
Note: If your notes for a task exceed 2,500 characters, some of the notes will not be included in your export.
|
| Control Name | The name of the control that the task is associated with. |
Example: Current Task Status
Example: Current Task Status
View Task Page: Task Notes
Comments
0 comments
Article is closed for comments.