Business-Led Priorities
Link recovery decisions to critical services, tolerable disruption and operational dependencies.
ISO 22301 cyber resilience
Prepare for disruption.
Protect critical services.
Recover with confidence.
Connect continuity planning, incident response and recovery around the services your business depends on. Cyber360 helps you identify dependencies, agree recovery priorities and exercise the plans before an incident puts them under pressure.
Standards & assurance • Clear scope. Practical evidence.
Understand → Improve → Validate
From questions to decisions
Keep the business objective in view.
Resilience is more than having a backup. People need to know what must continue, what can wait, who makes decisions and how a safe recovery will be demonstrated. We bring those questions together into practical plans and exercises.
Plans Teams Can Use
Clarify response authority, recovery sequences and stakeholder communications.
Evidence From Exercises
Expose assumptions and record improvement actions through controlled, agreed tests.
When it adds value
Focus effort where it can make a difference.
A New Assurance Requirement
Clarify the business objective, scope and evidence expected by stakeholders.
A Changing Environment
Review the impact of new services, technology, suppliers or operating practices.
Unclear Ownership
Connect decisions and controls with named owners and practical responsibilities.
Preparing for Improvement
Establish a baseline and prioritise actions around risk and delivery dependencies.
Service areas
A structured path to practical improvement.
These are examples for scoping, not an all-inclusive package. Technologies, delivery expertise, access requirements and outputs are confirmed before an engagement.
01
Business Continuity Planning
What must keep working?
- Example scope
- Critical services, people, suppliers, facilities and business-impact assumptions.
- What we examine
- Continuity options, minimum operating needs, workarounds and escalation ownership.
- Evidence to take away
- A continuity plan and prioritised dependency map.
02
Disaster Recovery
Can systems return in the right order?
- Example scope
- Selected applications, infrastructure, identity services and recovery dependencies.
- What we examine
- Recovery time and recovery point objectives, restoration procedures and failover assumptions.
- Evidence to take away
- A recovery strategy, runbook actions and validation plan.
03
Incident Response Readiness
Who decides and acts during an incident?
- Example scope
- Incident roles, escalation, containment authority and response playbooks.
- What we examine
- Decision paths, hand-offs, evidence preservation and coordination with recovery teams.
- Evidence to take away
- Response playbooks and a tabletop exercise plan.
04
Ransomware Recovery Readiness
Could you restore safely after compromise?
- Example scope
- Backup arrangements, isolation, privileged access and selected recovery environments.
- What we examine
- Backup integrity, restoration evidence, clean-recovery dependencies and reinfection risks.
- Evidence to take away
- A readiness assessment and prioritised recovery improvements.
05
Crisis Communications
Can stakeholders receive timely, accurate information?
- Example scope
- Leadership, staff, customers, partners, regulators and media contacts where applicable.
- What we examine
- Approval routes, alternate channels, messaging ownership and notification dependencies.
- Evidence to take away
- A communications plan and scenario-specific message templates.
06
Resilience Exercises & Learning
What do rehearsals actually demonstrate?
- Example scope
- Tabletops, restoration tests and failover drills selected for the agreed objective.
- What we examine
- Observed performance, assumptions, recovery sequence and gaps against agreed criteria.
- Evidence to take away
- An exercise report, lessons and accountable improvement actions.
How it works
A clear path from review to improvement.
- 01
Define Critical Services
Agree business objectives, dependencies and disruption scenarios.
- 02
Assess the Readiness
Review continuity, response, backup and recovery evidence.
- 03
Set Recovery Priorities
Agree objectives, sequencing, owners and operational constraints.
- 04
Develop Usable Plans
Build or update agreed runbooks, playbooks and communications.
- 05
Exercise Safely
Run the agreed scenario with monitoring, permissions and stop conditions.
- 06
Improve and Repeat
Track actions and schedule revalidation as the environment changes.
What you receive
Clear enough to decide.
Detailed enough to act.
The reporting package is agreed around your audience and the decisions it needs to support.
Leadership & Business Owners
- Business-impact and dependency findings.
- Continuity priorities and recovery objectives.
- Crisis decision and communications responsibilities.
- A phased resilience improvement roadmap.
Response & Recovery Teams
- Agreed continuity, response and recovery playbooks.
- Backup and restoration readiness findings.
- Exercise plan, observations and lessons.
- Action register with owners and revalidation criteria.
Meaningful progress
Track the improvement.
Keep the evidence.
Agree what completion means for each action: an approved design decision, a reviewed configuration, a resolved finding or a demonstrated process. Record owners, dependencies, exceptions and the evidence available.
A closed task is not automatically a validated security outcome. Choose the follow-up review or test that answers the original question, and record what remains unverified.
Preparing the engagement
Start with the right context.
01
Scope & Objectives
- Identify services, systems and the assurance question driving the work.
- Share relevant obligations, stakeholder expectations and target dates.
02
Evidence & Context
- Provide existing policies, risk assessments, architecture and prior findings.
- Identify suppliers and dependencies relevant to the agreed scope.
03
People & Ownership
- Nominate business, technical, risk and operational contacts.
- Confirm decision authority and ownership of implementation actions.
04
Delivery & Follow-Up
- Agree work packages, access, constraints and acceptance criteria.
- Scope independent assurance, system changes and active testing explicitly.
Reference guidance: NIST: cyber resiliency guidance. Relevant practices are selected for the agreed scope; independent assurance and implementation boundaries are confirmed during scoping.
Clear boundaries
Know what the work establishes.
The engagement applies to the agreed scope and evidence. Your organisation retains responsibility for decisions and control operation. Independent audits, certification or attestation, specialist legal advice, production changes and active testing are separately agreed; outcomes are not guaranteed.
ISO 27001
Build a practical information security management system.
Explore the service →Data Privacy & Protection
Connect governance with personal-data risk and operations.
Explore the service →Defensive Security
Review security architecture, controls and operational readiness.
Explore the service →Practical questions
Before we get started.
Is this the same as disaster recovery?
No. Disaster recovery focuses on restoring technology. Cyber resiliency also addresses critical business services, people, suppliers, response decisions and adaptation.
Will you test production failover?
Only where explicitly scoped and approved. We agree safeguards, dependencies, monitoring, rollback and stop conditions before any disruptive test.
Do backups guarantee recovery?
No. Availability, integrity, access, restore procedures and clean environments need to be considered and tested within the agreed scope.
Is red teaming included?
No. Active adversary simulation is separately scoped and authorised. It can complement resilience exercises where it answers a defined question.
Take a closer look
The service overview,
ready to share.
Download the Cyber360 ISO 22301 Cyber Resilience brochure for the service scope, engagement approach, deliverables and preparation guidance.
PDF · 4 pages · 520 KB
Your next step
Could your critical services withstand the next disruption?
Tell us the decision you need to make. We’ll help define a useful scope.