Cybersecurity and Enterprise Resilience

Security programmes fail in a predictable way: controls are bought, the inventory is incomplete, and nobody has tested what happens when an attacker is already inside. Resilience is the other half and usually the weaker one, because recovery plans are written once and never exercised against a scenario in which the recovery systems are themselves affected. This week treats the two together, from identifying what the organisation cannot operate without to running an incident and getting back. Delegates work from their own environment and leave with a tested plan rather than a document.

It runs 7 times over the published calendar, in 6 cities and live online. Every date is the same programme with the same content and the same certificate.

• Identify what the organisation cannot operate without, and what depends on it.
• Prioritise controls against the way attacks actually arrive rather than against a checklist.
• Detect an intrusion that is already inside the perimeter.
• Run an incident with a defined command structure, including the decisions nobody wants to take.
• Test a recovery plan against a scenario where the recovery systems are affected.

Information security managers and officers, IT managers responsible for infrastructure and recovery, risk and continuity managers, and internal auditors reviewing security.

Short input, then work. Across 5 days of roughly 6 teaching hours each, the balance sits deliberately with the second: a programme where the trainer talks for six hours produces notes rather than capability.

• Your own material

  Exercises run on situations delegates bring, not on a case study written for a different organisation in a different decade.

• A capped cohort

  Small enough that everybody is asked something. Executive programmes are capped tighter still.

• Practice under scrutiny

  The difficult conversation, the challenged assumption, the decision defended out loud. Judgement is not built by watching.

• Something to take back

  Each day ends with a thing you can use on Monday rather than a slide deck you will not reopen.

• A dependency map of the delegate's critical services, with single points of failure named.
• A prioritised control plan tied to the threats the organisation actually faces.
• An incident response and recovery plan with roles, thresholds and a tested escalation path.

A GATI certificate recording what you attended, issued after the programme has run and attendance has been taken. Attending at least 80 per cent of the days earns a certificate of completion; attending less earns a certificate of attendance stating exactly what was attended.

Every certificate carries a code that anybody can check against GATI's own record, which is what makes it worth holding. It records participation. This site will not imply one it does not have.