Your path to cyber resilience.

Prezilient designs and runs cyber exercises that prepare leaders and technical teams for a real incident.

Choose a tabletop exercise, cyber range, CTF or cyber lab. Each ends with a written record of what happened, what should change and who owns each next step.

Discuss your requirements See the four formats

T+00:00Start
T+00:07Inject 01 Unusual sign-ins reported
T+00:18Inject 02 File server unavailable
T+00:33Decision 01 Isolate the affected segmentOwner: IT operations
T+00:46Inject 03 A journalist asks for comment
T+01:04Decision 02 Agree the holding statementOwner: Communications
T+01:28Debrief Findings, owners, next steps

T+01:30Exercise clock
90 minutes

University and research partners

Prezilient is an Óbuda University spin-off, grown out of our research and teaching.

Who it is for

Your team's first real incident should not be its first rehearsal.

For security, technology and L&D leaders.

Who takes part

Leadership teams
Security teams
Technical teams
Cross-functional incident teams

Four formats

Choose a format for what your team needs to practise.

The formats cover different skills, from incident decisions at a table to practising one technique in a lab. We help you choose one and shape it around your people and environment.

To practise: incident decisions

Tabletop Exercises

Decisions under pressure.

Leadership
Executives and crisis roles work through escalation, communication and continuity.
Technical
Security and IT teams work through triage, containment and recovery decisions.
Combined
Both groups in one scenario, including the handovers between them.

A facilitator walks the room through an unfolding incident, adding new information as it goes. The group decides what to escalate, how to keep operating and what to say, and agrees who owns each decision.

Who takes part: Leadership and cross-functional incident teams

Ask about a tabletop exercise

To practise: hands-on incident response

Cyber Range

Focused scope. Connected complexity.

Scoped
One focused task in a bounded environment, such as investigating and containing a single compromised server.
Complex
Several connected systems. Actions in one zone show up in another, so the team practises the response end to end.

Your team investigates and responds at the keyboard inside a replica environment, built for the exercise and kept separate from your live systems.

Who takes part: Security and technical response teams

Ask about a cyber range exercise

To practise: individual skills and teamwork

CTF

Jeopardy and Attack–Defence.

Jeopardy
A board of challenges by category and difficulty. Teams or individuals solve, score and choose the next one.
Attack–Defence
Every team runs the same services. Keep yours available and patched while you probe everyone else’s.

Capture the Flag is a competition. Teams or individuals solve technical challenges; each solved challenge reveals a flag, a code that earns points. In Attack–Defence, teams also keep their own services running while the others probe them.

Who takes part: Individuals and technical teams

Ask about a CTF event

To practise: one technique, repeated

Cyber Labs

Targeted practice, built around the skills you need.

Linux
Permissions, services and log review
Web
Input handling, sessions and access control
Windows
Event logs, accounts and persistence
SOC tools
Alert triage and investigation in a SIEM
Forensics
Disk, memory and timeline artefacts
Custom
Built around your own stack and objectives

Pick a scope, such as Linux, Web or SOC tools, and work through tasks in a lab built for it. Each task is a loop: attempt, feedback, retry, then a check that confirms the skill.

Who takes part: Technical teams practising one focused skill

Ask about a cyber lab exercise

How it works

Four steps from scope to debrief.

Three things shape every exercise: who takes part, what they need to practise and the environment they work in. The steps below turn them into a scenario, a run and a written record.

Scope
Together we agree who takes part, what they need to practise and what evidence you want at the end.
You leave withObjectives and participants
Design
We build the scenario, the environment, the challenge board or the practice path around your objective.
You leave withScenario and environment
Run
Participants work through the exercise while we facilitate, observe and adjust as it unfolds.
You leave withDecisions and actions on record
Debrief
We walk through the exercise with everyone who took part and agree the findings.
You leave withFindings, owners and next steps

Before you get in touch

Who will take part?: Roles, experience and what they need from the session.
What needs practice?: A decision, a response or a technical skill.
What should we plan around?: Your timing, your environment and any constraints.

Evidence

A written record with owners and next steps.

The debrief turns what happened into findings your team can act on. You decide what the record must show when the exercise is scoped, so it answers the objective you set.

What happened?: The decisions, actions and information available at the time.
Why did it matter?: How each observation relates to the objective you set.
What should change?: Responsibilities, coordination or skills that need attention.
What comes next?: Where further practice or a change of approach will help.

Exercise record

Scenario: file server unavailable (Tabletop exercise, Combined variant)

Exercise record: Illustrative example, not client data
ID	Finding	Owner	Next step
F-01	Escalation to the crisis lead took longer than the plan allows.	Head of IT operations	Name an out-of-hours deputy and rehearse the call tree.
F-02	The holding statement was delayed by a legal review that had not been scheduled.	Communications lead	Pre-approve two holding statements with legal.
F-03	The decision to isolate the segment was made quickly and everyone knew the reason.	Security operations	Keep this practice and write down the criteria behind it.