GDPR Compliance Journey - 14 Process Documentation

Gydeline
17 May 201805:10

Summary

TLDRIn this informative video, Mike Sutherland discusses the essential steps for establishing and maintaining processes under the General Data Protection Regulation (GDPR). He emphasizes the importance of documenting, implementing, and communicating processes such as data mapping and subject access requests. The video provides a detailed walkthrough of a subject access request process document, highlighting the need for a clear process owner, purpose, and regular review to ensure ongoing improvement and compliance with GDPR standards.

Takeaways

  • 📝 Documenting Processes: The importance of documenting processes is emphasized, including the need for implementation and communication within the organization.
  • 🔄 Continuous Improvement: Processes should be reviewed regularly to ensure ongoing improvement and documentation of these revisions.
  • 👤 Process Ownership: Assigning an owner to each process, such as a data protection officer, ensures accountability and responsibility.
  • 🔍 Purpose Clarification: Describing the purpose of each process clearly helps to avoid confusion and ensures everyone understands its necessity.
  • 📋 Process Steps: Outlining the steps involved in a process, such as subject access requests, helps standardize the approach and facilitates compliance.
  • 🔗 Policy Linkage: Indicating which policies relate to a process and vice versa provides a clear connection between procedural actions and overarching guidelines.
  • 🗓️ Review and Update: Regularly updating the process documentation with the latest version and date ensures the information remains current and relevant.
  • 📬 Communication: Communicating processes effectively to all members of the organization is crucial for compliance and efficiency.
  • 📈 Process Review Cycle: The script highlights the cyclical nature of process review and improvement, suggesting a never-ending quest for betterment.
  • 📚 Subject Access Request Example: The script provides a detailed example of a subject access request process, illustrating the steps and considerations involved.
  • 🔑 SLA and Categorization: Setting Service Level Agreements (SLAs) and categorizing requests within processes helps manage expectations and workflow.

Q & A

  • What is the main topic of the video script?

    -The main topic of the video script is discussing the various processes required as part of the General Data Protection Regulation (GDPR), such as data mapping, data protection, impact assessments, subject access requests, breach process reviews, and the steps to document, implement, and review these processes.

  • What are the key steps mentioned in the script for putting a process together?

    -The key steps mentioned are: documenting the process, implementing the process with systems in place, communicating the process to the organization, regularly reviewing the process, and improving it as needed.

  • What is the importance of documenting a process in GDPR compliance?

    -Documenting a process is important because it provides a clear record of the steps involved, ensures that the process is understood and followed correctly, and helps in maintaining compliance with GDPR requirements.

  • Why is it necessary to implement a process after documenting it?

    -Implementing a process after documenting it is necessary to ensure that the documented procedures are actually being followed in practice, and that the systems and resources are in place to support the process.

  • How does communication of the process contribute to GDPR compliance?

    -Communication ensures that everyone in the organization is aware of the process, which is crucial for GDPR compliance as it involves collective responsibility and understanding of data protection measures.

  • What is the role of the process owner in GDPR process management?

    -The process owner is responsible for overseeing the process, ensuring its proper implementation, and making sure it is reviewed and updated as needed. In the script, Mike Savile is identified as the process owner for the subject access request process.

  • What is a subject access request and why is it important under GDPR?

    -A subject access request is a request made by an individual to a data controller to access their personal data. It is important under GDPR as it allows individuals to exercise their rights to information and ensures transparency and accountability in data handling.

  • What are the steps involved in the subject access request process as described in the script?

    -The steps include receiving the request, sending an email to acknowledge it, categorizing the request, setting an SLA time, managing and logging it by the help desk, and recognizing any sub-processes such as data export, erasure, or correction before closing the ticket.

  • How does the script relate the process to policies in GDPR compliance?

    -The script indicates that processes should be related to and referenced by relevant policies, ensuring that the procedures are aligned with the organization's policy framework and GDPR requirements.

  • What is the significance of maintaining a version history and last updated date for a process document?

    -Maintaining a version history and last updated date helps track changes and improvements over time, ensuring that the process is current and compliant with the latest regulations and best practices.

  • What will be the topic of discussion in the next video according to the script?

    -The next video will be discussing contracts, which is another important aspect of GDPR compliance.

Outlines

00:00

📝 GDPR Process Documentation and Implementation

In this segment, Mike Sutherland introduces the topic of processes required under the General Data Protection Regulation (GDPR). He discusses the importance of documenting processes such as data mapping, data protection, impact assessments, and subject access requests. Mike emphasizes the need to not only document these processes but also to implement them with appropriate systems in place. Communication of these processes to all members of the organization is highlighted as a key step. The video script also stresses the necessity of regular review and improvement of these processes, illustrating the cyclical nature of process documentation and enhancement. An example of a subject access request process document is provided, detailing its structure, including the process title, type, status, owner, purpose, steps, related policies, and the document's version and update history.

