Product · Resilience & Operations

CyberResponse

Incident response, before the incident

In brief

CyberResponse is Cyber Defense Advisors' incident response offering. It is bought two ways: as consulting — discrete projects such as an evidence readiness assessment, an incident response program build, a tabletop exercise or emergency response — or as an annual retainer that adds a contracted response clock (from 8 business hours down to 1 hour, 24/7), a prepared environment and a block of included activation hours.

Most companies meet their incident response firm during the worst week of their year. By then the evidence is gone, the notification clocks have been running for days, and nobody is sure whether the insurer will cover the people on the phone.

CyberResponse puts a named incident commander on contract before any of that — and commits in writing to how fast we answer. Buy it as discrete consulting projects when you have a question, a finding or an incident already underway, or as an annual retainer that keeps you prepared and puts a response clock in the contract.

Who buys it

  • CEO or owner
  • CFO
  • General Counsel
  • CIO or IT director
  • CISO
  • Chief Risk Officer
  • Board and audit committee
contracted response clock, by tier
8 hrs → 1 hr
to a tested activation path
60 days
covered from the day the activation card is issued
Day one
digital forensics, one chain of custody
In-house

Scope

The first hour decides the cost

An unprepared company spends the first hours of an incident on logistics instead of containment. These are the gaps CyberResponse closes before you need it.

  • No one to call

    Cold calls, scoping and contracting while the attacker is still working — and firms triage unretained callers behind retained ones.

  • No agreed first move

    Someone reimages the machine and destroys the evidence that would have shown what was taken.

  • Insurance friction

    Many policies require carrier approval of the responder. Engage the wrong firm first and that spend may not be covered.

  • Clocks nobody is watching

    State breach laws, HIPAA, GDPR and customer-notice terms each run from discovery, not from when you notice them.

Ways to buy

Two ways to engage

Project work

CyberResponse Consulting

Discrete engagements bought when you have a question, a finding, or an incident already underway. No subscription, no commitment on either side.

  • Evidence Readiness Assessment — would your logging survive an investigation?
  • IR Program Build — plan, decision rights, activation protocol
  • Tabletop Exercise — scenario-based, executives in the room
  • Runbook Development — the top scenarios, step by step
  • Compromise Assessment — a point-in-time hunt for what is already there
  • Emergency Incident Response — non-retained, best effort, standard rates
  • Post-Incident Remediation — run as a managed program

Annual subscription

CyberResponse Retainer

Everything in the readiness ladder, plus a contracted response clock and a block of activation hours. The difference between the tiers is the clock and the hours — never the seniority of who shows up.

  • A clock in the contract — 8 business hours to 1 hour, 24/7
  • A prepared environment — profile, crown jewels, backups, contacts
  • Insurance and counsel alignment confirmed before anything happens
  • In-house forensics — our own examiners, engaged on day one
  • Included activation hours, rolling into readiness if unused
  • Retainer-holder rate on anything beyond the included block
  • Tested annually — tabletop, activation path, out-of-band contact

Subscription

Retainer tiers

Every tier gets a named incident commander. What changes is how fast we are contractually committed to answer, and how many activation hours are included.

  • Entry

    Ready

    8 hrsBusiness hours

    • 10 activation hours
    • Annual tabletop
  • High exposure

    Advanced

    1 hr24 / 7

    • 50 activation hours
    • Quarterly check-ins
  • Multi-entity

    Enterprise

    CustomTo your terms

    • Scoped to carrier and contractual response duties

What's included

ItemConsultingReadyReady PlusAdvanced
Contracted response clock Not included8 business hrs4 hrs, 24/71 hr, 24/7
Named incident commander Per project Included Included Included
Environment and crown-jewel profile Billable Included Included Included
Incident response plan and activation card Billable Included Included Included
Notification and obligation register Billable Included Included Included
Evidence readiness assessment Billable Included Included Included
Insurance and counsel alignment Not included Included Included Included
Scenario runbooks BillableTop 2Top 4Top 4 + sector
Tabletop exercise BillableAnnualAnnualSemi-annual
Readiness check-ins Not includedAnnualSemi-annualQuarterly
Included activation hours None102550
In-house digital forensics Billable Included Included Included
Situation reports and draft notifications Billable Included Included Included
Recovery validation, report and roadmap Billable Included Included Included
Unused hours roll into readiness Not included Included Included Included

Activation items are delivered when an incident is declared. Included hours are hours, not a cap on the engagement; work beyond them bills at the retainer-holder rate.

When an incident is declared

The activation clock

  1. Hour 0

    Activation call

    You call the number on the activation card.

  2. Within the clock

    Incident commander engaged

    Triage call convened, severity set, decision log opened.

  3. +2 hours

    Containment direction

    First containment and evidence preservation instructions.

  4. +4 hours

    Forensics activated

    CDA examiners begin imaging and analysis. First executive report.

  5. +24 hours

    Scope and clocks

    Preliminary scope. Insurer and counsel notified. Deadlines named.

  6. +72 hours

    Timeline and data impact

    Working attacker timeline; containment validated.

  7. Until closure

    Reports and recovery validation

    No system is declared clean until access is proven gone.

  8. +10 days

    Post-incident report

    Root cause, timeline, findings and a remediation roadmap with owners.

