Crisam Logo
  • CRISAM®
    CRISAM®
    • What is CRISAM®?
    • Method
    • Content
    • Customers
    • Academy
    • Webinars
    • Events
  • Areas of application
    Areas of application
    • Information Security Management
    • Integrated Risk Management
    • ESG
    • CRISAM® AI
    • Data Protection Management
    • Audit Management
    • Compliance Management
    • Business Continuity Management
    • Tax Compliance Management System
    • Project Risk Management
    • Legal Register
    • Conflicts of Interest Software
    • CRISAM® Legal Hold Software
  • Industries
    Industries
    • Automotive
    • Energy
    • Manufacturing
    • Financial Services
    • Retail
    • Real Estate & Construction
    • Healthcare
    • Broadcasting & Telecommunications
    • Technology
    • Transport & Logistics
  • More
    More
    • Download Center
    • CRISAM® Academy
    • Webinars
    • News
    • Jobs
    • CRISAM® Partners
    • Trust Center
    • Contact
  • en
    • en-gb
    • de
Request
  • Language
    • en-gb
    • de
  • CRISAM®
    • What is CRISAM®?
    • Method
    • Content
    • Customers
    • Academy
    • Webinars
    • Events
  • Areas of application
    • Information Security Management
    • Integrated Risk Management
    • ESG
    • CRISAM® AI
    • Data Protection Management
    • Audit Management
    • Compliance Management
    • Business Continuity Management
    • Tax Compliance Management System
    • Project Risk Management
    • Legal Register
    • Conflicts of Interest Software
    • CRISAM® Legal Hold Software
  • Industries
    • Automotive
    • Energy
    • Manufacturing
    • Financial Services
    • Retail
    • Real Estate & Construction
    • Healthcare
    • Broadcasting & Telecommunications
    • Technology
    • Transport & Logistics
  • More
    • Download Center
    • CRISAM® Academy
    • Webinars
    • News
    • Jobs
    • CRISAM® Partners
    • Trust Center
    • Contact
  • Request
Quick answer Rhythm Who is affected Obligations Implementation Comparison Knowledge Getting started FAQ
Regulations and frameworks

Implementing the GDPR: from the record of processing activities to audit-ready evidence

The 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

Book a demo View obligations
CRISAM® Compliance ReportSample values
☰Risk AG/ ISMS and DPMS sample project↷?

Overview

GDPR
Chapter II Principles
43 %
Chapter IV Controller and processor
45 %
Chapter V Transfers to third countries or international organisations
28 %
Chapter III Rights of the data subject
45 %
0 %20 %40 %60 %80 %100 %
Target 80%
Risk AGCOMPLIANCE REPORTPage 2
Quick answer

What is the GDPR?

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.

Legal actRegulation (EU) 2016/679
Adopted on27 April 2016
SupervisionData protection authorities of the Member States
Territorial scopeEU, directly applicable
The rhythm

The GDPR is not a project with an end date

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.

Ongoing

Maintain the record

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.

Before processing

Impact assessment

Where a high risk is likely, Article 35 requires a data protection impact assessment before processing begins.

Regularly

Test effectiveness

Article 32 requires appropriate technical and organizational measures and regular testing of their effectiveness.

Within 72 hours

Report a breach

Under Article 33, a personal data breach must be reported without undue delay and, where feasible, within 72 hours.

At any time

Be able to demonstrate

Under the accountability obligation in Article 5(2) and Article 24, you must be able to demonstrate compliance on request.

Scope

Anyone who processes personal data is affected

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.

Typical triggers for a management system

  • The record has become too extensive for a spreadsheet
  • A supervisory authority asks questions, and the documents are spread across several repositories
  • A customer requires evidence of your measures in the data processing agreement
  • Data subject requests come in regularly, and the answers are compiled from scratch every time
  • The group mandates a uniform approach across all entities
  • Data protection and information security maintain the same measures twice

Controller or processor

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.

When a data protection officer is required

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.

The accountability obligation shifts the burden of proof

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.

Obligations

What the GDPR requires of controllers

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.
Implementation

Implementing the GDPR, step by step

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.

CRISAM® Record of Processing Activities ReportSample values
☰Risk AG/ ISMS and DPMS sample project↷?

Record of processing activities

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.

Applicant management
DescriptionHandling of applications, running of selection procedures, communication with applicants and documentation of the application process.
Legal basisConsent, legal obligation, contract
PurposeManaging applications and selecting suitable candidates
Retention period6 months after the procedure ends, up to 1 year if kept on file with consent
Erasure deadlineAfter the retention period ends
Type of processingElectronic, paper file
Data subjectsApplicants (HR)
Profiling
Data applicationsApplicant portal, office software, telephony
Processors
NameCategoryAgreement concluded
Software development processorCloud✓
Cloud office softwareCloud✓
HR service providerService provider✓
Risk AGRECORD OF PROCESSING ACTIVITIESPage 5

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.

