THIRTEEN DELTA BOUTIQUE CYBERSECURITY START THE CONVERSATION

Free incident response readiness scan

A self-assessment with 41 statements on what you arrange before an incident. They come from our cyber crisis and incident response playbook and from our workshops, and together they are the bare minimum for incident response readiness. You can fill it in on your own in about twenty minutes and see per area where you stand and where to start. Where you don't know the answer, choose 'not sure' and check it later with the people who know.

No sign-up. Your answers stay in your browser, so print or save your results before you close the page.

START THE SCAN THE FREE TEMPLATE

How to answer.

Yes

It is in place, and you could show it today.

Partly

It exists, but is incomplete, out of date or untested.

No or not sure

It is not in place, or nobody knows. Both count as a gap, and every 'not sure' is worth checking.

Statements marked FIRST HOURS decide how the first hours of an incident go. Your results show per area what is in place, and which sections of our free incident response plan template cover the rest.

The scan covers the bare minimum. The statements come from chapter 15 of our playbook, Staying ready, and from what our tabletop exercises test. They line up with the public guidance of NCSC-NL, NCSC-UK and CISA on preparing for an incident. A full score means the basics are in place. The scan says nothing yet about your sector, your suppliers or how your plan holds up under pressure, and it doesn't replace an audit.

The plan and the crisis team

7 STATEMENTS

A written incident response plan exists, approved by management, with copies outside your own IT: on paper and in a separate cloud location.
FIRST HOURS The crisis roles are named, each with a deputy, and both can be reached outside office hours. The roles are the crisis chair, the operational lead, the communication owner, legal and privacy, the scribe who keeps the decision log, and HR.
FIRST HOURS One role has written authority to declare a crisis and convene both crisis teams, with the thresholds agreed.
Three severity levels are agreed, and anyone may raise the alarm at the highest level without asking permission.
The main decisions are authorised in advance, in writing: emergency spending, disconnecting systems, engaging the incident response partner and a negotiator, notifying regulators, insurer and police, and approving external statements.
An operational and a strategic crisis team are defined, each with its own people and an agreed meeting rhythm.
Scenario plans are adapted to your three to five main threats, with your own systems and numbers.

Outside help and contacts

7 STATEMENTS

FIRST HOURS You know which incident response firm you would call, and a second firm in case the first has no capacity. Their emergency numbers are in the contact tree, and your insurer accepts both.
You know what each firm on your list offers: its response time, and how fast it can deploy its own tooling. You also know whether it covers threat hunting (searching for what your alerts missed) and a compromise assessment (an independent check that the adversary has gone).
Your cyber insurer's emergency line, notice period, consent rules for spending and panel requirements are known and written in the plan.
FIRST HOURS An out-of-band channel for the crisis team is set up on private devices and has been tested, with a meeting place outside your own Microsoft 365 or Google environment.
The offline contact tree is complete, with two people and two ways to reach each role and a way to reach all staff. It is printed, stored off the network and was checked in the last six months.
The contacts and portals of your national computer security incident response team (CSIRT), the data protection authority and the police cybercrime unit are known in advance.
For each IT provider with admin access, you hold your own copy of the admin passwords and every provider account uses multi-factor authentication (MFA). The contract obliges the provider to report its own incidents to you promptly and gives you the right to forensic reports. You have tested how to cut the link.

Communication

4 STATEMENTS

Holding statements are prepared for each audience, staff, customers, people whose data is affected and the press, and approved by legal and communication.
One spokesperson is named for the outside world, and everyone else knows to refer questions to that person.
You have a short list of crisis communication specialists or agencies you could call, with their numbers in the contact tree, and you know which one you would call first.
You have a plan for data theft without encryption. It says how you find out whose data it is, who writes the notice to affected people, who staffs the phones and whether anyone engages with a leak site.

Legal and the deadlines

3 STATEMENTS

FIRST HOURS The reporting map is filled in, with an owner for every filing that applies to you. That can include the NIS2 early warning within 24 hours, the notification within 72 hours, the final report and the GDPR notification, where feasible within 72 hours. It can also include the Digital Operational Resilience Act (DORA), the Cyber Resilience Act and the Critical Entities Resilience (CER) Directive.
The pay-or-rebuild question has been discussed with the board in advance and the decision tree is drawn. That includes your position on paying when backups don't help, because the data was stolen.
The person who files your reports can still reach the reporting portals without a company mailbox or laptop. You are registered with your national authority where the law requires it.

Detection and evidence

7 STATEMENTS

