Skip to content

Esta página también está disponible en español.

Ver en español
Almenara

Incidents · Incident management and reporting

When something happens, you will know what to report, to whom and by when

A serious incident leaves hours for the first report, not days. Almenara helps you classify it, keeps each regime’s deadline in view and prepares every report from what is already recorded. Your lead reviews it and sends it.

One incident, every deadline

Tell us what you are and what happened. The calculator says which reports you have to prepare, for whom and by when. They all come from the same incident record.

What you are

What happened

5 reports · 2 authorities · next in 4 h

Sample data

By deadline

Who to notify

DORA
Major: critical service affected and unauthorised access to data.Reglamento Delegado (UE) 2024/1772, art. 8.1 y 9
GDPR
Personal data breach: notify the AEPD.Reglamento (UE) 2016/679 (RGPD), art. 33.1 y 34.1

Sample data A payment institution of 90 people. Ransomware encrypts the payment reconciliation system for 9 hours, with possible access to customer data. Indicative deadlines and thresholds, with their source. Not legal advice.

The incident, from start to finish

The calculator’s case, step by step. Every report comes from the record as it fills up; nothing is written twice.

Sample data

  1. T0

    Detection

    The reconciliation system stops responding: the files are encrypted. The incident record is opened.

  2. 2 h

    Classified as major

    Each framework’s criteria are assessed with what is recorded.

    AI proposes
    Proposes the classification under each regime: critical service affected and data access, major for DORA; personal data breach for the GDPR.

    A person decides
    The security lead reviews and confirms it. The deadlines start from that moment.

  3. 4 h

    Containment

    The affected servers are isolated and compromised access is cut.

  4. 6 h

    Initial notification

    Almenara prepares it from the data in the record; the security lead reviews it and sends it to the Bank of Spain.

  5. 9 h

    Recovery

    The Continuity playbook is followed: restore from backup and back to service.

  1. 78 h

    Intermediate report

    With containment and recovery already recorded. The AEPD received the breach notification before 72 h.

  2. 1 month

    Final report

    Root cause, final impact and measures, from the latest intermediate report.

  3. 1 month

    Post-incident review

    What worked, what didn’t and what changes. Signed off by management.

  4. 1 month

    Actions in Compliance

    Corrective actions and the evidence for 5.24–5.28 stay in Compliance.

  5. Next review

    Annual drill

    The scenario goes into the next incident drill.

The reports that don’t go to an authority

The same record also produces the reports for your management, your suppliers and your clients.

Sample data

Summary for management

To
The CEO and the management committee
When
From classification, updated with each report
Includes
  • Status and impact, on one page
  • The decisions that are theirs: do we notify clients? Do we activate the continuity plan?
  • Their obligations, which under NIS2 belong to management

AI proposes the draft from the record; the security lead reviews and approves it.

Post-incident report

To
Management and the teams involved
When
When the incident is closed
Includes
  • Full timeline
  • Root cause and lessons learned
  • Actions with an owner and a date

AI proposes the draft from the record; management reviews and approves it.

What sits behind every report

One record, every report

The incident is recorded once. The classification under each framework, the deadlines and the fields of each report come from there.

Spanish formats

Templates with the fields each authority asks for: Bank of Spain, INCIBE-CERT, CCN-CERT and AEPD.

Ready for each channel

Almenara prepares the report; sending depends on each authority’s channel, and when and who sent it is recorded.

Continuity playbooks

If the incident stops a critical process, the playbook says who does what and in which order things recover.

It starts at a supplier

The incident arrives linked to its profile in Suppliers, and the supplier answers through its portal.

Post-incident review

Timeline, root cause and lessons, with actions followed until they are closed.

Evidence for Compliance

Every closed incident leaves evidence for ISO 27001 controls 5.24 to 5.28, ready for the auditor.

Is it major?

Three questions and we tell you under which frameworks you would have to notify.

What are you?
Is a critical service affected?
Is personal data compromised?

With your answers

DORA
Major: critical service affected and unauthorised access to data.
GDPR
Personal data breach: notify the AEPD.
See the deadlines in the calculator

Indicative. For DORA, the other criteria use the sample case values.

See it before you talk to anyone

  • Demo

    Your cloud provider goes down

    Your cloud provider goes down at 09:12: you see whether it is serious, which deadlines are running and the draft report ready for your lead to review and send.

    Walk through the case

What the platform does and what our team does

With the module, your team does the work and the platform organises it, reminds you and keeps it with its evidence. If you’d rather delegate part of it, our team does it as a fixed-scope service, contracted separately.

Included in the module

What the platform does

  • Records and classifies every event and incident
  • Works out what must be notified, to whom and by when under DORA, NIS2, the ENS and the GDPR
  • Prepares the initial, intermediate and final reports from what is already recorded; your lead reviews them and sends them through each authority’s channel
  • Keeps the lessons learned from every closed incident
Separate service

What our team does

  • Incident response exerciseEvery year

    A full incident response exercise, with the notification to the authority prepared as if it were real.

  • Incident response playbooksOnce

    Five response playbooks for the most likely incidents in your organisation.

  • Post-incident reviewWhen needed

    When a real incident happens, we analyse the causes, the response and what needs to change.

See the full service catalogue

And every report comes from the same record, whatever the regime: NIS2, DORA, Spain’s National Security Framework (ENS) or the General Data Protection Regulation (GDPR).

See it with your own data

Ask for information or a meeting: in 60 minutes we load a sample of your data and you see it working.