
CRISAM® ICS and Audit as the Backbone of the Three Lines of Defense Model
How to interlock the internal control system and audit in CRISAM® and implement the Three Lines of Defense model.
Next date: 15 December 2026, 01:00View datesEvery control is derived from an assessed risk, managed through a workflow, and documented with evidence. The structure follows IDW PS 982. Risks, controls, compliance requirements, and audits are all mapped in the same model.
| Control objective | Effectiveness | Maturity level | Open |
|---|---|---|---|
| Payment approval | effective | 4 | 0 |
| Supplier onboarding | limited | 3 | 4 |
| Access provisioning | not effective | 2 | 7 |
| Closing entries | effective | 4 | 1 |
| Inventory count | under review | 3 | 2 |
| Order approval | not tested | 2 | 0 |
| Control | Process | Loss potential | Status | Owner |
|---|---|---|---|---|
| Dual control for payment run | Financial accounting | €4.20M | effective | Head of Finance |
| Supplier master data maintenance | Purchasing | €3.10M | limited | Head of Purchasing |
| Access recertification | IT operations | €2.75M | not effective | Head of IT |
| Production order approval | Production | €1.95M | effective | Plant management |
| Quote terms approval | Sales | €1.40M | under review | Head of Sales |
Manufacturing, retail, energy, and healthcare: wherever controls, risks, and audits need to be managed together instead of running side by side.
The controls sit in a spreadsheet, the evidence in folders, the responsibilities in email threads. Before the next closing, the gathering starts all over again.
The reports are finished on time, yet the path to them is still hard to prove.
The data is up to date at all times, even between two audits.
IDW PS 982 provides the framework. The methodology is built into the system, and you decide on control types and frequency. Each step builds on the previous one. That is why the result is a report based on documented data.
The ICS starts with a structured risk assessment. Risks in business processes, IT, and compliance are captured and assessed.
For every assessed risk, you create the matching control. The wizard guides you through the steps, and the help column explains each field right next to it.
A descriptive name for the control. Follow the naming convention of your organization.
Control owner and reviewing functionThe control owner performs the control. The reviewing function assesses its effectiveness, separated according to the Three Lines of Defense model.
Risk coveredResults from the selection in the previous step. Through this link, the control later takes effect in the risk report.
Control type and frequencyControls the follow-up and the tasks assigned to the people involved.
Required evidenceDefines what is stored when the control is performed. The evidence stays versioned on the object and is available to the audit later.
Assigned standardThrough this assignment, the control counts toward the analysis without you having to collect the evidence more than once.
Controls are not just documented, they are also performed. Workflows assign tasks, send deadline reminders, and track implementation, one-time or recurring.
| Control | Frequency | Due | Owner | Status |
|---|---|---|---|---|
| Dual control for payment run | monthly | Mon | Head of Finance | completed |
| Open item reconciliation | monthly | Wed | Accounts receivable | in progress |
| Access recertification | quarterly | Thu | Head of IT | overdue |
| Goods receipt sample check | weekly | Fri | Head of Logistics | open |
| Approval of terms deviations | weekly | Fri | Head of Sales | open |
| Bank account reconciliation | monthly | Fri | Treasury | in progress |
| Emergency access review | quarterly | Fri | Head of IT | completed |
| Review of open purchase orders | weekly | Fri | Head of Purchasing | in progress |
| Fixed asset register reconciliation | monthly | Fri | Asset accounting | open |
Effectiveness is assessed, not assumed. The compliance level by business process shows where the control system works and where gaps exist.
| Rating | Controls | Share |
|---|---|---|
| effective | 191 | 77 % |
| partially effective | 38 | 15 % |
| not effective | 12 | 5 % |
| not tested | 7 | 3 % |
| Total | 248 | 100 % |
The same data produces the management report and the documentation for internal and external audits, without you having to gather anything a second time.
| Measure | Chapter | Deadline | Owner | Status |
|---|---|---|---|---|
| Revise ERP authorization concept | 3 | 31 Oct | Head of IT | overdue |
| Adjust purchasing approval limits | 3 | 15 Nov | Head of Purchasing | in progress |
| Document escalation paths | 4 | 30 Nov | Compliance | in progress |
| Plan Q4 control tests | 5 | 15 Dec | Internal audit | completed |
| Tighten supplier master data maintenance | 3 | 20 Dec | Head of Purchasing | in progress |
| Review report recipients by site | 4 | 31 Jan | Controlling | open |
| Substitution arrangement for critical roles | 1 | 15 Feb | Head of HR | open |
| Repeat payment run effectiveness test | 5 | 28 Feb | Internal audit | open |
The list of controls stays the same. What changes is what you can prove with it and how much manual work it takes.
Every control is linked to an assessed risk. You can justify why it exists and see where a control is missing.
Execution, monitoring, and reporting are assigned separately. Who takes on which task is documented on the object, not just agreed verbally.
Workflows distribute tasks, send deadline reminders, and request results. Follow-up questions shortly before the due date are no longer needed.
Controls, measures, and changes are versioned and kept in a history. For the audit, the status at any given point in time is available, not just the current one.
Roles and responsibilities for risks, controls, monitoring, and reporting follow the governance model, without additional workarounds.
ICS, risk management, compliance, and audit access the same objects. Redundant surveys are eliminated.
From risk assessment through execution to the audit report, the entire process is built into the module, with no custom development.
The model starts with the risk assessment in business processes, IT, and compliance. The controls are derived from it, not defined independently of it.
The Content Libraries provide hundreds of predefined controls, including for information security, data protection, IT security, and compliance.
You map company-specific controls individually, with your own fields, control types, and test steps.
Assignment, execution, and follow-up run through workflows. The people involved are automatically reminded of open tasks.
One-time and recurring controls are given dates and deadlines. Due and overdue executions are visible at all times.
Roles and responsibilities for risks, controls, monitoring, and reporting are clearly assigned and traceable.
Controls, measures, changes, and results are centrally documented, versioned, and kept in an auditable history.
Every change is retained with its timestamp and author. For the audit, the status of the reporting period is available, not just the current one.
Status, effectiveness, and open measures at a glance. From every key figure, you go straight to the individual control.
Reports on risks, controls, and measures for management, plus audit and review reports for internal and external audits.
Views by organizational unit, site, or role. Each group of recipients sees the part of the same data set that is relevant to them.
Risks, controls, compliance requirements, and audits are considered together. This increases the steering effect of the ICS.
The methodology is built into the system. You neither have to develop it yourself nor justify it separately during the audit. How CRISAM® calculates is explained by the CRISAM® method.
Each role sees the part that is relevant to it, and everyone works on the same objects. There is no more coordinating which list is currently valid.
You see which risk each control covers and where a control is missing. Test steps, results, and evidence are documented on the same object as the control.
One control takes effect in the ICS, in information security, and in the compliance evidence, without you having to carry out the same survey several times.
Effectiveness, open measures, and deadlines are included in the report. Every figure can be traced back to the individual control, even after the reporting date.
Companies that manage controls, risks, and audits in one system. The customer overview shows which modules each company uses.
AIXTRON SE
In use: Risk management, ICS
AIXTRON is a provider of deposition equipment for the semiconductor industry with customers worldwide. For a global high-tech company, reliable management and risk structures are especially important.
Amprion
In use: Risk management, ICS
Amprion is a German transmission system operator whose extra-high-voltage grid secures the power supply for millions of people. In an environment of high systemic importance, stable, traceable and scalable GRC processes are essential.
Aquila Capital
In use: Risk management, Information security, Audit
Aquila Capital is an asset manager focused on investments in the energy transition and infrastructure. With sustainable investment strategies and complex structures, transparency, a clear view of risks and sound governance are especially important.
An internal control system (ICS) is the entirety of rules, procedures, and controls a company uses to limit risks in business processes, IT, and compliance. It comprises the control environment, risk assessment, control activities, information and communication, and monitoring activities. In CRISAM®, it is built from assessed risks, performed through workflows, and documented in an audit-proof manner.
The setup starts with a structured risk assessment. Risks in business processes, IT, and compliance are identified and assessed, and the necessary controls are then derived specifically from them. Predefined controls from the Content Libraries can be adopted, and you additionally model company-specific controls yourself.
CRISAM® ICS is methodologically sound and built on recognized standards such as IDW PS 982. All controls, measures, changes, and results are centrally documented, versioned, and kept in an auditable history. Audit and review reports support internal and external audits, and every key figure can be traced back to the individual control.
A spreadsheet documents controls but does not manage how they are performed. In CRISAM®, every control is linked to the risk it covers, workflows manage assignment, scheduling, and follow-up, and every execution leaves versioned evidence. The status is available at any time instead of being gathered once a year.
CRISAM® integrates the ICS into the overall GRC context. Risks, controls, compliance requirements, and audits are considered together and access the same objects. This ensures consistent information, avoids redundancies, and strengthens the steering effect of the ICS.
The governance model separates operational responsibility, monitoring, and independent audit. CRISAM® supports this model: roles, responsibilities, and accountabilities for risks, controls, monitoring, and reporting are clearly assigned and traceable, and every assignment is visible on the object.
The CRISAM® GRC platform and the CRISAM® ICS module are required. The ICS is fully integrated into the platform and is not a standalone solution. Existing systems remain in place and are connected through interfaces.
A webinar on the interplay of ICS and audit, an overview of the platform, and the courses of the CRISAM® Academy.

How to interlock the internal control system and audit in CRISAM® and implement the Three Lines of Defense model.
Next date: 15 December 2026, 01:00View dates
Risk, compliance, internal control system, and audit management on one platform, with a view to IDW PS 340 (revised version) and NIS2.
Next date: 1 December 2026, 02:00View datesAn overview of webinars and training sessions, plus the self-paced courses of the CRISAM® Academy and the product materials in the download center.
AcademyDownload centerBring two or three controls from your company. We will show you how they are derived from the risk, how execution is managed, and what the evidence looks like.
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