05:01

🔍 Upcoming Discussion on Contracts in GDPR Compliance

The second paragraph of the script teases the next topic of discussion, which is contracts, in the context of GDPR compliance. It serves as a brief transition, indicating that the focus will shift to contracts in the subsequent video, without going into the specifics of what will be covered. The speaker expresses hope that the audience finds their compliance journey straightforward, suggesting that the content provided so far has been helpful and accessible.

Mindmap

Keywords

💡GDPR

GDPR stands for General Data Protection Regulation, which is a regulation in EU law on data protection and privacy for all individuals within the European Union (EU) and the European Economic Area (EEA). It also addresses the transfer of personal data outside these areas. In the video, GDPR is the main theme, as the discussion revolves around the processes required for compliance with this regulation.

💡Data Mapping

Data mapping refers to the process of creating a detailed diagram or model of data flows within an organization. It is a crucial step in understanding and managing data for GDPR compliance. In the script, data mapping is listed as one of the processes required as part of GDPR, indicating its importance in tracking and managing personal data.

💡Data Protection

Data protection involves safeguarding the privacy and integrity of data. It is a fundamental aspect of GDPR, which requires organizations to implement measures to protect personal data from unauthorized access or breaches. The script mentions data protection as one of the processes that organizations need to consider for GDPR compliance.

💡Impact Assessments

Impact assessments are evaluations performed to identify and mitigate the risks of various processes or systems. In the context of GDPR, these assessments are important for understanding the potential effects on data protection. The video script lists impact assessments as a necessary process for GDPR compliance.

💡Subject Access Requests

Subject access requests (SARs) are a right granted to individuals under GDPR, allowing them to request access to their personal data held by an organization. The script discusses the process of handling SARs, emphasizing the need for a documented and implemented procedure to respond to such requests.

💡Breach Process

A breach process outlines the steps an organization should take in the event of a data breach. It is a critical component of GDPR compliance, ensuring that organizations can respond effectively to protect data integrity. The script mentions the breach process as one of the processes that need to be documented and reviewed regularly.

💡Process Documentation

Process documentation involves creating written records that describe how a process should be carried out. In the script, it is emphasized that documenting processes is not only about recording them but also about ensuring they are implemented and communicated within the organization.

💡Implementation

Implementation refers to the act of putting a plan, process, or idea into effect. In the context of the video, implementation is key to ensuring that documented processes are actually carried out within an organization, supporting GDPR compliance.

💡Communication

Communication in this context means disseminating information about processes throughout an organization to ensure that all relevant parties are aware and understand their roles. The script highlights the importance of communicating processes to everyone in the organization.

💡Review and Improvement

Review and improvement involve regularly assessing and enhancing processes to ensure they remain effective and compliant. The script stresses the need for ongoing review and improvement of GDPR processes, illustrating the dynamic nature of compliance.

💡Data Protection Officer (DPO)

A Data Protection Officer is a role designated under GDPR to oversee data protection strategies and ensure compliance with data protection regulations. In the script, the DPO is identified as the owner of the subject access request process, highlighting the critical role of this position in GDPR compliance.

Highlights

Introduction to the General Data Protection Regulation (GDPR) compliance processes by Mike Sutherland.

Discussion on various processes required by GDPR, including data mapping, data protection, and impact assessments.

Emphasis on the importance of documenting processes as part of GDPR compliance.

Explanation that merely documenting processes is not enough; they must also be implemented with proper systems.

The necessity of communicating processes to ensure everyone in the organization is aware.

Highlighting the non-static nature of GDPR processes, requiring regular review and improvement.

Introduction of the subject access request process as an example of GDPR documentation.

The importance of assigning a process owner, such as a data protection officer, for accountability.

Describing the purpose of the subject access request process to ensure clarity and understanding.

Detailing the steps involved in managing and logging subject access requests by the help desk.

Mention of sub-processes such as data export, erasure, and correction within the request process.

The significance of recognizing and documenting the completion of the request process by closing the ticket.

Linking processes to relevant policies to maintain a coherent compliance framework.

Documentation of the last update date and version number for process records.

The call to action for continuous improvement and communication of GDPR processes.

Preview of the next topic to be discussed, which is contracts in the context of GDPR.

Closing remarks encouraging simplicity in GDPR compliance.

Transcripts

play00:02

[Music]

play00:03

hello and welcome back once again to our

play00:07

GDP our compliance Chile I'm Mike

play00:09

