The Analytics module offers two sets of charts: the risk exposure dashboard and the activity monitoring dashboard.
Clients with multiple entities can determine the dashboard scope by selecting one or more entities.
The charts can be viewed on-screen or downloaded as data files.
Table of contents
Using the Analytics module
To use the Analytics module:
-
In the sidebar, select Management > Analytics.
2. In the back office sidebar, click Analytics and select one of the following:
-
Risk exposure
-
Activity monitoring
3. Click the Select entities field and select the entity or entities to be included in the dashboard.
4. If you selected Activity monitoring, click the Select dates field and either select a preset period or select a start date and end date to determine the period you wish to monitor.
To easily retrieve the entities and dates selected, bookmark the page using your web browser just as you would any standard web page. You can then return to the bookmark later.
5. You can now view the results on screen or download them:
- View the results on-screen: click the Show report button. If you hover the mouse over a chart, several icons and types of information appear: you can hover the “information” icon for a brief explanation (available on most charts), hover a section of the chart or text next to it for detailed data on one aspect, or click the download icon to download the data of that chart in a csv, xlsx or json file.
If you selected several entities, the results are consolidated.
-
Download the results in a PDF file: click the Download button. If several entities are selected, you can choose between a separate report for each entity selected, or a single consolidated report. For files that require significant time to generate, you will receive an email with a secure link to the PDF.
Risk exposure dashboard
The following table provides a detailed explanation of the data shown in each chart.
To view the data:
-
Select the entities.
-
Click Show report.
-
Only active processing activities are taken into account.
-
It can take up to 24 hours for changes to be taken into account in the charts.
Chart |
Description |
Processing activities |
|
Breakdown of processing activities by:
|
|
Breakdown of processing activities into those that:
|
|
Breakdown of processing activities by area and status (there may be several pages; see the arrows under the chart). |
|
Breakdown of processing activities based on information in Data section > Nature tab:
|
|
Breakdown of processing activities based on information in Data section > Categories tab. |
|
Subcontracting |
|
Number of processing activities involving third parties that are either Processors or Subprocessors (Identification section > Third parties tab > Qualification menu). |
|
Number of third parties that are either Processors or Subprocessors. Each data processor is only counted once, even if they are involved in multiple processing activities. |
|
Percentage of Processors or Subprocessors with an agreement that covers data protection as per the GDPR (third parties repository > Technical, Organisational and legal measures tab > Does the agreement with the third party cover data protection as per the GDPR? > Yes) |
|
Data flows |
|
Data based on how the Cross-border flow section is completed in each processing activity:
|
|
Global view of all cross-border flows. |
|
Software |
|
Total number of software programs in software repositories |
|
Percentage of software that has a risk rating |
|
Percentage of software that has a compliance rating |
|
For each software in the repository, the table shows:
|
|
Only includes software that has a risk rating.
Example. In this screenshot there are:
|
|
Only includes software that has a compliance rating. Same approach as for “Software count by risk rating” (see above). |
Activity monitoring dashboard
The following table provides a detailed explanation of the data shown in each chart.
To view the data:
-
Select the entities.
-
Select the dates.
-
Click Show report.
-
Only active processing activities are taken into account.
-
It can take up to 24 hours for changes to be taken into account in the charts.
Chart |
Description |
Processing activities |
|
Number of processing activities in “Being validated” status that were changed to “Validated” status during selected period. |
|
Number of times that “Validated” processing activities were changed to “To be reviewed” status during selected period. If the same processing activity is reviewed several times, each review is counted. |
|
Percentage of processing activities in “To be reviewed” status that were switched back to “Validated” during selected period. Target is 100%. |
|
Number of processing activities created during selected period. |
|
|
Shows daily number of processing activities in each status.
|
Impact assessments (PIA) |
|
Number of PIAs that were changed to “Validated” status during selected period. |
|
Number of PIAs created during selected period. |
|
Daily number of PIAs in each status. This chart works the same way as the “Processing trends” chart. See above for more information. |
|
Data subject requests (DSR) |
|
Number of DSRs received during selected period. |
|
Percentage of DSRs created and started to be processed during selected period. “Initiated” means at least partially completed by an actual person. The target is 100%. |
|
Average number of days between DSR creation and date it enters “Done” status. Includes time spent waiting for data subjects to respond to requests. |
|
Number of DSRs received, broken down by nature. If a DSR has several “natures”, each one is counted. |
|
Trends in number of DSRs created |
|
Data breaches |
|
Number of data breaches created during selected period, broken down by risk assessment. |
|
Privacy by design |
|
Number of projects closed during selected period, broken down by opinion. |
|
Number of existing projects at end of selected period, broken down by status. |
|
Number of projects created during selected period. |
|
Audits and controls |
|
Number of audits and controls started during selected period, broken down by origin (external or internal). “Started” refers to the start date entered when creating the audit or control, not the date it actually started. |
|
End-of-period status of audits and controls started during period, broken down by origin (external or internal). |
|
Actions |
|
Number of actions completed or archived during selected period. |
|
Number of actions that reached their deadline during selected period and have not been completed. |
|
Number of actions created during selected period (including those planned for a future period). |