Security Management & Resilience
We help prepare your organization for an incident - before it happens
We develop incident response plans, create playbooks, run tabletop exercises, and assess organizational readiness. We work in line with NIST SP 800-61r3 (2025) and IEC 62443-2-1, incorporating the three-stage NIS2 notification timeline: 24-hour early warning, 72-hour incident notification, and one-month final report.
- 5
- 8+
Security Management & Resilience
- Incident readiness assessment
- Incident response plan development (IT + OT)
- Playbook creation for key scenarios
During an incident, what is usually missing is what could have been prepared beforehand: logs, an inventory of systems, agreed roles and contacts. NIS2 adds a notification timetable for significant incidents: an early warning within 24 hours of becoming aware, an incident notification within 72 hours with an initial assessment of severity and impact, and a final report on the root cause and the mitigation applied no later than one month after the notification. OT brings its own constraints: the safety of people and plant comes first, then the availability and integrity of the process, and data confidentiality last. Restoring a PLC means loading a verified copy of its program and configuration and checking the process, and forensics on legacy systems is limited. We help you build response capability and test it in exercises before a real incident arrives.
Scope of the service
Incident readiness assessment - analysis of existing procedures, detection tools, and response capabilities
Incident response plan development (IT + OT) - aligned with NIST SP 800-61r3 and CSF 2.0
Playbook creation for key scenarios: ransomware, data breach, OT/SCADA attack, insider threat, supply chain compromise
Tabletop exercises at three levels: strategic (C-level, crisis communication), tactical (SOC/IT, detection and escalation), operational (OT engineers, segment isolation and recovery)
Crisis communication plan - internal (board, employees) and external (regulator, media, customers)
Notification procedures for significant incidents under NIS2 as transposed into national law: 24h early warning, 72h incident notification and a final report one month after the notification; for financial entities, also major ICT-related incident reporting under DORA
Post-incident review framework - root cause analysis, lessons learned, plan updates
IR plan integration with OT environments per IEC 62443-2-1 - accounting for availability priorities, limited maintenance windows, and industrial forensics constraints
How we work, step by step
Readiness assessment
We analyse existing procedures, roles, tools, and detection capabilities. We verify alignment with NIS2 and IEC 62443-2-1 requirements. We identify gaps in readiness.
Plan development
We create an IR plan tailored to the organization - with clear roles, escalation paths, communication procedures, and regulatory notification timelines. We account for OT-specific requirements.
Playbooks
We prepare playbooks for the most critical threat scenarios - step by step, with checklists, assigned owners, and target response times. Separate playbooks for IT and OT incidents.
Tabletop exercises
We run incident simulations at three levels: strategic (board - decision-making and crisis communication), tactical (SOC/IT - detection, analysis, escalation), and operational (OT engineers - network segment isolation, evidence preservation, recovery). We test the plan under controlled conditions.
Review and improve
We analyse exercise results, identify areas for improvement, and update the plan. We deliver a continuous improvement framework that keeps the IR plan in step with changes in the organization and its environment.
What a playbook from us looks like
A policy says an incident must be reported. A playbook says who does it, when and how. Every playbook has these parts:
- Scenario
- Each playbook covers one event, for example ransomware, a data breach, an attack on OT/SCADA systems or a supply chain compromise.
- Owners and escalation
- Every step has an assigned owner, and the playbook sets out the escalation path.
- Steps with response times
- The checklist goes step by step and gives the time allowed for each step.
- Notifications
- The reporting timetable for the CSIRT and the regulator covers the early warning within 24 hours, the notification within 72 hours and the final report within a month. Financial institutions follow the DORA deadlines.
- OT section
- Separate OT steps describe isolating a segment with process continuity in mind, securing evidence on legacy systems and the order of recovery.
- Communication
- The playbook states who tells what to the board, staff, customers and the media.
Who we serve
We've worked with national energy grid operators, systemically important banks, industrial automation manufacturers, renewable energy operators, and US DoD contractors.
Not sure this service fits your situation? Describe your environment and deadline in a few lines and we will propose a scope. We reply within one business day.
Frequently asked questions
How does an IR plan differ from a security policy?
A security policy defines general principles and requirements. An IR plan is an operational document that specifies who does what and when during an incident - with concrete procedures, checklists, and assigned owners. A policy says 'incidents must be reported'. An IR plan says 'John Smith calls the CSIRT within 24 hours at number X, using form Y'.
Do you help during an incident that is already underway?
Yes, we also support clients during an incident: analysis, containment and recovery decisions. Experience shows, however, that this works best when we have first run a short preparation project together. During an incident, the data needed to manage it is usually missing: logs, an inventory of systems, agreed roles and contacts. Preparation puts these in place beforehand, so when something happens we work from facts from the first hour.
What do tabletop exercises look like?
Tabletop exercises are facilitated incident simulations where the client's team walks through a scenario step by step. We run them at three levels: strategic (board - decision-making and crisis communication), tactical (SOC/IT - detection, analysis, escalation), and operational (OT engineers - network segment isolation and recovery). No production systems are required.
Why does OT incident response require a different approach?
In OT environments the safety of people and plant comes first, and the integrity and availability of the process take precedence over data confidentiality. A PLC is not restored like a workstation: a verified copy of its program and configuration has to be loaded, often during a shutdown window, and the process checked. Forensics on legacy systems (for example Windows XP stations) is limited because devices log little, and a quick return to operation often conflicts with preserving evidence. Isolating an OT network segment may halt a production line. The IR plan must account for these constraints - which is why we work in accordance with IEC 62443-2-1.
What are the NIS2 incident notification deadlines?
Under Article 23 of NIS2, a significant incident has three mandatory stages: an early warning within 24 hours of becoming aware of it; an incident notification within 72 hours with an initial assessment of severity and impact and, where available, indicators of compromise; and a final report no later than one month after the notification, covering the incident, its likely root cause, the mitigation applied and any cross-border impact. The CSIRT may also request an intermediate report. If the incident is still ongoing when the final report is due, the entity submits a progress report and then the final report within one month of handling the incident.
What is NIST SP 800-61r3?
It is the updated NIST incident response publication released in 2025 - the first revision since 2012. The key change is alignment with NIST Cybersecurity Framework 2.0 and its six functions: Govern, Identify, Protect, Detect, Respond, Recover. Instead of a four-phase incident lifecycle, the new model recognizes that incident preparation is an ongoing element of cybersecurity risk management.
How often should the IR plan be tested?
We recommend tabletop exercises at least once a year and after any significant change in infrastructure or regulations. Organizations in regulated sectors (energy, finance) should consider semi-annual exercises.
What does the price of an incident response plan depend on?
The number of days depends on whether the plan covers IT, OT or both, how many playbooks you need, at how many levels we run tabletop exercises (strategic, tactical, operational) and how many sites there are. The price is the estimated days times the daily rate, broken down by stage from the readiness assessment to the post-exercise review. We agree the scope on a free call.
Related sectors, services and insights
Sectors
- Banking and financeWe test a bank's digital channels and run red teaming aligned with the TIBER-EU methodology.
- EnergyWe check whether the operational network can be reached from the IT network or over VPN.
- Manufacturing and industryWe secure older automation too, and plan tests together with your maintenance team.
Services
- Cybersecurity TrainingEach group gets its own programme, and we measure the effect, e.g. with simulated phishing.
- NIS2 Compliance AuditWe establish whether NIS2 applies to you and which security measures are still missing.
- OT Security AssessmentWe show which paths lead to your controllers and what to fix first.
Articles
- Ransomware - what it is, how an attack unfolds and how to respondHow ransomware works: encryption and data theft, the course of an attack, the RaaS market, impact on OT, CISA response steps and NIS2 reporting duties.
- Incident Response Guide for Small Business - 5 StepsFive steps for responding to an incident in a small business: preparation, identification, resolution, reporting, and lessons learned.
We'll discuss scope, methodology, and timeline.
Free consultation, no strings attached.








