Content library
TISAX: Information security
9.6.2: Managment of data protection incidents

Requirement description

Objective: The objective of processing data protection incidents is to ensure that possible damage to the data subjects is limited and that a recurrence is prevented. In addition, the legally required documentation and, if necessary, timely reporting to the supervisory authority must be ensured.

Requirements (must): Data protection incidents (e.g. unauthorized access to personal data) are processed in a timely manner.
The requirements from 1.6 of the information security questionnaire also take into account data protection incidents or, alternatively, there is an emergency plan for dealing with data protection incidents.
In addition, procedures are established and documented to ensure the following aspects:
- immediate notification to the respective responsible person, as far as his order is affected
- Documentation of the incident handling activities
- Training of employees on the defined measures/processes
- Support of the respective controller in the processing of data protection incidents

How to fill the requirement

TISAX: Information security

9.6.2: Managment of data protection incidents

Task name
Priority
Status
Theme
Policy
Other requirements
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
ISO 27001
16.1.5: Response to information security incidents
ISO 27001
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.
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
ISO 27001
TSU-14: Tietoturvaloukkaukset
Julkri
5.34: Privacy and protection of PII
ISO 27001
66: Tietoturvaloukkausten hallinta
Digiturvan kokonaiskuvapalvelu
P6.5: Notification of unauthorized disclosure of personal information from third parties
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.

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
ISO 27001
16.1.7: Collection of evidence
ISO 27001
5.26: Response to information security incidents
ISO 27001
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
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
ISO 27001
16.1.5: Response to information security incidents
ISO 27001
RS.CO-3: Information sharing
NIST
66: Tietoturvaloukkausten hallinta
Digiturvan kokonaiskuvapalvelu
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 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
17
requirements

Examples of other requirements this task affects

A.10.1: Notification of a data breach involving PII
ISO 27018
DE.CM-6: External service provider activity monitoring
NIST
5.23: Information security for use of cloud services
ISO 27001
P6.5: Notification of unauthorized disclosure of personal information from third parties
SOC 2
21.2.b (incidents): Incident management
NIS2
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.

Tasks included in the policy

