Cybersecurity
Incident response and readiness
If something has already happened, call us. If you want to be ready before it does, we help with plans, exercises and the technical groundwork that makes response faster.
What we help with
Most incidents start small: a suspicious sign-in, a ransom note, a security tool alert, or a customer who reports odd email from your domain. What happens in the first hours decides how much is lost.
We help you work out what happened, how far it went, how to contain it, and how to recover safely. We preserve evidence with chain of custody where it may matter for legal or insurance purposes, and we coordinate with your counsel and insurer when you ask us to.
We follow the incident response lifecycle described in NIST SP 800-61 Revision 3, which aligns incident response with the NIST Cybersecurity Framework 2.0.
How an engagement starts
- 1
Intake call
We ask what you saw, when, and what has been done so far. We tell you what to preserve and what to avoid.
- 2
Scoping
We agree what we will look at, who can approve actions and how we will communicate.
- 3
Triage and containment
Establish the likely scope, then recommend containment steps you can take safely.
- 4
Investigation
Collect and analyze logs and endpoint or cloud data. Build a timeline. Identify the entry point and what was accessed.
- 5
Recovery support
Help eradicate the attacker’s access and bring systems back with confidence.
- 6
Lessons learned
A written account, and a short list of changes that would have made this easier to stop.
Incident response services
-
Digital forensics and incident response
Investigate suspected intrusions: preserve evidence, determine scope, support containment and recovery, and document what happened.
-
Compromise assessments
A focused, time-boxed look for signs that attackers are or have been in your environment.
-
Ransomware readiness
Assess whether you could detect, contain and recover from ransomware, and fix the weak points: identity, backups, segmentation and response.
-
Incident response planning
Write plans and playbooks your team can use at 2 a.m., based on NIST SP 800-61 Rev 3 and tested against realistic scenarios.
-
Tabletop exercises
Facilitated discussions where executives and technical teams work through a realistic incident, find gaps and agree changes.
What to have ready
- A current list of critical systems and their owners
- Who can authorize isolating or shutting down a system
- Contacts for legal counsel, cyber insurer and communications
- Where logs live and how long they are kept
- Backup status, including whether backups are isolated from the network
- Administrator account inventory and who holds break-glass access
Questions people ask
Do you offer 24/7 response?
We confirm availability during the intake call and in writing. We do not promise round-the-clock coverage in general terms.
Should we pay a ransom?
That is a decision for your leadership, counsel and insurer. We can help assess what was taken, whether backups are usable and what the attacker has access to, so the decision is made with facts.
Will you notify authorities or customers?
No. Notification decisions belong to you and your counsel. We can provide technical facts for those decisions.
Related
-
Security operations
Threat hunting, detection engineering, SIEM consulting, SOC engineering, automation and threat intelligence.
-
Consulting and GRC
Security strategy, architecture review, security engineering and implementation, and readiness support for NIST CSF, SOC 2, ISO 27001, PCI DSS, HIPAA and CMMC.
Need to understand your security exposure?
Speak with a security expert
Talk through your environment and goals. We reply to scope the work before anything is tested.
Speak with a security expertPlan an assessment
Answer a few questions and get a structured preliminary scope you can send us.
Use the plannerUnder attack right now?
Call the US office and tell us what you are seeing. Do not wait for a form reply.
Incident response