Data Breaches - Revision history

Cbisso: /* Privileges */

2018-10-10T10:31:05Z

‎Privileges

Cbisso: /* Introduction to Data Breaches */

2018-09-24T09:57:04Z

‎Introduction to Data Breaches

Sottini: /* Information */

2018-09-13T20:56:38Z

‎Information

Sottini: /* Privileges */

2018-09-13T20:56:13Z

‎Privileges

Sottini: /* Related processes */

2018-09-13T20:54:44Z

‎Related processes

Sottini: /* Reports */

2018-09-13T20:53:42Z

‎Reports

Sottini: /* Workflow */

2018-09-13T20:53:07Z

‎Workflow

Sottini: /* Information */

2018-09-13T20:52:21Z

‎Information

Sottini: /* Workflow */

2018-09-13T20:46:23Z

‎Workflow

Sottini: /* Workflow */

2018-09-13T20:45:29Z

‎Workflow

@@ Line 72: / Line 72: @@
 * update fields when possible.
 |-
-|<u>Audit Team</u> || Members of the ''group'' assigned to this role have view (read) privileges.
+|<u>Auditors 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:

@@ Line 1: / Line 1: @@
 == Introduction to Data Breaches ==
-Data breaches workflow provide the mean to manage the lifecycle of 'data breaches''. This means recording and updating the information related to the ''data breach'', supporting the tasks needed for remediation and the needed communication.
+Data breaches workflow provide the mean to manage the lifecycle of ''data breaches''. This means recording and updating the information related to the ''data breach'', supporting the tasks needed for remediation and the needed communication.
 == Workflow ==

@@ Line 37: / Line 37: @@
 == Information ==
-''Access request'' records are organized in seven sections:
+''Data breach'' records are organized in seven sections:
 * <u>''Identification''</u>, where identification data of the ''data breach'' are recorded,

@@ Line 52: / Line 52: @@
 == 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).
+''Data breaches'' 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 ''dta breach'' 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"
@@ Line 68: / Line 68: @@
 |<u>Data Processor Group</u> || Members of the ''group'' assigned to this role have view (read) privileges.
 |-
-|<u>Working Team</u> || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:
+|<u>Investigation Team</u> || 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.

← Older revision		Revision as of 20:54, 13 September 2018
Line 86:		Line 86:

	== Related processes ==		== Related processes ==
−	''~~Access Requests~~'' can be related to ''~~processing activities~~''.	+	''Data breaches'' can be related to ''risks'', ''actions'' and ''issues / non conformities''.

@@ Line 83: / Line 83: @@
 == Reports ==
-The list of ''access requests'' can be filtered and exported to excel format from the ''view'' '''''Access Requests'''''.
+The list of ''data breaches'' can be filtered and exported to excel format from the ''view'' '''''Data Breaches'''''.
 == Related processes ==
 ''Access Requests'' can be related to ''processing activities''.

@@ Line 24: / Line 24: @@
 |In charge || In this status, the ''data breach'' has been taken in charge and it is being actioned.
 |-
-|Notified || In this status, the ''data breach'' has been notified to the authority.
+|Notified || In this status, the ''data breach'' has been notified to the interested parties.
 |-
 |Resolved || In this status, all activities related to the ''data breach'' are completed and closure is expected after confirmation of remediation.

@@ Line 37: / Line 37: @@
 == Information ==
-''Access request'' records are organized in five sections:
+''Access request'' records are organized in seven sections:
-* <u>''Identification''</u>, where identification data of the ''access request'' are recorded,
+* <u>''Identification''</u>, where identification data of the ''data breach'' 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 ''data breach'';
-* <u>''Access Request Details''</u>, with the details of the ''access request'';
+* <u>''Investigator''</u>, with the details of the resource in charge of investigating the ''data breach'';
-* <u>''Data Subject Details''</u>, with the details of the ''data subject'' issuing the ''access request'';
+* <u>''Data Breach Details''</u>, with the details of the ''data breach'';
-* <u>''Data Subject Representative''</u>, containing the details of the representative of the ''data subject'', if any.
+* <u>''Data Breach Impact''</u>, containing information about the ''data breach'' impact;
 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 32: / Line 32: @@
 |Closed || In this status, all activities related to the ''data breach'' are performed and remediation / communications are completed. This is an end of life status, meaning no further status transitions are allowed.
 |-
-|Cancelled || 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.
+|Cancelled || ''Data breach'' cancelled. This is an end of life status.
 |-
 |}

@@ Line 30: / Line 30: @@
 |Suspended || Activities concerning the ''data breach'' are temporarily suspended.
 |-
-|Closed || In this status, all activities related to the ''data breach'' are completed and remediation is confirmed. This is an end of life status, meaning no further status transitions are allowed.
+|Closed || In this status, all activities related to the ''data breach'' are performed and remediation / communications are completed. This is an end of life status, meaning no further status transitions are allowed.
 |-
 |Cancelled || 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.