Under attack right now?
Call us and say it is an incident. You do not need a retainer for the first call.
Incident response
Under attack? We stop the attack, get your systems running again and handle the reporting, with certified incident responders. Need proof for an auditor or a regulator? We write and test your incident response plan. You deal with one team from the first call to the final report.
Active incident? Call +1 514 577 8599 instead of using the form. Retainer clients get agreed response times.
Fixed scope
in writing before work starts
1 business day
reply time
Under attack
Containment on the first call
Investigation and forensics
Clean recovery and reporting
Auditor or regulator asking
Incident response plan and playbooks
GDPR breach report and evidence
Tabletop exercise with report
In short
We contain the attack, preserve evidence, investigate how attackers got in and what they reached, restore systems from clean backups and prepare the report for insurers, regulators and customers. The work is carried out by certified incident responders from a CREST-accredited firm. Organisations with a retainer get agreed response times and named responders.
Services
Isolate affected systems, disable compromised accounts and stop the spread, without destroying evidence.
How they got in, what they touched, what left the network, and whether they still have access.
Scope the encryption, check backups, assess decryption options and plan a clean restore.
Rebuild and restore from known-good backups, rotate credentials and harden what was exploited.
Timeline and findings for your insurer, regulators, auditors and customers. Breach-notification support.
Fix the root cause, improve monitoring and logging, and run a tabletop exercise so the next one is shorter.
A plan your auditor and your team can both use: roles, severity levels, escalation, communication, evidence handling and playbooks for ransomware, account compromise and data leaks.
A realistic scenario run with management and IT, with a written report of what worked, the gaps found and the actions agreed. Auditors ask for this evidence every year.
Examples
Stop the spread, assess backups and decryption options, restore cleanly and close the entry point.
Compromised mailboxes secured, forwarding rules and fraud attempts traced, customers warned if needed.
What was exposed, who must be notified and how to stop it happening again.
Isolated, investigated and rebuilt from known-good configuration, often as code.
What was exposed and when, documented with the measures taken, so you can answer the data protection authority and inform affected people if needed.
Plan and playbooks written and tested in an exercise, so you can show auditors and customers that the plan has been tested.
How to start
Retainer fees are quoted after a short call about your size, systems and cyber insurance. Unused retainer hours can be used for readiness work such as tabletop exercises or a penetration test.
No retainer needed
Scoping call first
Hourly or fixed-scope engagement
Agreed response times
Named responders
Pre-agreed rates
Onboarding of your environment
Readiness hours included
Incident response plan and playbooks
Tabletop exercise with report
Certified responders
Evidence for ISO 27001, SOC 2, PCI DSS and NIS2
Process
Tell us what you see. We agree immediate containment steps with you on the first call.
Certified responders work with your team to stop the attack and preserve evidence.
Clean restore, root-cause fixes and a written report for insurers and regulators.
Ready for audits
Auditors, regulators, enterprise customers and insurers ask for proof of how you would respond: a plan and evidence that it was tested. We prepare both.
Annex A 5.24 to 5.28: incident management planning, assessment, response, learning from incidents and collection of evidence.
Trust Services Criteria CC7.3 to CC7.5: evaluating security events, responding to incidents and recovering from them.
Requirement 12.10: an incident response plan that is ready to activate, and tested at least once a year.
Incident handling and reporting: an early warning within 24 hours, a notification within 72 hours and a final report within one month.
A personal data breach must usually be reported to the data protection authority within 72 hours. After a leak, the authority may ask for your facts, timeline, measures and incident procedure.
Cyber insurers ask for a tested plan or retainer at renewal; enterprise customers and investors ask for your plan, last exercise and responders.
An honest note before you book.
A plan that was never tested rarely satisfies an auditor. Plan for a tabletop exercise as well.
This readiness work prepares you for an audit. It does not replace your certification audit.
Already in an active incident? Skip this and call us first.
Prepared or not
FAQ
Straight answers. Ask us anything else on a call.
Do not decide before you know what was taken, whether backups are usable and what your insurer and local law require. We help you work through that quickly.
Disconnect them from the network rather than powering them off, so memory evidence is not lost. Then call us.
Many cyber insurance policies and renewals now ask for one, and some insurers have panels of approved responders. Check your policy; we can set up a retainer that fits its requirements, and coordinate with the insurer during an incident.
Yes. Tell your insurer early; many policies require notifying them first. We provide the documentation they ask for.
Certified responders from RedSecLabs, a CREST-accredited firm and PCI QSA, working as one team with us. We stay your single point of contact and coordinate with your IT team and any of your own vendors.
Yes, in practice. ISO 27001 (Annex A 5.24 to 5.28), SOC 2 (CC7.3 to CC7.5) and PCI DSS (requirement 12.10) all expect a documented incident response process, and PCI DSS requires the plan to be tested at least once a year. Auditors look for the plan, evidence that it was tested, and lessons learned being acted on.
A plan written and tested with a CREST-accredited firm (we work with RedSecLabs) carries more weight with auditors, enterprise customers and insurers than one written in-house, and an outside team spots gaps your own team is too close to see. It is also good evidence for customer security questionnaires and due diligence.
Yes. Under GDPR, a personal data breach must normally be reported to the supervisory authority within 72 hours of becoming aware of it, and the authority can follow up with questions or an investigation. We establish what happened and which data was affected, document the facts, timeline and measures taken, and help you answer the authority and decide whether affected people must be informed, with your legal adviser or DPO. A forensic report is available if needed.
At least once a year, and after major changes such as a new cloud platform, an acquisition or a real incident. Most frameworks expect annual testing; many companies run one for management and a more technical one for IT.
Related
Next step
Send a few details, and pick up to 3 times if you would like a call. Active incident? Call +1 514 577 8599 instead of using the form. Retainer clients get agreed response times.
You talk to the expert who would do the work
Written scope and price after the call
No obligation