MaRisk Compliance and Risk Management
Banking Risk Management | MaRisk
Manage MaRisk Compliance and Risk Management with Cetbix GRC
Bring regulatory requirements, risk assessments, internal controls, outsourcing activities and compliance evidence together in one central GRC environment.
Strengthen your risk management framework with MaRisk
The Minimum Requirements for Risk Management (MaRisk – Mindestanforderungen an das Risikomanagement) are supervisory requirements issued by the German Federal Financial Supervisory Authority (BaFin). They establish principles for appropriate and effective risk management in institutions within their scope.
MaRisk addresses the organisation of risk management, management responsibilities, risk-bearing capacity, business and risk strategies, internal controls, risk-specific processes, outsourcing and risk reporting.
For financial institutions, implementing MaRisk means translating supervisory expectations into operational processes, clearly assigned responsibilities, effective controls and reliable documentation.
Cetbix GRC provides a central environment for organising regulatory requirements, risks, controls, responsibilities, evidence and corrective actions. It can help institutions structure and oversee the activities that contribute to their MaRisk compliance programme.
Who needs to consider MaRisk?
MaRisk is primarily relevant to institutions subject to the corresponding German banking and financial supervisory requirements. Its precise applicability depends on the institution's regulatory status, business activities and applicable legal provisions.
- Credit institutions: Banks and other credit institutions within the scope of the German Banking Act (KWG).
- Financial services institutions: Institutions subject to relevant supervisory requirements, depending on their regulatory classification.
- Investment firms: Relevant investment firms where MaRisk requirements apply under the applicable legal and supervisory framework.
- Financial groups: Institutions that need to consider group-wide risk management, governance and reporting arrangements.
- Risk and compliance functions: Teams responsible for regulatory implementation, risk controlling, internal controls and supervisory documentation.
The exact scope and proportionality of requirements must be assessed individually. Not every financial company is automatically subject to every MaRisk provision.
1. MaRisk regulatory requirements and governance
MaRisk specifies supervisory expectations for the organisation of risk management and internal governance. It is closely connected to the organisational requirements under Sections 25a and 25b of the German Banking Act (KWG).
Institutions must establish appropriate business organisation and risk management arrangements that reflect their size, complexity, business activities and risk profile.
Cetbix GRC can support the governance and oversight of MaRisk requirements by connecting regulatory obligations to internal policies, risks, controls, responsible stakeholders and supporting evidence.
- Maintain a structured register of applicable MaRisk requirements.
- Document regulatory responsibilities and internal governance arrangements.
- Connect requirements to internal policies and procedures.
- Assign accountable owners for implementation and review.
- Record management approvals and compliance assessments.
- Document identified gaps and corrective actions.
- Monitor the implementation status of relevant requirements.
2. Risk-bearing capacity and risk strategy
A central element of MaRisk is the requirement to maintain an appropriate framework for risk-bearing capacity. Institutions must identify and assess material risks and ensure that these risks are adequately considered in their risk management and strategic planning.
The risk strategy should be consistent with the business strategy and reflect the institution's risk appetite, material risks and available risk-bearing capacity.
Cetbix GRC can support the documentation and governance activities associated with risk-bearing capacity and risk strategy management.
- Document the institution's business and risk strategies.
- Maintain records of material risk assessments.
- Connect identified risks to relevant risk owners and business areas.
- Document risk appetite, limits and related control responsibilities.
- Record management reviews and strategy approvals.
- Track risk mitigation measures and outstanding issues.
- Maintain evidence of periodic risk strategy reviews.
3. Risk identification, assessment and monitoring
MaRisk expects institutions to identify, assess, manage and monitor material risks across their business activities. Risk identification should consider the institution's overall risk profile, relevant dependencies and potential concentrations.
Risk assessments should be proportionate to the institution's activities and should provide a reliable basis for management decisions and risk monitoring.
Cetbix GRC can support a structured risk management process by maintaining risk registers, assessments, responsibilities, controls and remediation records.
- Maintain a central inventory of material risks.
- Document risk identification and assessment methodologies.
- Assess inherent and residual risks.
- Assign risk owners and responsible business units.
- Connect risks to controls and mitigation measures.
- Record risk acceptance decisions and approvals.
- Monitor changes in risk exposure and outstanding actions.
Key risk categories under MaRisk
MaRisk addresses different categories of risk that may affect an institution's financial position, earnings, liquidity and operational stability.
Counterparty default risk
Risks arising from the failure of borrowers, counterparties or other contractual partners to meet their obligations.
Market price risk
Risks resulting from changes in interest rates, foreign exchange rates, equity prices, commodity prices and other market factors.
Liquidity risk
Risks associated with the institution's ability to meet payment obligations and maintain adequate funding and liquidity.
Operational risk
Risks arising from inadequate or failed internal processes, people, systems or external events, including relevant ICT-related risks.
Credit spread risk
Risks resulting from changes in credit spreads that affect the value of relevant positions and exposures.
ESG risk drivers
Environmental, social and governance factors that may influence material risk categories and the institution's risk profile.
4. Internal control system and organisational requirements
MaRisk requires an appropriate internal control system that supports the identification, assessment, management and monitoring of material risks.
Institutions need clear organisational structures, defined responsibilities, appropriate separation of duties and effective control processes. The control framework should reflect the nature, scale and complexity of the institution's activities.
Cetbix GRC can help organisations structure and document their internal control environment.
- Maintain an inventory of internal controls and control objectives.
- Connect controls to regulatory requirements and identified risks.
- Assign control owners and review responsibilities.
- Document control descriptions, procedures and frequencies.
- Record control assessments and testing results.
- Document control deficiencies and remediation activities.
- Maintain evidence of management oversight and reviews.
5. Governance, risk controlling and compliance functions
MaRisk establishes requirements for the organisation of key control and oversight functions. Institutions must ensure that relevant responsibilities are clearly defined and that control functions can perform their activities appropriately.
The risk controlling function supports the institution-wide identification, assessment and monitoring of risks. The compliance function supports the management of material compliance risks, while internal audit provides independent reviews of the institution's processes and controls.
Cetbix GRC can support the coordination and documentation of these governance activities.
- Document responsibilities across management and control functions.
- Maintain records of risk controlling activities and assessments.
- Organise compliance obligations and related control activities.
- Record internal audit findings and recommendations.
- Assign remediation owners and target dates.
- Track management responses and corrective actions.
- Maintain supporting evidence for supervisory and audit reviews.
6. Outsourcing and third-party risk management
MaRisk AT 9 addresses the requirements for outsourcing activities. Institutions must assess the risks associated with outsourcing and establish appropriate arrangements for selecting, monitoring and controlling external service providers.
Outsourcing does not transfer the institution's responsibility for meeting its regulatory obligations. The institution must retain appropriate oversight of outsourced activities and ensure that relevant risks are adequately managed.
Cetbix GRC can support the governance and documentation of outsourcing and third-party risk management activities.
- Maintain an inventory of outsourcing arrangements and service providers.
- Document outsourcing assessments and risk classifications.
- Record due diligence and provider evaluation results.
- Connect providers to relevant services, processes and risks.
- Document contractual requirements and monitoring responsibilities.
- Track provider reviews, incidents and identified deficiencies.
- Maintain evidence of approvals, reassessments and corrective actions.
- Document relevant contingency and exit considerations.
7. ICT risk management and the relationship with DORA
Information and communication technology risks form an important part of operational risk management. Financial institutions need to consider the potential impact of technology failures, cyber incidents, data loss, system disruptions and dependencies on external ICT service providers.
The Digital Operational Resilience Act (DORA), Regulation (EU) 2022/2554, establishes a dedicated European framework for ICT risk management, incident handling, resilience testing and ICT third-party risk management. DORA has applied since 17 January 2025.
MaRisk and DORA should be considered together where both frameworks apply. They are complementary regulatory frameworks, not interchangeable compliance standards.
Cetbix GRC can support the governance and oversight of related regulatory requirements and risk management activities.
- Document ICT-related risks and responsible owners.
- Connect ICT risks to operational risk assessments.
- Maintain references to ICT policies and control procedures.
- Record ICT third-party assessments and provider responsibilities.
- Document incident-related findings and remediation actions.
- Connect relevant DORA requirements to internal controls.
- Maintain evidence of reviews, approvals and testing activities.
Important: DORA contains specific requirements and scope provisions. Institutions should assess the applicable regulatory obligations individually and avoid assuming that a MaRisk control automatically fulfils every DORA requirement.
Which frameworks support MaRisk implementation?
MaRisk is a principles-based supervisory framework. It does not prescribe one universal management system or certification standard. Institutions can use established risk management, information security, business continuity and internal control frameworks to structure their implementation activities.
The appropriate combination depends on the institution's regulatory obligations, business model, risk profile and existing governance arrangements.
Recommended risk management framework stack
1. ISO 31000
Focus: Enterprise risk management
ISO 31000 provides principles and guidelines for managing risks across an organisation.
- Risk identification and assessment.
- Risk analysis and evaluation.
- Risk treatment and monitoring.
- Integration with organisational governance.
- Communication and continuous improvement.
MaRisk relevance: Supports the design of a consistent institution-wide risk management approach.
2. ISO/IEC 27001
Focus: Information security management
ISO/IEC 27001 provides requirements for establishing and maintaining an Information Security Management System (ISMS).
- Information security risk management.
- Policies and responsibilities.
- Access control and asset management.
- Incident management.
- Supplier security and continuous improvement.
MaRisk relevance: Supports information security governance and the management of relevant ICT and operational risks.
3. DORA
Focus: Digital operational resilience
DORA establishes requirements for ICT risk management and digital operational resilience in financial entities within its scope.
- ICT risk management framework.
- ICT incident management and reporting.
- Digital operational resilience testing.
- ICT third-party risk management.
- Information sharing and governance.
MaRisk relevance: Addresses specific ICT-related regulatory obligations alongside the broader MaRisk risk management framework.
4. COSO Internal Control – Integrated Framework
Focus: Internal control and governance
The COSO framework provides principles for designing, implementing and assessing internal control systems.
- Control environment.
- Risk assessment.
- Control activities.
- Information and communication.
- Monitoring activities.
MaRisk relevance: Provides a useful structure for internal control governance and control effectiveness assessments.
5. ISO 22301
Focus: Business continuity management
ISO 22301 specifies requirements for a Business Continuity Management System (BCMS).
- Business impact analysis.
- Business continuity strategies.
- Incident response and recovery.
- Continuity exercises and testing.
- Continual improvement.
MaRisk relevance: Supports the organisation of business continuity and operational resilience arrangements.
6. BSI IT-Grundschutz
Focus: Information security controls
BSI IT-Grundschutz provides a structured methodology for identifying information security requirements and implementing appropriate safeguards.
- Information security management.
- Risk analysis and protection requirements.
- Technical and organisational safeguards.
- Business continuity and incident handling.
- Documentation and security reviews.
MaRisk relevance: Can support the implementation and documentation of information security controls relevant to operational and ICT risks.
Choosing the right framework combination
Institutions should select supporting frameworks according to their specific requirements rather than attempting to implement every framework in full. Regulatory obligations remain the primary reference for determining compliance.
| Management objective | Recommended framework combination | Primary objective |
|---|---|---|
| Enterprise risk management | MaRisk + ISO 31000 | Consistent risk identification, assessment, treatment and monitoring. |
| ICT and information security | MaRisk + DORA + ISO/IEC 27001 | ICT risk governance, information security and digital operational resilience. |
| Internal control system | MaRisk + COSO | Control design, responsibilities, monitoring and effectiveness assessments. |
| Business continuity | MaRisk + ISO 22301 | Continuity planning, incident response and operational recovery. |
| Information security controls | MaRisk + BSI IT-Grundschutz or ISO/IEC 27001 | Structured implementation and documentation of information security safeguards. |
How Cetbix GRC supports framework-based MaRisk compliance
Financial institutions often work with multiple regulatory requirements, standards and internal policies. Without a central structure, this can lead to duplicated controls, fragmented documentation and inconsistent reporting.
Cetbix GRC can help organisations connect MaRisk requirements with supporting frameworks, internal controls, risks, responsibilities and evidence.
Example: Connecting MaRisk, DORA and ISO 27001
Regulatory requirement: Maintain appropriate arrangements for identifying, assessing and managing operational and ICT-related risks.
Supporting frameworks:
- MaRisk: Institution-wide risk management and internal control requirements.
- DORA: Specific ICT risk management and digital operational resilience obligations.
- ISO/IEC 27001: Information security management and risk treatment practices.
Illustrative GRC structure:
- Regulatory requirement: Applicable MaRisk operational risk requirements and relevant DORA ICT risk management provisions.
- Framework requirements: Relevant ISO/IEC 27001 information security controls and DORA requirements.
- Risk: A failure of a critical ICT service could disrupt banking operations, affect customer services and create regulatory or financial consequences.
- Control: Maintain a documented ICT risk management process covering risk identification, assessment, treatment, monitoring and escalation.
- Owner: ICT Risk Manager, supported by the CISO and operational risk management.
- Evidence: ICT risk assessments, control reviews, service inventories, incident records, provider assessments and management approvals.
- Corrective action: Address identified control gaps, assign accountable owners and monitor remediation progress.
Outcome: A traceable compliance structure connecting regulatory obligations and framework practices to operational risks, controls, accountable stakeholders and supporting evidence.
Important: Framework alignment is not automatic MaRisk compliance
ISO/IEC 27001 certification does not automatically demonstrate compliance with all MaRisk requirements. ISO/IEC 27001 primarily addresses information security management and does not cover every aspect of banking risk management, governance, risk-bearing capacity or supervisory reporting.
Similarly, ISO 31000 provides useful risk management principles but does not replace the specific supervisory requirements of MaRisk.
DORA establishes directly applicable legal obligations for financial entities within its scope. Compliance with a supporting framework or an individual MaRisk control does not automatically demonstrate compliance with all DORA requirements.
Institutions must assess the applicable legal and supervisory requirements and map them to appropriate internal processes, controls and evidence.
Cetbix GRC can help manage this mapping and provide visibility into regulatory coverage, framework implementation, outstanding gaps and corrective actions.
8. Risk reporting and management information
MaRisk requires appropriate risk reporting to support management decisions and effective oversight. Risk reports should provide relevant information about the institution's risk profile, material developments, risk concentrations and limit utilisation.
Reporting should be structured so that management and relevant oversight functions can identify significant changes, assess their potential impact and take appropriate action.
Cetbix GRC can support the governance and documentation of risk reporting activities.
- Maintain records of risk reporting responsibilities.
- Connect risk assessments to relevant reporting requirements.
- Document management reviews and reporting approvals.
- Track findings and follow-up actions arising from risk reports.
- Maintain supporting documentation and evidence.
- Provide a structured overview of outstanding risks and remediation activities.
A GRC platform supports the organisation and traceability of reporting activities. It does not replace an institution's specialised risk calculation, regulatory reporting or banking systems.
9. Documentation, audit readiness and supervisory evidence
Institutions must maintain appropriate documentation of their risk management arrangements. Policies, procedures, risk assessments, control activities, responsibilities and management decisions should be sufficiently documented to support internal oversight and supervisory review.
Consistent documentation also helps internal audit and other control functions assess whether the institution's arrangements are appropriate and effective.
Cetbix GRC can provide a structured environment for managing compliance responsibilities and associated documentation.
- Maintain a register of applicable regulatory requirements.
- Connect requirements to internal policies and procedures.
- Organise risk assessments and control documentation.
- Record responsible owners, reviewers and approvers.
- Maintain supporting evidence and assessment records.
- Document audit findings and management responses.
- Track corrective actions, deadlines and completion status.
- Provide management visibility into compliance progress.
From MaRisk requirement to risk, control and evidence
MaRisk compliance becomes operational when supervisory requirements are connected to institutional risks, responsible owners, implemented controls and supporting evidence.
Illustrative example: ICT service disruption affecting banking operations
Regulatory reference: MaRisk requirements relating to operational risk management, internal controls and outsourcing, together with applicable DORA ICT risk management requirements.
Business context: A financial institution identifies that an important banking process depends on an external ICT service provider. A prolonged service disruption could affect payment processing, customer services and internal operations.
This is an illustrative GRC workflow. The record identifiers, owners and actions below are examples and are not represented as live Cetbix customer data.
| GRC element | Illustrative record |
|---|---|
| Requirement | Maintain appropriate arrangements for identifying, assessing and managing operational risks and relevant outsourcing dependencies. |
| Risk | RISK-MARISK-001 – An interruption of an external ICT service could disrupt critical banking processes, affect customer services and create operational, financial and regulatory consequences. |
| Control | Maintain an ICT and outsourcing risk management process covering provider assessment, service monitoring, incident escalation, continuity arrangements and periodic reviews. |
| Control owner | ICT Risk Manager. Accountable stakeholders: Chief Information Officer and relevant business process owner, supported by operational risk management and supplier management. |
| Evidence | ICT risk assessment, outsourcing assessment, provider due diligence, contractual documentation, service monitoring records, incident reports, continuity plans and review results. |
| Finding | FINDING-MARISK-001 – The documented recovery arrangements for the external ICT service have not been reviewed following a material service change. |
| Corrective action | CAPA-MARISK-001 – Reassess the service dependency, update recovery arrangements, verify escalation procedures and document the review. Suggested owner: ICT Risk Manager. |
| Outcome | A traceable compliance record connecting regulatory requirements to operational risks, implemented controls, accountable owners, supporting evidence and remediation status. |
The result: MaRisk requirements and related risk management activities can be managed through a structured governance process rather than disconnected spreadsheets, documents and action lists.
A structured MaRisk compliance workflow
- Determine regulatory applicability: Identify the relevant MaRisk requirements based on the institution's regulatory status, business model and activities.
- Define the compliance scope: Document relevant organisational units, business processes, risk categories and control functions.
- Identify regulatory requirements: Map MaRisk provisions and other applicable requirements to internal policies and processes.
- Perform risk assessments: Identify and assess material risks, including operational, ICT, outsourcing and financial risks.
- Evaluate existing controls: Review the design, implementation and effectiveness of relevant control activities.
- Define responsibilities: Assign accountable owners across management, risk controlling, compliance, IT and business functions.
- Document evidence: Maintain risk assessments, policies, control records, approvals and supporting documentation.
- Manage findings and remediation: Assign corrective actions, responsible owners and target dates.
- Monitor and report: Review risk developments, control results, outstanding actions and management information.
- Review continuously: Reassess the framework when business activities, risks, regulatory requirements or organisational structures change.
More than a MaRisk compliance checklist
Regulatory requirements
Organise MaRisk requirements and connect supervisory obligations to internal policies, risks and controls.
Integrated risk management
Document material risks, assessments, mitigation measures, risk owners and residual risk decisions.
Internal control management
Connect control objectives, activities, owners, reviews and evidence to applicable requirements.
Outsourcing oversight
Maintain structured records of providers, outsourcing assessments, responsibilities and related risks.
Evidence management
Keep policies, assessments, control records, approvals and audit evidence connected to compliance records.
Corrective actions and reporting
Turn identified gaps, audit findings and control deficiencies into accountable remediation activities.
MaRisk and related regulatory developments
25 May 2017
The General Data Protection Regulation (GDPR) became applicable across the European Union.
17 January 2025
The Digital Operational Resilience Act (DORA), Regulation (EU) 2022/2554, became applicable to financial entities within its scope.
30 June 2026
BaFin published Circular 06/2026 (BA), the 9th amendment to MaRisk.
Ongoing
Institutions should review their MaRisk implementation against the currently applicable circular, relevant statutory requirements and supervisory guidance. They should also assess the interaction with DORA and other applicable European financial regulations.
Regulatory implementation should be treated as an ongoing process. Institutions should monitor BaFin publications and applicable legal changes, assess their impact and update internal policies, controls and documentation where necessary.
Who can benefit from Cetbix GRC?
- Credit institutions and banks.
- Financial services institutions within the relevant regulatory scope.
- Investment firms subject to applicable MaRisk requirements.
- Banking groups and financial holding structures.
- Risk management and risk controlling departments.
- Compliance and internal control functions.
- ICT risk management and information security teams.
- Outsourcing and third-party risk management teams.
- Internal audit and supervisory preparation teams.
- Management teams responsible for governance and regulatory oversight.
Frequently asked questions
What does MaRisk stand for?
MaRisk stands for Mindestanforderungen an das Risikomanagement, meaning Minimum Requirements for Risk Management. It is a supervisory circular issued by BaFin that specifies requirements for the organisation and risk management of institutions within its scope.
Is MaRisk a law?
MaRisk is a supervisory circular rather than a standalone act of parliament. It specifies supervisory expectations based on statutory requirements, particularly under the German Banking Act (KWG).
Which MaRisk version is currently applicable?
The current published version is BaFin Circular 06/2026 (BA), the 9th MaRisk amendment, published on 30 June 2026. Institutions should consult the official BaFin publication for the applicable wording and implementation details.
Which institutions are subject to MaRisk?
MaRisk primarily applies to institutions within its defined supervisory scope under the German banking and financial regulatory framework. Applicability depends on the institution's regulatory status, business activities and relevant legal provisions.
What are the main areas covered by MaRisk?
MaRisk covers general governance and risk management requirements, risk-bearing capacity, business and risk strategies, internal controls, risk-specific processes, outsourcing, documentation and risk reporting.
What is the difference between MaRisk and DORA?
MaRisk addresses the broader risk management and governance framework of institutions within its scope. DORA is an EU regulation focused on digital operational resilience and ICT risk management. Financial entities may need to comply with both frameworks, depending on their regulatory scope.
Does ISO 31000 automatically demonstrate MaRisk compliance?
No. ISO 31000 provides principles and guidelines for risk management, but it does not replace the specific supervisory requirements of MaRisk. Institutions must assess and implement the applicable regulatory obligations.
Does ISO/IEC 27001 certification guarantee MaRisk compliance?
No. ISO/IEC 27001 addresses information security management. It can support the management of relevant ICT and operational risks, but it does not cover all MaRisk requirements relating to banking governance, risk-bearing capacity, financial risks and supervisory reporting.
What is the purpose of MaRisk AT 9?
MaRisk AT 9 addresses outsourcing arrangements. It establishes expectations for assessing, organising and monitoring outsourcing activities and their associated risks. Institutions retain responsibility for meeting their regulatory obligations.
How can GRC software support MaRisk compliance?
GRC software can help organise regulatory requirements, risks, controls, responsibilities, policies, evidence, audit findings and corrective actions. It provides a structured way to monitor compliance activities and maintain traceability.
Does Cetbix GRC automatically make an institution MaRisk compliant?
No. A GRC platform supports governance, risk management, control oversight and evidence management. The institution remains responsible for determining regulatory applicability, implementing effective arrangements and meeting its supervisory obligations.
Can Cetbix GRC support multiple regulatory frameworks?
Cetbix is designed to support governance, risk and compliance activities across regulatory frameworks. It can help organisations manage overlapping requirements, connect frameworks to internal controls and maintain a consistent view of compliance activities. The available framework libraries and specific workflows should be confirmed against the capabilities configured in the relevant Cetbix environment.
Strengthen your MaRisk Compliance with Cetbix GRC
Discover how Cetbix GRC can help connect MaRisk requirements, financial and operational risks, internal controls, outsourcing activities and compliance evidence in one structured environment.
MaRisk refers to the German Minimum Requirements for Risk Management issued by BaFin. The relevant regulatory framework includes the German Banking Act (KWG), applicable BaFin circulars and, where relevant, the Digital Operational Resilience Act (DORA), Regulation (EU) 2022/2554. This page is for general information and does not constitute legal, regulatory or supervisory advice. Regulatory applicability, proportionality, implementation requirements and the interaction between MaRisk and other regulatory frameworks must be assessed individually. Cetbix GRC supports governance, risk and compliance activities but does not replace management accountability, regulatory reporting, specialised banking systems, independent audits or legal advice.