The response clock is the contractual commitment. The steps that follow are our standard sequence, not guaranteed timings.

Deliverables

What a retained client holds before anything happens

  • Activation card

    One number, one address, a defined escalation path and an out-of-band method for when the primary one is compromised.

  • Incident response plan

    Client-specific, with roles, severity model, decision rights and escalation.

  • Environment and crown-jewel profile

    Assets, critical systems, backups, contacts and third-party dependencies, kept current.

  • Notification and obligation register

    Regulatory, contractual and insurance notice duties with their clocks, assembled before anyone needs them.

  • Evidence readiness report

    Logging coverage and retention against likely attack paths, with the blind spots and the fixes.

  • Scenario runbooks and tabletop findings

    The top scenarios step by step, tested with executives in the room.

Delivery approach

How it's delivered

  1. Discovery

    Environment profile, crown jewels, insurance position, contacts. Activation card issued.

    Weeks 1–2

  2. Design

    IR plan, severity model, decision rights, escalation, notification register.

    Weeks 3–4

  3. Build

    Evidence readiness assessment, logging fixes, scenario runbooks.

    Weeks 5–7

  4. Validation

    Tabletop with executives; activation path tested end to end.

    Week 8

  5. Ongoing

    Check-ins, plan maintenance, annual tabletop, standing availability.

    Month 3 on

Timeline. Sixty days to a tested activation path. You are covered by the clock from the day the activation card is issued — not from the day onboarding completes.

Built to the standards your auditors cite

Standard / authorityApplied to
NIST SP 800-61 Rev. 3Incident response lifecycle and plan structure
NIST CSF 2.0 — Respond (RS) and Recover (RC)Response and recovery outcomes
ISO/IEC 27035-1:2023Incident management principles and process
ISO/IEC 27001:2022 Annex A 5.24–5.28Incident management controls
SOC 2 TSC CC7.3–CC7.5Incident evaluation, response and recovery criteria
HIPAA 45 CFR §164.308(a)(6)Security incident procedures
PCI DSS v4.0.1 Requirement 12.10Incident response plan requirements
CMMC Level 2 — Incident Response domainIncident response practices for defense contractors
GDPR Articles 33 and 34; state breach notification statutesNotification and obligation register
SEC Form 8-K Item 1.05Material cybersecurity incident disclosure (public filers)

Responsible AI

Where AI is used — and where it is not

  • AI correlates large volumes of log, EDR and identity data into a candidate attacker timeline. A forensic analyst verifies every finding that reaches the report.
  • Notification obligations are mapped against the facts of the incident to produce the clock list. The incident commander and counsel decide what is notifiable.
  • Executive updates, board briefings and draft notices are drafted from the decision log. The incident commander edits and signs; counsel reviews external notices.
  • IR plans, runbooks and tabletop scenarios are drafted from your environment profile and current attack patterns, then approved by the incident commander.

AI accelerates, people decide. Nothing AI produces becomes a finding until an analyst has verified it against the evidence, and client evidence is never used to train external models.

Why CDA

Why CyberResponse from CDA

  • Independent by design

    CDA did not build, manage or monitor your environment, so our findings stand up with an insurer, a regulator and a court.

  • One firm, one chain of custody

    Forensics is performed in-house by CDA examiners, from acquisition to the signed report, with no third party in your incident.

  • A clock in the contract

    Response times are contractual commitments by tier — from 8 business hours to 1 hour, 24/7.

  • A quiet year still delivers

    Unused activation hours roll into readiness work, so the retainer improves your position even when nothing happens.

Ideal client profile

Companies of 50 to 1,000 employees with no internal incident response capability, material downtime cost or regulated data — including companies whose MSP is currently the only responder.

Scope, guardrails and responsible AI

What we do not do: legal advice or regulatory representation; ransom negotiation or payment facilitation (we name a specialist in your plan and leave the decision with you and counsel); infrastructure rebuild beyond containment direction; ongoing managed detection. What a clock is and isn't: response times are contractual commitments. Containment time, recovery time and insurance outcomes are not, and we will not sell them as such.

Frequently Asked Questions

Our cyber insurance already includes incident response. Why retain someone?

A carrier's panel firm is allocated when you call, has never seen your environment, and starts from zero. A CyberResponse retainer is a team that already knows your environment, with a response time in the contract — and CDA aligns with your carrier up front so coverage isn't put at risk.

What happens to activation hours we don't use?

Unused activation hours roll into readiness work — runbooks, testing, logging fixes — so a quiet year still delivers something.

Are containment and recovery times guaranteed?

No. The response clock is the contractual commitment. Containment time, recovery time and insurance outcomes are not, and we will not sell them as such.

Can we call you if we are not a retained client?

Yes. Emergency Incident Response is available without a retainer on a best-effort basis at standard rates, without a contracted response time.

Where should we start?

With an Evidence Readiness Assessment. It shows whether your logging would survive an investigation — the question every retainer depends on.

Ask us about a readiness assessment first

Put a response clock in the contract