Difference between revisions of "Audits"

From Privacy-Now
Jump to: navigation, search
(Workflow)
(Privileges)
 
(7 intermediate revisions by one other user not shown)
Line 18: Line 18:
 
! Status !! Description
 
! Status !! Description
 
|-
 
|-
|Default || A temporary status when the ''access request'' is initially created before the first save
+
|Default || A temporary status when the ''audit'' is initially created before the first save.
 
|-
 
|-
|Opened || An ''access request'' in this status is draft and it is not actioned.
+
|Opened || An ''audit'' in this status is draft and it is not actioned yet.
 
|-
 
|-
|Requested || An ''access request'' in this status is confirmed and it is waiting to be actioned.
+
|Planned || An ''audit'' in this status is planned for execution.
 
|-
 
|-
|In charge || In this status, the ''access request'' has been taken in charge and it is being actioned.  
+
|In progress || In this status, the ''audit'' is in progress.  
 
|-
 
|-
|Cancelled || ''Access request'' cancelled. This is an end of life status.
+
|Completed || In this status, all activities related to the ''audit'' were completed and closure is expected after confirmation.
 
|-
 
|-
|Completed || In this status, all activities related to the ''access request'' were completed and closure is expected after confirmation.
+
|Closed || In this status, all activities related to the ''audit'' are completed and confirmed. This is an end of life status, meaning no further status transitions are allowed.
 
|-
 
|-
|Suspended || Activities concerning the ''access request'' are temporarily suspended, meaning no further status transitions are allowed.
+
|Cancelled || ''Audit'' cancelled. This is an end of life status.
|-
 
|Closed || In this status, all activities related to the ''access request'' are completed and confirmed. This is an end of life status, meaning no further status transitions are allowed.
 
 
|-
 
|-
 
|}
 
|}
  
 
== Information ==
 
== Information ==
''Access request'' records are organized in five sections:
+
''Audit'' records are organized in four sections:
  
* <u>''Identification''</u>, where identification data of the ''access request'' are recorded,
+
* <u>''Identification''</u>, where identification data of the ''audit'' are recorded,
* <u>''Ownership & Organization''</u>, containing the assignment of the key roles enabled to manage the ''access request'';
+
* <u>''Ownership & Organization''</u>, containing the assignment of the key roles enabled to manage the ''audit'';
* <u>''Access Request Details''</u>, with the details of the ''access request'';
+
* <u>''Details''</u>, with the details of the ''audit'' to accomplish;
* <u>''Data Subject Details''</u>, with the details of the ''data subject'' issuing the ''access request'';
+
* <u>''Results''</u>, with the conclusions of the ''audit''.
* <u>''Data Subject Representative''</u>, containing the details of the representative of the ''data subject'', if any.
 
  
 
Detailed information on the meaning and use of every field can be found by pointing the mouse on the (i) next to each field. This will activate a tooltip with a brief description of the field.  
 
Detailed information on the meaning and use of every field can be found by pointing the mouse on the (i) next to each field. This will activate a tooltip with a brief description of the field.  
Line 50: Line 47:
  
 
== Privileges ==
 
== Privileges ==
''Access request'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users & Groups]] for more information on how to set this privilege).
+
''Audit'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users & Groups]] for more information on how to set this privilege).
  
The lifecycle of the ''access request'' is managed by the roles described in the table below. ''Groups'' are pre assigned to the roles according to the ''settings'' (see [[Settings]] for more information on how to set these defaults). Initial assignments can be modified according to privileges choosing among the enabled ''groups'' (see once again [[Settings]] for more information on how to enable ''groups'').
+
The lifecycle of the ''audit'' is managed by the roles described in the table below. ''Groups'' are pre assigned to the roles according to the ''settings'' (see [[Settings]] for more information on how to set these defaults). Initial assignments can be modified according to privileges choosing among the enabled ''groups'' (see once again [[Settings]] for more information on how to enable ''groups'').
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 70: Line 67:
 
* update fields when possible.
 
* update fields when possible.
 
|-
 
|-
|<u>Audit Team</u> || Members of the ''group'' assigned to this role have view (read) privileges.
+
|<u>Auditors Supervisory Team</u> || Members of the ''group'' assigned to this role have view (read) privileges.
 
|-
 
|-
|<u>Owner</u> || This role can be assigned to a single user among members of the ''groups'' previously described. The <u>Owner</u> has several privileges:
 
* transition to any compatible status,
 
* update fields when possible.
 
 
|}
 
|}
 
== Warning and alerts ==
 
TBC
 
  
 
== Reports ==
 
== Reports ==
The list of ''access requests'' can be filtered and exported to excel format from the ''view'' '''''Access Requests'''''.
+
The list of ''audits'' can be filtered and exported to excel format from the ''view'' '''''audits'''''.
  
 
== Related processes ==
 
== Related processes ==
''Access Requests'' can be related to ''processing activities''.
+
''Audits'' can be related to ''risks'' and ''issues / non conformities''.

Latest revision as of 15:24, 28 September 2018

Introduction to Audits

Audits provide a control mechanism over personal data management system and activities.

The process enables to record audits information and to support their fulfilment.

Workflow

A new audit can be created using the Add New functionality and choosing "New Audit".

A workflow enables to move audits" in several statuses as shown in the following picture.

Audits workflow and statuses.


The following table explains the meaning of each status:

Status Description
Default A temporary status when the audit is initially created before the first save.
Opened An audit in this status is draft and it is not actioned yet.
Planned An audit in this status is planned for execution.
In progress In this status, the audit is in progress.
Completed In this status, all activities related to the audit were completed and closure is expected after confirmation.
Closed In this status, all activities related to the audit are completed and confirmed. This is an end of life status, meaning no further status transitions are allowed.
Cancelled Audit cancelled. This is an end of life status.

Information

Audit records are organized in four sections:

  • Identification, where identification data of the audit are recorded,
  • Ownership & Organization, containing the assignment of the key roles enabled to manage the audit;
  • Details, with the details of the audit to accomplish;
  • Results, with the conclusions of the audit.

Detailed information on the meaning and use of every field can be found by pointing the mouse on the (i) next to each field. This will activate a tooltip with a brief description of the field.

Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See How To for more information.

Privileges

Audit can be created by the users to whom the corresponding privilege is granted (see Users & Groups for more information on how to set this privilege).

The lifecycle of the audit is managed by the roles described in the table below. Groups are pre assigned to the roles according to the settings (see Settings for more information on how to set these defaults). Initial assignments can be modified according to privileges choosing among the enabled groups (see once again Settings for more information on how to enable groups).

Role Description
DPO Group Members of the group assigned to this role have full privileges. They can:
  • transition records to any compatible status,
  • update fields when possible,
  • update data sources directly in record management.
Data Controller Group Members of the group assigned to this role have view (read) privileges.
Data Processor Group Members of the group assigned to this role have view (read) privileges.
Working Team Members of this group have several privileges. They can manage the entire lifecycle, being enabled to:
  • transition records to any compatible status,
  • update fields when possible.
Auditors Supervisory Team Members of the group assigned to this role have view (read) privileges.

Reports

The list of audits can be filtered and exported to excel format from the view audits.

Related processes

Audits can be related to risks and issues / non conformities.