Run a restore drill in an isolated environment →
A repeatable drill you can run on one service with its owner present, producing a measured recovery time and a written finding.
Each exercise has a scope to agree and a written result at the end. Work within an approved test environment.
A repeatable drill you can run on one service with its owner present, producing a measured recovery time and a written finding.
An enrolment sequence for a small group of administrative accounts, with recovery designed before the first credential is issued.
A structure for service documentation, plus the test that tells you whether it is finished.
Turn a vague estate list into a per-edition view with owners and deadlines attached.
Start with a credible scope, a funded plan and an honest understanding of what the certificate proves.
Reconcile devices, services and access paths before deciding which controls you need to prove.
Turn defaults and inherited settings into a controlled baseline, then check what devices actually enforce.
Build an update process that includes applications, remote devices and proof of installation.
Prove who can sign in, what they can do and whether protection is actually enforced.
Check effective protection across the estate and turn technical results into answers you can defend.
Connect each answer to current evidence and give the signatory a declaration they can understand.
Make the whole estate ready for independent testing and understand the 2026 consequences of incomplete patch remediation.
Understand the standard, the certification route and the work that IT should—and should not—own alone.
Define a management system around real services and dependencies, including the issues outside IT's direct control.
Connect business consequences to controls, with owners and a record of what is actually implemented.
Turn access, patching, changes and recovery into repeatable controls without creating a second helpdesk.
Close the gaps between technical controls and the business processes that depend on them.
Find weaknesses while you can still fix them, and give leadership decisions rather than a ceremonial presentation.
Prepare people and evidence for the first certification audits, including awkward questions and honest gaps.
Fix causes, verify that changes work and keep the ISMS useful after certification.