ERM module · ISO 31000 · DORA · NIS2

Enterprise Risk Management (ERM).
A living register instead of a pre-audit spreadsheet.

ISO 31000 applied operationally: a risk register linked to processes, assets, vendors, controls and key risk indicators. Inherent, residual and target risk assessed on a configurable matrix, with a versioned history of every analysis – not a static spreadsheet updated once a year.

In brief

What is the risk management module in BCMLogic Next?

It is enterprise risk management (ERM) software in which operational, ICT, business continuity and compliance risks are identified, assessed and monitored in a single register. Each risk is linked to processes, assets, vendors and contracts from the Organisation module, and to controls and KRIs. As a result, the risk level reflects data – incidents, BIA results, control status – not just declarations.

Key facts

Risk analysis: a wizard with eight configurable steps – from the risk profile to KRIs and the summary

Matrix: for example 5 likelihood levels and 4 impact areas; the risk level is calculated as a weighted sum of impacts

Controls: a register of existing and planned safeguards with type, maturity, automation and test result

KRIs: an indicator library with warning and critical thresholds, updated from integrations or manually with evidence

History: every assessment is versioned – you can go back to an earlier one and compare changes over time
See it in action

Risk register, analysis and controls in practice

Recordings from the BCMLogic Next platform. Pick an area – the next recording starts automatically.

BCMLogic Next · Risk Management

Risk register and the analysis of a selected risk: profile, links to processes, assets, vendors and contracts, then inherent and residual risk assessment.
Assessment methodology

From inherent to target risk

The matrix shows how controls move risk from the inherent to the residual level, and how the treatment plan takes it to the target level.

Impact (1–5)

I
R
T
Likelihood (1–5)
I

Inherent risk

Assessed before controls: likelihood and financial, reputational, legal and regulatory, and business continuity impact. Optional – some methodologies assess residual risk only.

R

Residual risk

Assessed after existing controls. Based on it, the system allows a strategy: further mitigation, acceptance with justification and expiry date, or monitoring.

T

Target risk

The level the organisation aims for once the treatment plan is implemented. Completed plans become active controls.

Example 5×5 matrix. Scales, impact areas, weights and risk level thresholds are fully configurable.

Step-by-step analysis

Eight steps of risk analysis – you decide their order and which are mandatory

An example methodology supplied with the platform. Dictionaries, scales, threshold descriptions and impact areas can be adapted to the methodology your organisation uses.

1

Risk profile

Category, sub-category, cause, description and owner.

2

Links

Processes, assets, vendors and contracts affected by the risk – from the Organisation and Vendor registers.

3

Inherent risk

Likelihood and impact across several dimensions before controls.

4

Residual risk

Assessment after existing controls – showing how much they really reduce the risk.

5

Risk treatment

The strategy allowed for the given level: mitigation with an action plan, acceptance with justification and expiry date, or monitoring.

6

Target risk

The level to be reached once the plan is implemented.

7

Key risk indicators

Assigning indicators that objectively measure changes in likelihood or impact.

8

Summary

Review and saving the analysis as a new version in the risk history.

Requirements the module addresses
ISO 31000
The risk management process: identification, analysis, evaluation, treatment, monitoring and review.
ISO/IEC 27001
Information security risk assessment and treatment (clauses 6.1.2, 6.1.3, 8.2, 8.3).
DORA – Article 6
An ICT risk management framework, documented and reviewed at least once a year.
NIS2 – Article 21(2)(a)
Policies on risk analysis and information system security. In Poland, under the amended KSC Act, as part of the ISMS – implementation by 3 April 2027, first audit of essential entities by 3 April 2028.

This summary is for information only. The scope of obligations depends on the entity’s status and current legislation.

Scope of use

One module for many types of risk

Risks are analysed at many levels – from an IT system or location, through management systems, up to the unit, company and group – with category isolation and consistent escalation to higher levels.

Operational risk (ERM)

Risks of business processes and services, typically managed at department or division level.

Business continuity risk

Risks in the categories of people, IT infrastructure, locations and vendors – at process and resource level.

Compliance risk

A risk library maintained in the application or imported from external sources.

Exception management

A form for deviations from a security rule: opinions from legal, security and IT, risk level and validity period of the approval.

Operational loss events

Actual events with estimated financial and non-financial losses across multiple categories.

Vulnerabilities

Categorisation and monitoring of vulnerabilities, prioritised by the criticality of linked processes and assets, with task assignment.

What this means in practice

Two users opening the same register may see different sets of risks. Permissions are granted dynamically – by risk category, organisational unit, asset or process. A site manager sees their own risks and can escalate a serious threat, while the board gets an aggregated view.