Sutherland this time we are talking

play00:11

about processes now there are a lot of

play00:16

processes required as part of GDP are

play00:18

things like data mapping data protection

play00:22

impact assessments subjects access

play00:24

requests breach process reviews and

play00:28

we've got some of them listed on this

play00:30

side of the screen but when you're

play00:33

thinking about process and we'll show

play00:35

you one of our documents in a second

play00:37

there are a number of steps you need to

play00:39

consider when putting the process

play00:41

together the first thing we need to do

play00:43

is to actually document the process but

play00:47

it's not just enough to document it you

play00:49

need to implement the process so make

play00:50

sure that the systems are in place to

play00:52

back that up and once you've documented

play00:55

and implemented you then need to

play00:56

communicate that process so that

play00:58

everybody in your organization is aware

play01:00

of that process and like many things in

play01:04

the gdpr it's not just a one-time effort

play01:06

so you need to review that process on a

play01:09

regular basis and make sure that you

play01:11

continue to improve it and when you do

play01:14

improve it you need to document the

play01:16

process as a cycle that goes on and on

play01:18

to keep your processes as good as they

play01:21

can be so let's now take a look at what

play01:24

our process we talked a couple of times

play01:28

ago about subject access requests so

play01:31

just going to show you through our

play01:33

subject - request document so this is

play01:38

our subject access request process

play01:40

document and in line with all our

play01:43

process documents we have a title and we

play01:47

give the processor type now that can be

play01:51

irregular as in this case so we do this

play01:54

process when somebody requests it we

play01:57

have other processes which are on a

play01:59

daily a weekly a monthly schedule so we

play02:02

define the type of process we give it a

play02:05

status whether it's live Draft under

play02:08

review or retired and then importantly

play02:11

we need to give

play02:13

the process an owner so that could be a

play02:17

role and the role to learn the subject

play02:19

to access request process in our cases

play02:21

the data protection officer and also we

play02:24

give that role and that person a name so

play02:27

we know that Mike Savile is responsible

play02:29

for this process now it's important to

play02:32

describe the purpose of the process

play02:34

because we don't want people to think oh

play02:35

well we're not sure why it's needed why

play02:38

we're doing it so in the case of

play02:40

subjects access requests we say that

play02:43

exists to enable individuals to exercise

play02:45

their rights to information and it gives

play02:48

us a standard approach for documenting

play02:50

responding to and fulfilling these

play02:52

requests we then in every process go on

play02:56

to document these steps that are

play02:57

required so there's a series of wreaths

play03:00

of steps and overarching comment that

play03:03

says we manage and we log it by our help

play03:05

desk and then some quite simple steps we

play03:09

don't need to go into very detailed

play03:11

descriptions but we need to get the

play03:12

process steps laid out so receive the

play03:15

tickets send an email response to

play03:18

acknowledge the requests give it a

play03:20

category set an SLA time on the request

play03:23

then there might be sub processes so we

play03:26

don't need to define every single nuance

play03:30

of the sub process here in the request

play03:32

process but we do need to recognize that

play03:34

there's a separate data export process

play03:36

there's a separate data erasure process

play03:38

there's a separate data deletion or

play03:40

correction process and then some other

play03:45

steps before we finally finally get on

play03:48

to closing the ticket and at that point

play03:51

the process is finished it's all

play03:54

important to indicate which policies

play03:58

this process relates to and vice-versa

play04:02

so if you see saw the earlier video on

play04:05

policy you would have seen us referring

play04:07

to process so in this instance there are

play04:11

several policies that would reference

play04:14

this subject access request process and

play04:16

we've listed them in the document here

play04:19

and finally at the footer of the

play04:22

document we've said when it was last

play04:24

updated and in this case the 13th of

play04:26

April and the version number of the

play04:28

document and that gives us a complete

play04:31

view of the process for subject access

play04:34

requests so I hope you found that useful

play04:38

we've got other other processes

play04:41

documented in exactly the same way but

play04:43

just to reiterate you need to document

play04:45

you then need to implement your

play04:47

processes you then need to communicate

play04:49

them tell people about your processes no

play04:52

good having them if you haven't told

play04:53

people and keep reviewing them with a

play04:56

view to keeping them improved or

play04:58

improving them on an ongoing basis so

play05:00

that's it for this time next time we are

play05:03

going to be talking about contracts so

play05:06

until then we hope you find your

play05:08

compliance simple

Rate This

5.0 / 5 (0 votes)

Related Tags
GDPR ComplianceData ProtectionSubject AccessProcess DocumentationData MappingImpact AssessmentBreach ProcessPolicy ReviewCompliance TipsMike SutherlandData Officer