4.2

Cyber Readiness

Security awareness and incident response for public teams

Public-sector systems are targeted precisely because they hold citizen data. This programme builds practical security awareness across staff and rehearses incident response with the people who would actually handle it.

Scope[DEPARTMENTS IN SCOPE]
Duration[e.g. 4-8 WEEKS]
Staff covered[NUMBER OF STAFF]
Exercises[TABLETOP / TECHNICAL]

What makes it different

Threats staff actually face

Built around phishing, credential handling and data exposure as they occur in public-sector work, not abstract threat theory.

Response rehearsed, not documented

Incident response is practised as an exercise. Plans that have never been run tend to fail on first use.

Role-appropriate depth

Frontline staff, administrators and technical teams receive different content matched to what they can actually act on.

Measured before and after

Susceptibility is measured, so improvement is demonstrable rather than asserted.

What you get

  • Baseline awareness assessment
  • Role-specific awareness training
  • Simulated phishing exercise
  • Incident-response tabletop exercise
  • Response playbook review
  • Post-programme readiness report

How it works

  1. 01
    Baseline

    Current awareness and susceptibility measured across the department.

  2. 02
    Role-based training

    Content delivered at the right depth for frontline, administrative and technical staff.

  3. 03
    Simulation

    Controlled phishing or social-engineering exercise to test practice, not memory.

  4. 04
    Response exercise

    A tabletop incident run with the people who would handle a real one.

  5. 05
    Report

    Readiness findings and prioritised recommendations for your leadership.

Who it is for

Government departments

Raise baseline security practice across a large, non-technical workforce.

Public service delivery teams

Protect citizen data handled in day-to-day operations.

Departmental IT teams

Rehearse response with the wider organisation, not in isolation.

Common questions

Yes. It is controlled, agreed in advance with your leadership, and designed to measure practice without penalising individuals.
Especially non-technical staff. Most successful intrusions begin with an ordinary user action, not a technical exploit.
Not as part of this programme. This covers awareness and response readiness. Technical testing of live systems is a separate, separately-authorised engagement.
Measured change in susceptibility, findings from the response exercise, and prioritised recommendations.
More for government

Other services in this group

Not sure which programme fits?

Tell us the department, the population you need to reach and your timeline — we will recommend the right delivery model, even if it is not this one.

Talk to our public-sector team