Use the contact page or call our team to confirm availability and the immediate scope. Do not send passwords, sensitive logs or evidence through a public enquiry form; we agree a suitable transfer method during intake.

We review escalation contacts, response authority, logging and recovery dependencies. The review records scope, dependencies and the evidence needed before implementation decisions are made.

We scope affected assets, examine available evidence and build an incident timeline. Findings are reviewed with the responsible team so access, operational impact and ownership are clear.

We document collection, integrity checks, access and chain-of-custody requirements. Implementation follows agreed acceptance criteria and approval points, with limitations documented.

We coordinate containment, restoration validation and improvements following the incident. Handover includes the responsibilities and review actions needed to keep the work useful over time.

The proposed deliverables include incident scope and investigation timeline; evidence inventory and technical findings; recovery recommendations and lessons learned. The final statement of work defines the format, acceptance criteria and responsibilities for each deliverable.

Containment and evidence preservation need to be coordinated. We agree responsibilities with your team, record the basis for decisions and separate verified findings from open questions. Recovery planning considers affected identities, dependencies and the checks needed before systems return to normal operation.

We first discuss your objective, current environment and operational constraints. The engagement follows scope incident, preserve evidence, analyze activity, and validate recovery. Access requirements, milestones and approval points are agreed before delivery.

Yes. We agree a responsibility matrix and communication process so your engineers, security team and service partners know who owns decisions, changes and follow-up actions. Ongoing support is included where specified in the agreed engagement.

Scope, environment size, access readiness, integration complexity and the level of implementation or ongoing support determine the proposal. We review those factors with you and agree milestones and fees before work begins.