Supporting technical capability
Review the evidence behind your recovery plan.
A scoped assessment of the available restore history, recovery documentation and access dependencies. An executed restore is included only when explicitly agreed in the statement of work; otherwise the report distinguishes recorded evidence from untested assumptions.
Engagement context
Where this capability applies.
- The board or a cyber insurer asked whether you could recover from ransomware.
- Backups exist but nobody has tested what actually restores.
- You need a realistic recovery time you can stand behind.
The agreed outputs
What the engagement provides.
Ransomware Blast-Radius Map
How far an attack would spread, which staff logins it takes over, and which servers those logins open up.
Restore Proof Pack
What restores, how fast, and what still hurts, with the recovery time measured from your own restore records.
Prioritized resilience roadmap
The gaps to close first, ranked by impact.
Worked example
Ransomware Blast-Radius Map
An illustration of the record an engagement can produce. Names and figures are constructed for this example.
Illustrative content. The engagement record is developed from the client’s own environment and agreed scope.
Commercial & delivery basis
The scope and conditions of the work.
Delivery window
1-2 weeks
Included scope
- Restore evidence for Microsoft 365 and backup data, with a controlled test restore where the statement of work includes one
- Blast-radius map
- Recovery timing supported by available evidence, with untested gaps labeled
- Prioritized resilience roadmap
Scope assumptions
- Your own restore history and recovery documentation are available to review
- A backup platform that is already in place and running
Exclusions
- Full disaster-recovery implementation (scoped separately)
- Production failover
- 24/7 monitoring, detection engineering, live incident response, or forensics
- On-premises, immutable-storage, or cross-platform recovery engineering
- Building a backup platform where none exists, which is its own scoped engagement
Required access
- Read-only access to backup and Microsoft 365 admin
- A test target, if a controlled restore is in scope
- A 30-minute kickoff with IT
Acceptance
The agreed completion standard.
The engagement is complete when the blast-radius map, restore proof pack, and resilience roadmap are delivered and walked through.
Discuss the work
Tell us what you need to change.
Share the systems involved, why the change is needed and your deadline. We clarify the work, responsibilities and information needed for a proposal.
Request an Architecture Briefing