Controls and indicators

Risk measured objectively, not just declared

Standards and sector regulations increasingly expect risk levels to be backed by measures. That is what the controls register and KRIs are for.

Controls register

Existing controls – general (e.g. antivirus on workstations) and asset-specific (e.g. a fire suppression system in the server room).
Planned and in-progress controls – treatment plans triggered when a risk exceeds the acceptable level.
Control card: nature, type, automation, maturity, implementation date, test result and test schedule.
A completed treatment plan becomes an active control and lowers residual risk.

Key risk indicators

A KRI library covering IT, business and cybersecurity, including indicators for DORA requirements and Polish FSA (KNF) expectations.
Values updated through integrations with source systems or manually – with evidence and justification.
A chart of changes over time with warning and critical thresholds.
An indicator owner and update requests sent from the platform.

Reports and export

Analytical reports, visualisations and export to MS Excel.

Role-based dashboards

Risk views for the management board, supervisory board and heads of business areas.

Expert GRC

The AI assistant proposes inherent, residual and target ratings from the risk description – the analyst approves every change.

Related modules

Risk fed by data from across the platform

Likelihood can be derived from the number of incidents affecting a process or asset, and impact from BIA data.

Organisation

Processes, assets and structure to which you assign risks and by which you aggregate reports.

Organisation module →

Business continuity

BIA results and BCP plans as a source of impact data and risk-reducing actions.

BCM module →

Vendor management

ICT vendor risk passed into the organisation’s risk register.

Vendor module →

Online demo

See risk analysis on your own methodology

In the demo we walk through the risk register, a full analysis on the matrix, the controls register and KRIs – and show how to configure scales and workflow for your methodology.

Book a demo →

Live walkthrough

About 30 minutes with a BCMLogic expert – focused on your risks and sector regulations.

Methodology configuration

Scales, impact areas, thresholds and analysis steps adapted to the organisation, not the other way round.

FAQ

Frequently asked questions about risk management

Answers for risk, compliance and information security teams.

How is risk management software different from an Excel register?
A spreadsheet shows the state as of its last update. Risk management software such as BCMLogic Next links each risk to processes, assets, vendors, controls and KRIs, versions every assessment, runs an approval workflow and grants permissions by role. The risk picture stays current and the decision trail is auditable.
What is the difference between inherent, residual and target risk?
Inherent risk is the level of risk before controls are taken into account. Residual risk is the level after existing controls. Target risk is the level the organisation aims to reach once the risk treatment plan is implemented. In BCMLogic Next all three ratings are shown on the same matrix.
Can I configure our own risk assessment methodology?
Yes. The order and mandatory status of analysis steps, dictionaries, likelihood scales, impact areas, threshold descriptions and the way the risk level is calculated are all configurable. The risk lifecycle – statuses and approvals – is modelled in the workflow editor so the system reflects your organisation’s process.
What are key risk indicators (KRIs) and how do they work in BCMLogic Next?
Key risk indicators are measurable values that signal a change in the likelihood or impact of a risk. In BCMLogic Next each indicator has an owner, warning and critical thresholds and a value history. Values are updated through integrations with other systems or manually with evidence, and indicators are assigned to specific risks.
How does BCMLogic Next support the risk analysis required by NIS2?
Article 21(2)(a) of the NIS2 Directive requires policies on risk analysis and information system security. In Poland the amended KSC Act has applied since 3 April 2026; essential and important entities must implement their obligations, including an ISMS, by 3 April 2027, and the first audit of essential entities is due by 3 April 2028. BCMLogic Next provides a risk register linked to assets and processes, versioned assessments and management reporting.
Is risk assessment in BCMLogic Next aligned with ISO 31000 and ISO 27001?
The module follows the ISO 31000 stages: identification, analysis, evaluation, treatment and monitoring. Asset risk analysis – with confidentiality, integrity and availability valuation, threats, vulnerabilities and controls – supports the information security risk assessment required by ISO/IEC 27001.
Is the history of risk assessments kept?
Yes. Every analysis is versioned – a periodic review or a materialised risk creates a new version, while previous ones remain available for viewing and comparison. This lets you show an auditor how and why the rating changed.
How does AI help with risk assessment?
Based on a risk’s description, category and links, the Expert GRC assistant can propose inherent, residual and target ratings and create or complete a risk in the register. Every change is first shown as a proposal and requires the user’s approval, and each query is logged for audit.
Next step

Risk you can see at any time – not only before the audit

We will show how BCMLogic Next connects the risk register with processes, controls, KRIs and vendors – and how to report it to the board.

Book a demo →