Privacy by design and how to do it well -TEISS® : Cracking Cyber Security

Data by design - protecting from the start

Information security / Privacy by design and how to do it well

Privacy by design and how to do it well

In the second of a 2-part installment, Hadi Hosn, Director of Cyber Security Solutions EMEA at SecureWorks, sets out strategies for integrating privacy by design into processes and applications.

What should businesses think about when creating processes or apps?

When it comes to integrating privacy by design into new processes and applications the business needs to involve data protection representatives early in the process to ensure data protection and security requirements are defined and integrated into the project.

Some of the key data protection considerations businesses should think about revolve around the following 6 domains:

  1. Governance & Oversight: ensuring the right data protection clauses are in place with third parties acting as data processors in the new application or process.
  2. People: Ensuring all staff members who may handle personal data in the course of their duties are adequately trained. This will avoid potentially costly and damaging legal action being taken should someone’s data be mishandled. Defining roles and responsibilities for handling data breaches and collecting information that will be shared with the regulator in the event of a breach.
  3. Process: defining data handling processes and data breach notification processes in line with GDPR requirements. Sharing the processes with the teams handling the data on a daily basis to ensure they are followed and measured.
  4. Communication: defining the communication plan and mechanisms, including who is responsible for communicating with customers and regulators and when this communication is required.
  5. Data: ensuring data is only kept for as long as required by the business. Covering data discovery, data lifecycle and documentation of data flows.
  6. Security: ensuring the security teams are involved in the design phase of the project to implement and integrate the necessary controls to protect the personal data.

Also of interest: 9 surprising things that are illegal under GDPR

What steps should businesses implement for privacy by design by default?

One of the key activities businesses should implement for data protection by design is the Data Protection Impact Assessment (DPIA) methodology and approach.

The DPIA is a risk assessment framework with a data protection and privacy focus. It is required for all new IT systems, third parties, business processes, teams and activities organisations build to process or handle personal data in scope of GDPR. By carrying out a DPIA, the data protection representatives can identify the data protection risks in a new system or project, and define mitigating plans to minimise those risks to an acceptable level. It can also be used to design more efficient and effective processes for handling personal data.

The steps required to complete a full DPIA include:

Step 1 – identify if a DPIA is needed:

As a starting point, the organisation needs to answer some screening questions to identify if a project has potential impact on data protection and privacy. Questions include:

  1. Are new technologies going to be implemented by the project to process personal data in scope of GDPR?
  2. Will the project involve automated data processing and decision making or profiling?
  3. Is a large volume of personal data being processed or planned to be processed by the project?
  4. Is data being transferred outside the EU?
  5. Will personal data be processed in ways which individuals might not reasonably expect?

Step 2 – complete the DPIA template for the project

The DPIA will cover the following domains which should be facilitated by the data protection representative and completed by the project teams.

  1. Personal Data workflow specifics
  2. Description of processing
  3. Information owner / risk owner
  4. Is the organisation a data controller or data processor?
  5. How is the data collected?
  6. Details of the systems containing personal data
  7. Who has access to the data?
  8. Is the data shared with third parties or other teams?
  9. Approximate volume of data processed
  10. Types of data (name, address, DOB, etc.)
  11. Threats and Risks
  12. What could happen as a result of a failure of the process ?
  13. What are the vulnerabilities / weaknesses in the system / process?
  14. What is the likelihood of the threat?
  15. What is the impact to the organisation?
  16. Risk Mitigation Recommendations
  17. What actions can the organisation implement to reduce the threats and risks identified?
  18. Who owns the action?
  19. When does the action need to be completed by?
  20. Document the findings and recommendations
  21. Feed the results into the solution

Step 3 – Regularly review the actions and owners

Conduct regular reviews of the actions documented in the DPIA and ensure owners are completing their responsibilities. Also review the risks and overall risk profile is still within acceptable risk tolerance for the organisation.

Also of interest: Welcome to society 5.0; integrating man and machine

Comments

Get the latest cyber news in your inbox

Join our community of cyber professionals today!