BrightNTech

Cyber Resilience · re:cyber

Know whether your incident response plan survives a real attack.

Answer 10 questions and see where your response breaks down, before an attacker finds out for you. Mapped to the NIST incident-response lifecycle and NIS2 and DORA expectations.

See it live

Plans from Starter· see pricing

Built on the BrightNTech Trust Layer
Do you have a written incident response plan with named roles and escalation paths?
1

Prepare

Do you have a written incident response plan with named roles and escalation paths?

Is there a 24/7 way to reach the people who can declare and lead an incident?
2

Prepare

Is there a 24/7 way to reach the people who can declare and lead an incident?

Are your critical assets, data flows and third-party dependencies inventoried and owned?
3

Prepare

Are your critical assets, data flows and third-party dependencies inventoried and owned?

How would you first learn you are under attack?
4

Detect & Analyse

How would you first learn you are under attack?

Can you reconstruct what happened from your logs?
5

Detect & Analyse

Can you reconstruct what happened from your logs?

Do you have pre-agreed severity criteria that trigger a defined response?
6

Detect & Analyse

Do you have pre-agreed severity criteria that trigger a defined response?

Can you isolate a compromised system or segment without taking the whole business down?
7

Contain & Recover

Can you isolate a compromised system or segment without taking the whole business down?

When did you last successfully restore critical systems from backup, end to end?
8

Contain & Recover

When did you last successfully restore critical systems from backup, end to end?

Do you run post-incident reviews that produce tracked, closed corrective actions?
9

Post-incident & Governance

Do you run post-incident reviews that produce tracked, closed corrective actions?

Can you meet your regulatory breach-notification duties on time (NIS2, DORA, GDPR 72h)?
10

Post-incident & Governance

Can you meet your regulatory breach-notification duties on time (NIS2, DORA, GDPR 72h)?

0 of 10 answered

The lifecycle

A response is only as strong as its weakest phase.

Most plans look fine on paper and fail at one specific step under pressure. re:cyber checks all four phases of the incident-response lifecycle.

Prepare

Response plan, named roles, on-call reachability, and a current asset and dependency inventory.

Detect and analyse

How fast you would know, forensic-ready logs, and severity criteria that trigger a defined response.

Contain and recover

Isolating a compromise without full shutdown, and a restore you have actually tested end to end.

Post-incident and governance

Reviews that close corrective actions, and meeting NIS2, DORA and GDPR notification duties on time.

1

Assess

Answer 10 questions across the incident-response lifecycle. Scored in your browser, no signup.

2

See the gaps

Get your maturity band and the areas where your response breaks down first.

3

Close them

Work a prioritised remediation path, with rehearsals and playbooks from our resilience team.

Built on the BrightNTech Trust Layer

Your security posture is exactly the data you cannot afford to leak.

A readiness assessment tells an attacker where you are weak. With re:cyber your answers stay in your browser to produce the band, your data stays in the EU unless you choose the region, it is not pooled with other customers, and it is never used to train our models. That is not a feature, it is the foundation.

  • Answers scored client-side by default.
  • No cross-customer data mixing.
  • EU data residency and GDPR alignment.
  • Aligned to NIS2 and DORA obligations.
Visit the Trust Center

Get your readiness report

Your per-question breakdown mapped to NIST, NIS2 and DORA, with a prioritised 90-day remediation path.

Request my report

Resell re:cyber

Run readiness assessments for your own clients under a referral partnership and earn on every engagement.

Become a partner