Task name
Priority
Status
Theme
Policy
Other requirements
No items found.

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.
38: Kiberuzbrukumu attiecināšana
NIS2 Latvia
1.1 (MIL2): Manage IT and OT Asset Inventory
C2M2
1.1 (MIL3): Manage IT and OT Asset Inventory
C2M2
1.1.1: Availability of information security policies
TISAX
1.1.1: Identify the organisation’s strategy and priorities
NSM ICT-SP
1.1.2: Identify the organisation’s structures and processes for security management
NSM ICT-SP
1.1.3: Identify the organisation’s processes for ICT risk management
NSM ICT-SP
1.1.4: Identify the organisation’s tolerances for ICT risk
NSM ICT-SP
1.1.5: Identify the organisation’s deliverables, information systems and supporting ICT functions
NSM ICT-SP
1.1.6: Identify information processing and data flow
NSM ICT-SP
1.1: Establish and Maintain Detailed Enterprise Asset Inventory
CIS 18
1.2 (MIL2): Manage Information Asset Inventory
C2M2
1.2 (MIL3): Manage Information Asset Inventory
C2M2
1.2.1: Establish a process to identify devices and software in use at the organisation
NSM ICT-SP
1.2.1: Scope of Information Security management
TISAX
1.2.2: Establish organisational guidelines for approved devices and software
NSM ICT-SP
1.2.2: Information Security Responsibilities
TISAX
1.2.3: Identify devices in use at the organisation
NSM ICT-SP
1.2.3: Information Security requirements in projects
TISAX
1.2.4: Definition of responsibilities with service providers
TISAX
1.2.4: Identify the software in use at the organisation
NSM ICT-SP
1.2: Address Unauthorized Assets
CIS 18
1.2: Manage Information Asset Inventory
C2M2
1.3 (MIL2): Manage IT and OT Asset Configuration
C2M2
1.3 (MIL3): Manage IT and OT Asset Configuration
C2M2
1.3.1: Identification of information assets
TISAX
1.3.1: Identify the users of the information systems
NSM ICT-SP
1.3.2: Classification of information assets
TISAX
1.3.2: Identify and define the different user categories
NSM ICT-SP
1.3.3: Identify roles and responsibilities linked especially to ICT security
NSM ICT-SP
1.3.3: Use of approved external IT services
TISAX
1.3.4: Use of approved software
TISAX
1.3: Manage IT and OT Asset Configuration
C2M2
1.3: Utilize an Active Discovery Tool
CIS 18
1.4 (MIL2): Manage Changes to IT and OT Assets
C2M2
1.4 (MIL3): Manage Changes to IT and OT Assets
C2M2
1.4.1: Management of Information Security Risks
TISAX
1.4: Manage Changes to IT and OT Assets
C2M2
1.4: Use Dynamic Host Configuration Protocol (DHCP) Logging to Update Enterprise Asset Inventory
CIS 18
1.5 (MIL1): Management Activities for the ASSET domain
C2M2
1.5 (MIL2): Management Activities for the ASSET domain
C2M2
1.5 (MIL3): Management Activities for the ASSET domain
C2M2
1.5.1: Assessment of policies and requirements
TISAX
1.5.2: External review of ISMS
TISAX
1.5: Management Activities for the ASSET domain
C2M2
1.5: Use a Passive Asset Discovery Tool
CIS 18
1.6.1: Reporting of security events
TISAX
1.6.2: Management of reported events
TISAX
1.6.3: Crisis preparedness
TISAX
10 §: Johdon vastuu
Kyberturvallisuuslaki
10. Processing of personal data relating to criminal convictions and offences
GDPR
10.1 (MIL2): Establish Cybersecurity Program Strategy
C2M2
10.1 (MIL3): Establish Cybersecurity Program Strategy
C2M2
10.1.1: Policy on the use of cryptographic controls
ISO 27001
10.1.2: Key management
ISO 27001
10.1.2: Key management
ISO 27017
10.1: Cryptographic controls
ISO 27001
10.1: Cryptographic controls
ISO 27017
10.1: Deploy and Maintain Anti-Malware Software
CIS 18
10.1: Establish Cybersecurity Program Strategy
C2M2
10.1: Non-conformity and corrective action
ISO 27001
10.2 (MIL2): Establish and Maintain Cybersecurity Program
C2M2
10.2 (MIL3): Establish and Maintain Cybersecurity Program
C2M2
10.2: Establish and Maintain Cybersecurity Program
C2M2
10.2: Configure Automatic Anti-Malware Signature Updates
CIS 18
10.2: Continuous improvement
ISO 27001
10.3 (MIL1): Management Activities for the PROGRAM domain
C2M2
10.3 (MIL2): Management Activities for the PROGRAM domain
C2M2
10.3 (MIL3): Management Activities for the PROGRAM domain
C2M2
10.3: Disable Autorun and Autoplay for Removable Media
CIS 18
10.3: Management Activities for the PROGRAM domain
C2M2
10.4: Configure Automatic Anti-Malware Scanning of Removable Media
CIS 18
10.5: Enable Anti-Exploitation Features
CIS 18
10.6: Centrally Manage Anti-Malware Software
CIS 18
10.7: Use Behavior-Based Anti-Malware Software
CIS 18
10: Cryptography
ISO 27001
10: Cryptography
ISO 27017
10: Cybersecurity Program Management (PROGRAM)
C2M2
10: Prosessi väärinkäytöksiin reagoimiseksi
Digiturvan kokonaiskuvapalvelu
11 §: Poikkeamailmoitukset viranomaiselle
Kyberturvallisuuslaki
11. Processing which does not require identification
GDPR
11.1.1: Physical security perimeter
ISO 27001
11.1.2: Physical entry controls
ISO 27001
11.1.3: Securing offices, rooms and facilities
ISO 27001
11.1.4: Protecting against external and environmental threats
ISO 27001
11.1.5: Working in secure areas
ISO 27001
11.1.6: Delivery and loading areas
ISO 27001
11.1: Establish and Maintain a Data Recovery Process
CIS 18
11.1: Secure areas
ISO 27001
11.2.1: Equipment siting and protection
ISO 27001
11.2.2: Supporting utilities
ISO 27001
11.2.3: Cabling security
ISO 27001
11.2.4: Equipment maintenance
ISO 27001
11.2.5: Removal of assets
ISO 27001
11.2.6: Security of equipment and assets off-premises
ISO 27001
11.2.7: Secure disposal or re-use of equipment
ISO 27001
11.2.7: Secure disposal or re-use of equipment
ISO 27017
11.2.8: Unattended user equipment
ISO 27001
11.2.9: Clear desk and clear screen policy
ISO 27001
11.2: Equipment
ISO 27001