CRISAM® Threshold AnalysisSample values
☰Risk AG/ ISMS and DPMS sample project↷?

Processing activities: threshold analysis

This chapter gives you an overview of which processing activities require a data protection impact assessment and for which one has been carried out.

NameArt. 35 GDPRG29BlacklistWhitelistOther high riskDPIA requiredDPIA carried outNumber of risks
Applicant management1
Performance appraisal✓✓✓✓✓1
Customer management (CRM)1
Wage accounting1
Customer loyalty program0
Payroll✓✓✓1
HR administration0
Social media use✓✓✓✓✓2
Site video surveillance0
Site access control0
Risk AGTHRESHOLD ANALYSIS AND DPIAPage 5

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.

CRISAM® MeasuresSample values
☰Risk AG/ ISMS and DPMS sample project↷?
OwnerMeasures
unassigned149
Data protection27
IT operations16
HR, facility5
Status
  • New158
  • Not started12
  • Approved9
  • In progress7
  • Not approved7
  • Deferred4
Category
  • Technical78
  • Organizational61
  • Org. and tech.58
NameCategoryOwnerPriorityStatus
⚲⚲⚲⚲⚲
Access loggingOrganizational and technicalIT operationsHigh In progress
Role-based access rightsOrganizational and technicalIT operationsMedium New
AnonymizationTechnicalData protectionLowNew
Data processing agreementOrganizationalMedium New
Automatic security updatesTechnicalIT operationsMedium New
Visitor policyOrganizationalFacilityMedium New
Clean desk policyOrganizationalHRMedium Not started
Clear screen policyOrganizational and technicalIT operationsMedium Not started
Data Loss PreventionTechnicalData protectionMedium New
Count = 197

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.

CRISAM® Audit Question AssessmentSample values
☰Risk AG/ ISMS and DPMS sample project↷?
OverviewHelp
Overview of audit question deviations
  • No value91.23%
  • Fulfilled3.84%
  • Low deviation2.33%
  • Medium deviation1.37%
  • Exceeded0.68%
  • High deviation0.55%
Object deviations
ObjectsBuilding blockStatusDeviation
Marketing processorProcessorNewIncompletely assessed
Software development processorProcessorIn progressMedium deviation
Applicant managementProcessing activityIn progressIncompletely assessed
Data protection management system (ISO 27701)Data protection management systemIn progressMajor deviation
Data protection coordinationData protection coordinatorIn progressMajor deviation
Objects and audit question fulfillment
ObjectNo.Audit questionFulfillmentDeviation
Marketing processor10How have responsibilities, tasks and obligations been arranged between the controller and the processor?EmptyNo value
Software development processor30How are the security, reliability and qualifications of the processor verified before engagement?DMedium deviation
Software development processor40How are the security, reliability and qualifications of the processor reviewed on a recurring basis?BFulfilled
Count = 730

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.

CRISAM® Record of Processing Activities ReportSample values
☰Risk AG/ ISMS and DPMS sample project↷?

Retention periods

This chapter lists all selected processing activities alphabetically, including retention period and erasure deadline.

Operation and support of a contract management system (SaaS)
Retention periodAfter the engagement ends, the data is erased or returned as instructed by the controller, unless statutory retention obligations apply.
Erasure deadlineAfter the engagement ends, as instructed by the controller.
Performance appraisal
Retention period1 year
Erasure deadlineAfter the retention period ends
Applicant management
Retention period6+1 months (Austrian Equal Treatment Act), a further 1 year if kept on file with consent. In an ongoing employment relationship, until the employee leaves.
Erasure deadlineAfter the retention period ends
External payroll accounting for clients
Retention periodTax-relevant data: 7 years under Section 132 of the Austrian Federal Fiscal Code (BAO) and the Austrian Commercial Code (UGB). Social security records: 7 years. Working time records: 2 years.
Erasure deadlineErasure or anonymization as soon as the data is no longer needed for payroll and no statutory retention obligations remain.
Risk AGRECORD OF PROCESSING ACTIVITIESPage 7

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.

CRISAM® Technical and Organizational Measures ReportSample values
☰Risk AG/ ISMS and DPMS sample project↷?

Overview of measures

The following list provides an overview of all measures. The measures are grouped by main category and sorted by priority and name.

