Content library
Data breach management
Management and documentation of data breaches

Other tasks from the same security theme

Task name
Priority
Status
Theme
Policy
Other requirements
Management and documentation of data breaches
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Incident management
Data breach management
11
requirements

Examples of other requirements this task affects

18.1.4: Privacy and protection of personally identifiable information
ISO27 Full
TSU-14: Tietoturvaloukkaukset
Julkri
5.34: Privacy and protection of PII
ISO27k1 Full
66: Tietoturvaloukkausten hallinta
Sec overview
P6.3: Record of unauthorized disclosures of personal information
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Management and documentation of data breaches
1. Task description

The organization must document all personal data breaches and their consequences and the corrective actions taken, regardless of the action ultimately resulting from the breach.

Failure to comply with the documentation obligation or notification is contrary to GDPR and may lead to sanctions defined on the regulation.

Reporting personal data breaches to authorities / data subjects
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Incident management
Data breach management
21
requirements

Examples of other requirements this task affects

33. Notification of a personal data breach to the supervisory authority
GDPR
34. Communication of a personal data breach to the data subject
GDPR
6.1.3: Contact with authorities
ISO27 Full
16.1.5: Response to information security incidents
ISO27 Full
RS.CO-2: Incident reporting
NIST
See all related requirements and other information from tasks own page.
Go to >
Reporting personal data breaches to authorities / data subjects
1. Task description

A personal data breach must be reported to the supervisory authority if the breach may pose a risk to data subjects rights and freedoms. Data subjects, on the other hand, must be informed if the breach is likely to pose a high risk to their rights and freedoms. For example, registrants may take steps to reduce the adverse effect (e.g. by closing their credit card).

The notification must include the following information:

  • a clear description of the personal data breach
  • the name and contact details of the data protection officer or other contact point from which further information can be obtained
  • the likely consequences of the personal data breach
  • the measures proposed or already taken by the controller; where appropriate, measures to mitigate possible adverse effects.
Process for detecting and reporting security breaches related to the supply chain
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Incident management
Data breach management
15
requirements

Examples of other requirements this task affects

DE.CM-6: External service provider activity monitoring
NIST
A.10.1: Notification of a data breach involving PII
ISO 27018
5.23: Information security for use of cloud services
ISO27k1 Full
21.2.b (incidents): Incident management
NIS2
P6.3: Record of unauthorized disclosures of personal information
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Process for detecting and reporting security breaches related to the supply chain
1. Task description

The organization shall define the procedures for reporting security breaches in the supply chain. The process must take into account all kinds of roles in the supply chain, whether we are the customer of the end product or one supplier in the chain.

Policies shall take into account agreements with partners and customers and their commitments regarding the reporting obligations of both parties.

Detailed assessment of the risk of data breach for data subjects
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Incident management
Data breach management
10
requirements

Examples of other requirements this task affects

34. Communication of a personal data breach to the data subject
GDPR
6.1.3: Contact with authorities
ISO27 Full
16.1.5: Response to information security incidents
ISO27 Full
RS.CO-3: Information sharing
NIST
66: Tietoturvaloukkausten hallinta
Sec overview
See all related requirements and other information from tasks own page.
Go to >
Detailed assessment of the risk of data breach for data subjects
1. Task description

The controller must assess the risk of the personal data breach to the data subjects. The assessment must take into account, for example, the following:

  • How likely is it that the data will be used to cause harm?
  • What harm could the data be used for (e.g. identity theft, fraud, psychological distress, humiliation or reputational damage)?
  • Nature, sensitivity and amount of personal data
  • How easy it is to identify the registrant using the data?
  • Are there many children or otherwise vulnerable people among the registrants?

The risk assessment affects the urgency and scope of reporting a breach.

Process for initiating data breach treatment
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Incident management
Data breach management
9
requirements

Examples of other requirements this task affects

24. Responsibility of the controller
GDPR
32. Security of processing
GDPR
16.1.5: Response to information security incidents
ISO27 Full
16.1.7: Collection of evidence
ISO27 Full
5.26: Response to information security incidents
ISO27k1 Full
See all related requirements and other information from tasks own page.
Go to >
Process for initiating data breach treatment
1. Task description

Our organization has pre-defined procedures through which the detected security breach will be addressed. The process may include e.g. the following things:

  • who are part of a team that is ready to respond to breaches
  • how and along what channel the entire team is immediately notified of the breach
  • the team determines the severity (low, medium, high) of the breach based on predefined criteria
  • the breach management is continued with a larger group according to the severity level

Universal cyber compliance language model: Comply with confidence and least effort

In Cyberday, all frameworks’ requirements are mapped into universal tasks, so you achieve multi-framework compliance effortlessly.

Security frameworks tend to share the common core. All frameworks cover basic topics like risk management, backup, malware, personnel awareness or access management in their respective sections.
Cyberday’s universal cyber security language technology creates you a single security plan and ensures you implement the common parts of frameworks just once. You focus on implementing your plan, we automate the compliance part - for current and upcoming frameworks.
Start your free trial
Get to know Cyberday
Start your free trial
Cyberday is your all-in-one solution for building a secure and compliant organization. Whether you're setting up a cyber security plan, evaluating policies, implementing tasks, or generating automated reports, Cyberday simplifies the entire process.
With AI-driven insights and a user-friendly interface, it's easier than ever to stay ahead of compliance requirements and focus on continuous improvement.
Clear framework compliance plans
Activate relevant frameworks and turn them into actionable policies tailored to your needs.
Credible reports to proof your compliance
Use guided tasks to ensure secure implementations and create professional reports with just a few clicks.
AI-powered improvement suggestions
Focus on the most impactful improvements in your compliance with help from Cyberday AI.