Every type of alert has a named person as its owner, and someone reads alerts out of hours.
Mail sent to your info@ and abuse@ addresses reaches security quickly, and every employee knows where to report something suspicious.
FIRST HOURS Endpoint detection and response (EDR) runs on servers and endpoints, and its coverage is measured against your asset list. You know which devices it cannot cover, such as firewalls and other appliances.
Logs are collected centrally, out of the adversary's reach, and kept for six months or more. You know how long each source is kept, and everything is on one clock, Coordinated Universal Time (UTC).
An evidence kit is ready: clean media, the means to capture memory and images, and a custody-log template. Triage collection tooling, which gathers the most useful forensic data from a system in minutes, is ready to deploy, either your own or your incident response partner's.
FIRST HOURS A decision-log template is ready, a scribe is named to keep it, and timestamps are in Coordinated Universal Time (UTC) from the first minute.
You know which of your devices face the internet, such as VPNs and firewalls, and patches for them come first. Someone follows the security advisories for these devices, and an advisory is treated as a possible incident.

Containment and access

7 STATEMENTS

FIRST HOURS You can disable accounts and revoke sessions and tokens across the whole environment today, and someone knows the exact steps.
Admin and service accounts are inventoried, and administrators use separate accounts for admin work. The most important accounts, administrators and finance, use phishing-resistant MFA, such as passkeys, and weaker sign-in methods are switched off for administrators.
The containment measures are built and tested in advance. They include host-firewall policies that block traffic between workstations, and the removal of administrative shares and the old SMBv1 file-sharing protocol. The Local Administrator Password Solution (LAPS) runs on workstations, and the cut-off for supplier and VPN access has been rehearsed.
Two emergency (break-glass) admin accounts sit outside single sign-on. Their credentials and your disk recovery keys, such as BitLocker keys, are stored offline and tested.
Your service desk checks identity before every password or MFA reset, in person or with a callback to a number already on file.
Staff know that IT never asks for a password or an MFA code. It never asks them to approve a sign-in they did not start, or to install remote-access software. Only approved remote-access tools run on your systems, and an alert fires when another one appears.
Unusual payments and access requests are confirmed by calling back a number you already hold, and urgent payments need a second person.

Backups and recovery

3 STATEMENTS

FIRST HOURS Backups are offline or immutable, and a real restore was tested in the last quarter.
FIRST HOURS Backup consoles and the virtualisation platform run on their own credentials outside Active Directory, with MFA and alerts on deletion and purge jobs.
The processes that must not stop are named, each with a tolerable downtime. The recovery order is written in the plan, based on a business impact analysis (BIA), and IT knows it.

Practice and upkeep

3 STATEMENTS

Helpdesk staff and system administrators know the first-hour do's and don'ts. Isolate, and power off only to stop active destruction. Don't wipe or reinstall, upload samples to public sites or AI tools, or discuss the response in email or chat.
A tabletop exercise with executives in the room took place in the last twelve months.
The plan is reviewed after every incident, exercise and major change, and at least once a year; findings become tasks with an owner and a date.
FAQ

Frequently asked questions.

Is the scan free?

Yes. There is no sign-up and no email address to leave. You see your results on screen straight away, and you can print them or save them as a PDF.

What happens to our answers?

They stay in your browser and are gone when you close the page. We don't receive your answers or your score. We only count how often the scan is started and finished, as part of our visitor statistics.

Who should fill it in?

Someone with an overview, such as the CISO, the IT lead or a crisis coordinator. It works well with IT, legal and communication in the same room, because gaps often sit between those roles.

Is there a Dutch version?

The scan is in English, like the free template it refers to. We work with you in Dutch or English, and there is a short introduction in Dutch.

How is the score calculated?

Yes counts in full and partly counts as half. Everything else counts as zero, including statements you leave open, so the score is always out of all 41 statements. Where the gaps sit tells you more than the percentage, so start with the areas.

Where do we start if we have many gaps?

With the statements marked FIRST HOURS. Your results show how many of them are in place and which sections of our free template cover the rest.

Can you help us with the results?

Yes, that is what our advisory work is for. We go through the results with you and agree the order in which to close the gaps. That becomes a readiness plan with an owner and a date for each item. We then help you carry it out, and the full playbook and a tabletop exercise on your own plan are part of that work. The usual way to start is a free conversation of 30 to 60 minutes, without obligation.

Does a high score mean we comply with NIS2?

A scan can't tell you that. This one looks at incident response readiness, which helps you prepare the incident handling and reporting that NIS2 asks for. Whether your organisation meets its duties depends on all your measures together, and is ultimately for your supervisor to judge.

May we share the scan?

Please do. Send the link to colleagues, your management team or organisations you work with, or link to this page from your own site.

CONTACT

Start the conversation.

A keynote, the First Responder Workshop or its board version, the Board & Executive Workshop, or just a hard question you'd like a straight answer to. Tell us what you're facing and we'll find the right format together, in the Netherlands, abroad or remote. You speak with the expert directly, and in confidence.

info@thirteen-delta.com FOLLOW US ON LINKEDIN

Active incident? HOW WE CAN HELP