Workplace security
PriorityMeasureOwnerOngoingStatusCategory
MediumBan on private devices (BYOD policy)-NewOrganizational
MediumVisitor policyFacilityNewOrganizational
MediumClean desk policyHR✓Not startedOrganizational
MediumClear screen policyIT operations✓Not startedOrganizational and technical
Protection against shoulder surfing-In progressOrganizational
Audit and compliance
PriorityMeasureOwnerOngoingStatusCategory
Regular review of security measures-NewOrganizational
Regular IT security audits-NewOrganizational
Security certifications-NewOrganizational
Awareness and compliance
PriorityMeasureOwnerOngoingStatusCategory
Regular data protection training-NewOrganizational
Risk AGTOMS REPORTPage 3
Data protection officers

Record, impact assessments, data subject requests, reporting.

Management

Accountability, resources, approval of high-risk processing activities.

IT operations and information security

Technical measures, logging, erasure, link to the ISMS.

Procurement and business units

Data processing contracts, information on processing activities in day-to-day business.

Multi-compliance

Capture once, use many times

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.

One measure, two pieces of evidence

The link to the ISMS ensures that technical and organizational relationships remain traceable at all times and do not have to be maintained twice.

ISO 27701 and ISO 29151 as well

In addition to the GDPR, international standards such as ISO 27701 and ISO 29151 can be covered and evaluated.

AI systems in the same model

If an AI system processes personal data, it belongs in both registers. In CRISAM®, the two objects are linked to each other.

Reports instead of binders

Automated reports on the record, impact assessments, measures and data subject requests, plus export functions for audits, management and external reviews.

Comparison

GDPR and NIS2: two notification paths, two 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.

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

Why this belongs together

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.

Knowledge on the topic

See the platform in action

A self-study course, an instructor-led training and the associated content catalog.

CRISAM® imagery: connected globe
Academy, e-learning

Data protection management

Record, impact assessment and measures in CRISAM®, at your own pace.

Go to the course
CRISAM® imagery: connected data points
Training, online

CRISAM® Intermediate IRM and DPMS

Risk management and data protection management working together, led by an instructor.

View dates
Resources

GDPR Knowledge Pack

The content catalog that forms the basis for your assessments in CRISAM®. Plus all dates, courses and product documentation at a glance.

Go to the Knowledge Pack
AcademyDownload center
Getting started

How to get started with CRISAM®

The first step depends on where you stand today.

Starting point A

The record lives in a spreadsheet

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.

Starting point B

The impact assessments are missing

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.

Book a demo
Frequently asked questions

Frequently asked questions about the GDPR

  • 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.

References

Sources and status

The regulatory information on this page comes from the following sources.

  • Regulation (EU) 2016/679 of 27 April 2016, General Data Protection Regulation, full text on EUR-LexLegal act
  • Austrian Data Protection Authority, Your obligations as a controllerObligations
  • Austrian Data Protection Authority, data breach procedureNotification
  • German Federal Commissioner for Data Protection and Freedom of Information, reporting data protection violationsNotification Germany

The information reflects the status of the sources listed as of the review date stated above.

Next step

The documents exist. Just not in one place.

In the demo, we walk through your case: record, threshold analysis, measures, processors and the finished reports.

Book a demo

No risk - let's just stay in touch!

Green phone icon for getting in touch.
Phone

+43 732 601 216-0

Green envelope icon representing email.
E-Mail

office@crisam.net

Green paper plane icon representing sending an email.
Newsletter

Register now

CRISAM GRC Software
Darstellung eines Trends im Risikomanagement

CALPANA business consulting GmbH

Blumauerstr. 45-47

4020 Linz, Austria

+43 732 601 216-0 sales@crisam.net

CALPANA business consulting Deutschland GmbH

Paul-Dessau-Str. 1

22761 Hamburg, Germany

+49 (40) 35 98 29 21 sales@crisam.net

CALPANA business consulting GmbH

Blumauerstr. 45-47

4020 Linz, Austria

+43 732 601 216-0 sales@crisam.net

CALPANA business consulting Deutschland GmbH

Paul-Dessau-Str. 1

22761 Hamburg, Germany

+49 (40) 35 98 29 21 sales@crisam.net
CRISAM®
  • What is CRISAM?
  • CRISAM® Method
  • CRISAM® Content
  • Customers
  • Academy
  • Webinars
  • Events
  • CRISAM® Academy
Operational area
  • Integrated Risk Management
  • Information Security Management
  • CRISAM® AI
  • ESG
  • Data Protection Management
  • Audit Management
  • Compliance Management
  • Business Continuity Management
  • Tax Compliance Management System
  • Project Risk Management
  • Legal Register
  • Conflicts of Interest Software
  • CRISAM® Legal Hold Software
