Data protection management
Record, impact assessment and measures in CRISAM®, at your own pace.
Go to the courseThe record of processing activities is maintained, the retention periods are documented somewhere else, and the technical and organizational measures are owned by IT. In an audit, what matters is that you can bring all of this together. CRISAM® connects processing activities, risks, measures and evidence in one shared model.
Legal status: 23 September 2026
The GDPR is Regulation (EU) 2016/679 on the protection of natural persons with regard to the processing of personal data. Among other things, it requires controllers to maintain a record of processing activities, implement appropriate technical and organizational measures, carry out a data protection impact assessment where the risk is high, report breaches and be able to demonstrate compliance at any time.
What sets it apart is the accountability obligation: complying with the requirements is not enough. You must be able to prove that you comply with them.
The deadlines are behind us. What remains are recurring obligations: some apply permanently, others are tied to time limits that only start with a specific event.
As a rule, the record of processing activities under Article 30 must be maintained continuously and kept up to date. Creating it once is not enough.
Where a high risk is likely, Article 35 requires a data protection impact assessment before processing begins.
Article 32 requires appropriate technical and organizational measures and regular testing of their effectiveness.
Under Article 33, a personal data breach must be reported without undue delay and, where feasible, within 72 hours.
Under the accountability obligation in Article 5(2) and Article 24, you must be able to demonstrate compliance on request.
There are no thresholds and no list of sectors. The question is not whether the GDPR applies, but in which role and with how much effort.
Whoever decides on the purposes and means of processing is the controller and bears the obligations under Articles 30, 32, 33 and 35. Whoever processes on behalf of a controller needs a contract with the controller under Article 28. Many companies are both, depending on the processing activity.
Under Article 37 et seq., a data protection officer must be designated, among other cases, by public authorities and bodies, and where the core activities consist of large-scale regular and systematic monitoring or of large-scale processing of special categories of personal data.
Under Article 5(2) and Article 24, controllers must be able to demonstrate compliance with the principles. In a dispute, having acted correctly is not enough. It must also be documented.
The eight obligations are closely linked. A processing activity without a legal basis remains a gap even if the measures are documented.
| Obligation | Basis | What is required | How you map it in CRISAM® |
|---|---|---|---|
| Accountability | Art. 5(2), Art. 24 | Compliance with the principles must be demonstrated, not just achieved | Compliance dashboards show the status of the record, impact assessments and measures. Automated reports and export functions provide the documentation for audits, management and external reviews. |
| Data subject rights | Art. 12 et seq. | Access, rectification, erasure and the other rights must be fulfilled. Article 12 governs procedures and time limits | Access reports for data subject requests are generated directly from the record and do not have to be pieced together again for every request. |
| Processors | Art. 28 | Anyone who engages external service providers to carry out processing needs a written data processing contract | Processors are fully documented, including contract status and audit results. Data transfers to third countries are recorded with safeguards and legal basis. |
| Record of processing activities | Art. 30 | As a rule, controllers maintain a record of all processing activities | Create and maintain a complete record under Article 30, including purpose, legal basis, recipients, retention periods and technical measures. |
| Technical and organizational measures | Art. 32 | Appropriate measures in proportion to the risk, such as pseudonymization and encryption, with regular testing of their effectiveness | Document, manage and assess the measures under Article 32. The link to the ISMS keeps technical and organizational relationships traceable. |
| Breach notification | Art. 33 | Without undue delay and, where feasible, within 72 hours of becoming aware of it, to the supervisory authority, where rights and freedoms may be affected | The notification path, including the persons responsible and the deadlines, is stored in the same model as the affected processing activity. Export functions provide the documentation for the authority. |
| Data protection impact assessment | Art. 35 | Required where a high risk is likely, for example with automated decisions, large-scale processing of special categories or systematic monitoring of publicly accessible areas | CRISAM® supports threshold analyses, risk assessments and the creation of complete reports under Article 35. Risks are assessed in a structured way and documented traceably. |
| Data protection officer | Art. 37 et seq. | Mandatory for public authorities and bodies, and for large-scale systematic monitoring or large-scale processing of special categories | Responsibilities are stored for each processing activity. Integrated workflows ensure clear ownership, deadline control and transparency on the implementation status. |
From the record of processing activities to the reports a supervisory authority requests.
Purpose, legal basis, data categories, recipients and time limits: you capture all the information required by Article 30 in a structured form instead of a spreadsheet.
The record of processing activities presents the content required by Art. 30 GDPR: description, legal basis, purpose, retention period and erasure deadline, data categories, recipients and processors for each processing activity.
| Name | Category | Agreement concluded |
|---|---|---|
| Software development processor | Cloud | ✓ |
| Cloud office software | Cloud | ✓ |
| HR service provider | Service provider | ✓ |
The threshold analysis shows whether an impact assessment is needed. If it is, the processing activity is assessed in a structured way and documented traceably.
This chapter gives you an overview of which processing activities require a data protection impact assessment and for which one has been carried out.
| Name | Art. 35 GDPR | G29 | Blacklist | Whitelist | Other high risk | DPIA required | DPIA carried out | Number of risks |
|---|---|---|---|---|---|---|---|---|
| Applicant management | 1 | |||||||
| Performance appraisal | ✓ | ✓ | ✓ | ✓ | ✓ | 1 | ||
| Customer management (CRM) | 1 | |||||||
| Wage accounting | 1 | |||||||
| Customer loyalty program | 0 | |||||||
| Payroll | ✓ | ✓ | ✓ | 1 | ||||
| HR administration | 0 | |||||||
| Social media use | ✓ | ✓ | ✓ | ✓ | ✓ | 2 | ||
| Site video surveillance | 0 | |||||||
| Site access control | 0 |
The technical and organizational measures are linked directly to the processing activity they apply to, instead of sitting as an annex in the contract folder. They are also linked to the objects in the ISMS.
| Owner | Measures |
|---|---|
| unassigned | 149 |
| Data protection | 27 |
| IT operations | 16 |
| HR, facility | 5 |
| Name | Category | Owner | Priority | Status |
|---|---|---|---|---|
| ⚲ | ⚲ | ⚲ | ⚲ | ⚲ |
| Access logging | Organizational and technical | IT operations | High | In progress |
| Role-based access rights | Organizational and technical | IT operations | Medium | New |
| Anonymization | Technical | Data protection | Low | New |
| Data processing agreement | Organizational | Medium | New | |
| Automatic security updates | Technical | IT operations | Medium | New |
| Visitor policy | Organizational | Facility | Medium | New |
| Clean desk policy | Organizational | HR | Medium | Not started |
| Clear screen policy | Organizational and technical | IT operations | Medium | Not started |
| Data Loss Prevention | Technical | Data protection | Medium | New |
Every service provider with access to personal data needs a contract. For transfers to third countries, safeguards and the legal basis are recorded as well.
| Objects | Building block | Status | Deviation |
|---|---|---|---|
| Marketing processor | Processor | New | Incompletely assessed |
| Software development processor | Processor | In progress | Medium deviation |
| Applicant management | Processing activity | In progress | Incompletely assessed |
| Data protection management system (ISO 27701) | Data protection management system | In progress | Major deviation |
| Data protection coordination | Data protection coordinator | In progress | Major deviation |
| Object | No. | Audit question | Fulfillment | Deviation |
|---|---|---|---|---|
| Marketing processor | 10 | How have responsibilities, tasks and obligations been arranged between the controller and the processor? | Empty | No value |
| Software development processor | 30 | How are the security, reliability and qualifications of the processor verified before engagement? | D | Medium deviation |
| Software development processor | 40 | How are the security, reliability and qualifications of the processor reviewed on a recurring basis? | B | Fulfilled |
The retention period and erasure deadline are stored for each processing activity. The report lists them all together, instead of keeping them in a separate erasure concept.
This chapter lists all selected processing activities alphabetically, including retention period and erasure deadline.
At the end come the reports that a supervisory authority or a customer requests. They are generated directly from the model instead of being pieced together from scattered folders.
The following list provides an overview of all measures. The measures are grouped by main category and sorted by priority and name.
| Priority | Measure | Owner | Ongoing | Status | Category |
|---|---|---|---|---|---|
| Medium | Ban on private devices (BYOD policy) | - | New | Organizational | |
| Medium | Visitor policy | Facility | New | Organizational | |
| Medium | Clean desk policy | HR | ✓ | Not started | Organizational |
| Medium | Clear screen policy | IT operations | ✓ | Not started | Organizational and technical |
| Protection against shoulder surfing | - | In progress | Organizational |
| Priority | Measure | Owner | Ongoing | Status | Category |
|---|---|---|---|---|---|
| Regular review of security measures | - | New | Organizational | ||
| Regular IT security audits | - | New | Organizational | ||
| Security certifications | - | New | Organizational |
| Priority | Measure | Owner | Ongoing | Status | Category |
|---|---|---|---|---|---|
| Regular data protection training | - | New | Organizational |
Record, impact assessments, data subject requests, reporting.
Accountability, resources, approval of high-risk processing activities.
Technical measures, logging, erasure, link to the ISMS.
Data processing contracts, information on processing activities in day-to-day business.
Data protection and information security often require the same measures, just from different angles. CRISAM® integrates data protection into the GRC platform so that risks, controls, measures and compliance requirements are considered together.
The link to the ISMS ensures that technical and organizational relationships remain traceable at all times and do not have to be maintained twice.
In addition to the GDPR, international standards such as ISO 27701 and ISO 29151 can be covered and evaluated.
If an AI system processes personal data, it belongs in both registers. In CRISAM®, the two objects are linked to each other.
Automated reports on the record, impact assessments, measures and data subject requests, plus export functions for audits, management and external reviews.
A security incident can trigger both notification obligations at the same time. Under Article 33, the GDPR requires notification to the data protection authority without undue delay and, where feasible, within 72 hours. NIS2 requires an early warning within 24 hours and a full notification within 72 hours to a different body. If you know only one of the two paths, you risk notifying too late or notifying the wrong body.
| Criterion | GDPR | NIS2 |
|---|---|---|
| Legal act | Regulation (EU) 2016/679, directly applicable | Directive (EU) 2022/2555, via national law |
| Protected interest | Rights and freedoms of natural persons | Functioning of essential and important entities |
| Who is affected | Any body that processes personal data | Entities from 18 sectors, medium-sized and larger |
| Notification trigger | Personal data breach | Significant security incident, even without personal data |
| Deadline | Without undue delay and, where feasible, within 72 hours | Early warning within 24 hours, full notification within 72 hours |
| Recipient | Competent data protection authority | In Germany the BSI portal, in Austria the NIS2 reporting platform of CERT.at |
| Mapping in CRISAM® | Processing activity, risk, measures and notification path in the DPMS | Incident, classification and notification chain in the ISMS |
A customer system encrypted after an attack is both: a significant security incident and a personal data breach. In CRISAM®, the incident is linked to the same objects as the affected processing activities. This way, both notification paths can be served from a single data collection. What applies to NIS2 is covered on its own page. For an overview of all frameworks that CRISAM® covers, see Standards and frameworks.
A self-study course, an instructor-led training and the associated content catalog.
Record, impact assessment and measures in CRISAM®, at your own pace.
Go to the courseRisk management and data protection management working together, led by an instructor.
View datesThe content catalog that forms the basis for your assessments in CRISAM®. Plus all dates, courses and product documentation at a glance.
AcademyDownload centerThe first step depends on where you stand today.
You start with the import. Purpose, legal basis, recipients and time limits are carried over. What used to sit in spreadsheet columns is then stored in the system as an object you can evaluate.
It starts with the threshold analysis. It shows which processing activities need an impact assessment. The result is structured assessments instead of free-text documents.
For this you need the CRISAM® GRC Platform and the CRISAM® DPMS Module. In the demo, we discuss your starting point and show what you already have in place.
The GDPR is Regulation (EU) 2016/679 on the protection of natural persons with regard to the processing of personal data. Among other things, it requires controllers to maintain a record of processing activities, implement appropriate technical and organizational measures, carry out a data protection impact assessment where the risk is high, report breaches and be able to demonstrate compliance at any time.
The data protection authority lists, among others: a record of processing activities under Article 30, appropriate technical and organizational measures under Article 32, a data protection impact assessment under Article 35 where the risk is high, the notification of breaches under Article 33, the designation of a data protection officer under Article 37 et seq., the fulfillment of data subject rights under Article 12 et seq., a contract with processors under Article 28, and accountability under Article 5(2) and Article 24.
Under Article 33, without undue delay and, where feasible, within 72 hours of becoming aware of the breach, where the rights and freedoms of data subjects may be affected. The notification goes to the competent data protection authority.
Under Article 35, for processing that is likely to result in a high risk to the rights and freedoms of natural persons. As examples, the data protection authority names automated decision-making, large-scale processing of special categories of personal data and systematic monitoring of publicly accessible areas. In addition, there are national blacklists and whitelists issued by the supervisory authorities.
A security incident can trigger both notification obligations at the same time. Under Article 33, the GDPR requires notification to the data protection authority without undue delay and, where feasible, within 72 hours. NIS2 requires an early warning within 24 hours and a full notification within 72 hours to a different body. If you know only one of the two paths, you risk notifying too late or notifying the wrong body.
Under Article 5(2) and Article 24, controllers must be able to demonstrate compliance with the principles. Complying with the requirements is not enough: compliance must be verifiably documented. In an audit, what counts above all is therefore whether compliance can be proven.
What matters is whether the record, risks, measures and evidence are linked in one shared model or sit in separate files. CRISAM® maintains a complete record under Article 30, including purpose, legal basis, recipients, retention periods and technical measures, supports threshold analyses and impact assessments under Article 35, and documents processors together with contract status and audit results.
Yes, and that avoids duplicate maintenance. The technical and organizational measures under Article 32 are largely the same ones an information security management system requires anyway. The link to the ISMS ensures that technical and organizational relationships remain traceable at all times. In addition to the GDPR, international standards such as ISO 27701 and ISO 29151 can be covered and evaluated.
The regulatory information on this page comes from the following sources.
The information reflects the status of the sources listed as of the review date stated above.
In the demo, we walk through your case: record, threshold analysis, measures, processors and the finished reports.
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Embedded Content. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Meetings. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information