When it happens, know what to do.
An incident is the worst time to decide who does what. We write your response plan, rehearse it with your leadership and engineers, and help you contain, investigate and recover when something happens.
- Price
- Set in your written proposal
- You receive
- A response plan your team has rehearsed and, during an incident, containment, investigation and a written account of what happened.
Scope, timeline and price in writing before any work starts.
Before. So you are ready.
- 01
Response plan
Roles, contacts and decisions written down, including who notifies regulators and clients. GDPR allows 72 hours to notify the authority; NIS2 asks for an early warning within 24.
- 02
Tabletop exercises
Realistic scenarios, such as ransomware or a leaked database, rehearsed with leadership and engineers.
- 03
Recovery readiness
Backups that can be restored, and the order in which systems come back.
During and after. Hands on.
- 01
Containment
Stop the spread first: isolate systems, revoke access and protect the evidence.
- 02
Investigation
How the attacker got in, what they reached and whether data left.
- 03
Recovery
Systems rebuilt clean and brought back in a safe order.
- 04
Lessons
The root cause fixed and the plan updated, so the same route does not work twice.
Questions, answered.
01We think we have been breached. What now?
Isolate affected machines from the network rather than switching them off, so evidence is preserved, and contact us. We help you contain the incident first, then investigate.
More in Cybersecurity.
Know where you stand before an attacker does.
Tell us what you run and what worries you. We will come back with a scope, a timeline and a price.