Cyber Defence & Recovery
Can you recover the service your business depends on?
We work with your existing technology team or provider to identify what puts one critical service at risk, agree who should fix it, and witness a restore or rehearse the response. You do not need an artificial intelligence project or a new platform.
The Defence and Recovery Sprint
Start with one service and a recovery target the business owner can sign off.
Agree the service, recovery time, and what must be usable before work resumes. With written authority, review your supplied exposure inventory, relevant vulnerability advisories, privileged and supplier accounts, device coverage, alert ownership, and backups. With your provider, witness one agreed non-production restore where access permits, or record the result as a rehearsal. A rehearsal does not prove a restore.
What a recovery record looks like
- Service
- Dispatch scheduling
- Owner
- Warehouse supervisor, supported by the backup provider
- Recovery target
- Open and check a usable sample dispatch schedule within two hours.
- Observed outcome
- Demonstrated in a test environment: one usable schedule in 74 minutes. Live dispatch was not tested.
- Outstanding fix
- The service desk lead owns the handover to the warehouse team and will rehearse it before the next retest.
What the sprint leaves you with
- A prioritised fix list with owners and due dates
- A witnessed result against the recovery target: demonstrated, missed, or not established
- A record of what was restored, rehearsed, or left untested
- Outstanding risks and a separately scoped retest option
Rehearse our response
Book a standalone exercise or add it to a scoped engagement. Your team and provider work through one realistic scenario using synthetic material.
Facilitated tabletop
Practise declaring an incident, deciding who can authorise containment, communicating when normal channels are unavailable, and handing back to the business owner. Receive a decision log and an action list with owners, dates, and an agreed follow-up.
Scheduled incident readiness and support
Document severity, escalation contacts, decision authority, and the recovery handover. We can support your named incident lead in a pre-agreed window or run a separate post-incident review. Your organisation retains decision authority.
Practical education
Technical staff practise deciding whether a public advisory applies, assigning an owner, and checking a fix using a synthetic inventory. They also practise triaging and escalating a sample endpoint alert. Leadership rehearses business decisions and when to resume service.
Strengthen our security operations
Choose one improvement for your existing team or provider. We agree what they should be able to observe or do before selecting the tools.
Threat and exposure review
For one business service, we review your inventory, relevant advisories, exposed systems, and supplier access. We prioritise gaps by their effect on the business and agree an owner and a check date for each. Any testing stays within the systems you authorise.
Endpoint defence and alert validation
Reconcile an agreed group of devices against your inventory. Review endpoint detection and response (EDR) coverage, sensor health, policies, and exceptions, then follow a vendor-supported benign test alert to a named responder. You receive a coverage list, the observed handover time, and one witnessed retest.
Security control validation
Agree what the control, alert queue, and responder should each show. Use authorised, non-destructive checks and record what was observed, missed, or not tested. Retest agreed fixes. An alert reaching a responder does not prove that the wider controls work.
Security operations centre consultancy
Review how your security operations centre (SOC), internal team, or provider handles alerts for one service. Check the agreed log sources, escalation path, queue ownership, and coverage hours. You receive a coverage map, a prioritised tuning change, and a handover with named responsibilities. Your team or provider keeps responsibility for monitoring.
Response automation
Start with one low-impact security orchestration, automation, and response (SOAR) workflow: add context to an alert, open a ticket, and notify its owner. Check duplicate alerts, connector failure, and manual fallback. You receive an approved playbook, a permissions list, and a named maintainer. Containment and account restrictions require named human approval.
Breach and attack simulation (BAS)
For a wider simulation, we first confirm that the right specialists and a controlled environment are available. Together we agree the safeguards, the conditions for stopping, and who can authorise the exercise in writing.
When do we bring in a specialist?
If an exercise calls for specialist support, we check who has the experience, availability, and insurance for that work. You see a written scope naming the people involved before you decide.
Which service would you least want to lose?
Tell us what needs to keep running, who owns it, and what your last exercise or restore left unresolved.
Discuss cyber defence and recovery