DRIMT logoDRIMT

    Risk assessment · NIS2 · ISO 27001 · DORA

    Cyber risk assessment that stays current

    Identify your assets, score every threat on likelihood and impact, and turn the results into owned, dated treatments — the risk analysis NIS2, ISO 27001 and DORA all start from.

    ISO/IEC 27001:2022

    Clause 6.1.2

    A defined, repeatable risk assessment process, re-run at planned intervals (clause 8.2)

    NIS2 Article 21(2)(a)

    Risk analysis

    The first of the ten measures — every other measure must be proportionate to it

    DORA Article 6

    Reviewed yearly

    The ICT risk management framework is documented and reviewed at least once a year

    The six-step risk assessment method

    Whether you follow ISO/IEC 27005, NIST SP 800-30 or the CCB's CyFun approach, a defensible cyber risk assessment follows the same loop. The point is not a perfect spreadsheet but a decision trail an auditor — and your board — can follow.

    1. 01

      Identify assets & owners

      List the systems, data, suppliers and people your critical services depend on, each with an accountable owner.

    2. 02

      Find threats & weaknesses

      Cover cyber, physical and human threats (NIS2 asks for an all-hazards approach) and the vulnerabilities they could exploit.

    3. 03

      Score likelihood × impact

      Rate each scenario on a shared scale — typically 1–5 — so risks become comparable across teams.

    4. 04

      Evaluate against appetite

      Compare scores to the risk appetite your management approved and decide which risks need action first.

    5. 05

      Treat with an owner and date

      Mitigate, transfer, avoid or formally accept each risk, linking it to a control, an owner and a deadline.

    6. 06

      Monitor and review

      Re-score when systems, suppliers or threats change, and at least once a year for DORA and ISO 27001.

    Every risk on one heatmap

    A heatmap puts likelihood against impact so the risks that matter jump out. Drimt scores and ranks each risk automatically and shows inherent risk (before controls) next to residual risk (after controls), so you can prove your measures actually reduce exposure.

    • Inherent and residual scores side by side for every risk
    • Risks ranked by severity, with owners and treatment deadlines
    • Duplicate risks across projects detected and merged
    • Board-ready export of the top risks and their trend

    Start from what is really on your network

    Most risk registers miss the assets nobody listed. Drimt connectors and network discovery find devices, services and cloud resources, then rank them by exposure so your assessment starts from reality, not memory.

    • Network and cloud asset discovery with risk ranking
    • Connectors keep the register current instead of a once-a-year export
    • Supplier and third-party risks tracked next to your own assets

    One assessment, mapped to every framework

    Run the risk analysis once and reuse it as evidence for each regulation that asks for it.

    • ISO/IEC 27001:2022 — clauses 6.1.2 (assessment), 6.1.3 (treatment), 8.2 and 8.3
    • ISO/IEC 27005:2022 — guidance for information security risk management
    • NIS2 — Article 21(2)(a) risk analysis and Article 20 approval by management bodies
    • DORA — Articles 6 to 8: ICT risk management framework, identification and classification
    • GDPR — Article 32 security of processing and Article 35 data protection impact assessments (DPIA)

    How Drimt helps

    Living risk register

    Risks, owners, treatments and evidence in one workspace, updated by your connectors.

    Automatic scoring

    Likelihood × impact scoring with inherent and residual views, ranked for you.

    Framework mapping

    Each risk linked to NIS2, ISO 27001 and DORA requirements and to the controls that treat it.

    Board reporting

    Top risks, trends and treatment status exported as an audit-ready report.

    Cybersecurity training for teams

    Frequently asked questions

    How often should we run a cyber risk assessment?

    At least once a year, and whenever something significant changes: a new system, a new critical supplier, a merger or a major incident. ISO 27001 requires assessments at planned intervals and DORA requires the ICT risk framework to be reviewed at least yearly.

    Qualitative or quantitative risk assessment?

    Most organisations start qualitative, with a 1–5 likelihood and impact scale, because it is fast and consistent. Quantitative methods that express risk in euros are useful for the biggest risks and for board discussions; Drimt's CFO module adds a euro exposure view on top of the scores.

    What is the difference between inherent and residual risk?

    Inherent risk is the score before any controls; residual risk is what remains once your controls are in place. Auditors look at both to see whether your measures actually work.

    Is a DPIA the same as a risk assessment?

    No. A GDPR data protection impact assessment focuses on risks to people's rights and freedoms for a specific processing activity. A cyber risk assessment covers risks to your organisation's systems and services. They should share data, but they answer different questions — which is why DPOs and CISOs benefit from one register.

    Who has to approve the risk assessment under NIS2?

    Article 20 of NIS2 makes management bodies approve the cybersecurity risk-management measures, oversee their implementation and follow training. They can be held liable for infringements.

    See your top risks in one session

    Book a demo and get a free audit scan: we map your assets, score your first risks and show where your exposure is highest.