Industries
  • Automotive
  • Energy
  • Manufacturing
  • Financial Services
  • Healthcare
  • Retail
  • Real Estate & Construction
  • Broadcasting & Telecommunications
  • Technology
  • Transport & Logistics
More
  • Download Center
  • CRISAM® Academy
  • Webinars
  • CRISAM® Partners
  • Jobs
  • News
  • Trust Center
  • Contact

© 2026 CALPANA business consulting GmbH. All rights reserved.

  • Imprint
  • Privacy
  • Trustcenter
linkedin
xing
Chartis Research Category LeaderChartis RiskTech Quadrant® for GRC Analytics 2025

You complete your registration on the next page. Unsubscribe at any time.

Please enter a valid email address.

Solutions

  • Risk management
  • Information & Cyber Security (ISMS)
  • Internal control system
  • Compliance Management
  • All solutions

Platform

  • Platform overview
  • CRISAM® AI
  • Reporting
  • Standards and frameworks

Resources

  • Success Stories
  • News
  • Webinars
  • Events
  • Careers

Kontakt

  • Österreich+43 732 601 216-0
  • Deutschland+49 40 35 98 29 21
  • E-Mailoffice@crisam.net
Live-Demo buchen

© 2026 CALPANA business consulting GmbH. All rights reserved.

CALPANA business consulting GmbH, Blumauerstraße 45-47, 4020 Linz, Österreich

CALPANA business consulting Deutschland GmbH, Paul-Dessau-Straße 1, 22761 Hamburg, Deutschland

  • Legal notice
  • Privacy
  • Trust Center
  • Cookie settings
  • GGovernanceStrategy & objectives

    • Strategic Management
    • Lean Management Systems
    • GRC Twins
    • Decision Intelligence
    • Policy Management

    Overview

    All solutions on one platform

    View all solutions

    RRiskRisk & resilience

    • Integrated Risk Management (IRM)
    • Project Risk Management
    • Information & Cyber Security (ISMS)
    • Business Continuity Management (BCM)
    • Supply Chain Security

    New: AI governance

    AI Governed Autonomy

    Steer and evidence critical AI decisions without slowing AI down.

    Explore the framework

    CComplianceCompliance & regulation

    • Legal Register
    • Data Protection Management
    • AI Management System
    • ESG Management
    • Internal Control System (ICS)
    • Audit Management
    • Compliance Management
    • Tax Compliance (TCMS)
    • Legal Hold
    • Conflicts of Interest
  • Features

    • CRISAM® platform overview
    • Reporting
    • Integrations
    • CRISAM® Method
    • Content
    • Onboarding & implementation
    • Trust Center

    Regulations & frameworks

    • DORA
    • NIS2
    • ISO/IEC 27001
    • GDPR
    • EU AI Act
    • CSRD
    • TISAX
    • ISO 22301
    All standards and frameworks covered

    Featured

    CRISAM® AI

    AI Risk Intelligence and AI Risk Assistance detect risks early and suggest measures.

    Discover CRISAM® AI
  • Industries

    • Financial services
    • Healthcare
    • Energy & utilities
    • Public sector
    • Automotive
    • Manufacturing
    • Transport & logistics
    • Retail & consumer goods
    • Real estate & construction
    • Broadcasting & telecommunications
    • Technology

    Teams

    • Risk management
    • CFO & CRO
    • CISOs & ISMS owners
    • CIO
    • Compliance
    • Internal audit & ICS
    • Data protection officers
    • ESG & sustainability
    • AI officers

    Customers

    • Success Stories

    Success Story

    Vossloh

    Vossloh

    How Vossloh AG introduced CRISAM® GRC to meet the requirements of IDW PS 340 (revised).

    Read the story
  • About CRISAM®

    • About us
    • Careers
    • Contact

    Partners

    • CRISAM® partners
    • CALPANA consulting
    • Become a partner
  • Resources

    • News
    • Download center
    • Academy

    Events

    • Events
    • Webinars

    Next date

    Corporate Risk Minds Europe 2026

    23 to 24 November 2026, Hotel Okura, Amsterdam

    Book an appointment
EN DE Login
Book a live demo
  • DE
Book a live demo
#RISK Meet CRISAM® at #RISK Expo Europe, ExCeL London, 10 to 11 November, Stand 13. Learn more
Corporate Risk Minds Europe 2026 Meet CRISAM® at Corporate Risk Minds Europe, stand 4, Hotel Okura Amsterdam, 23 to 24 November. Learn more