Compliance program

Breach response plan Before the clock starts

A data breach is a computer intrusion used to acquire confidential or secure information. Data breach losses reported to the Federal Bureau of Investigation topped $435 million in 2025. We build your response plan around the notice laws that may apply and practice it with your team.

Who it is for
Any organization that keeps customer, client or employee records
How it runs
A project to build the plan, then upkeep on a schedule
What you get
A sensitive data map, response plan, contact sheet and tabletop record

What a data breach response plan covers

The plan says who leads, who decides and who to call, how to rank an incident's severity, what evidence to keep and which notice deadlines apply to the data you hold.

In its current guidance, Special Publication 800-61 Revision 3 from April 2025, the National Institute of Standards and Technology (NIST) calls incident response plans the roadmap for putting an incident response capability in place.

The Federal Trade Commission (FTC) lists seven areas the written plan must address for financial businesses under its Safeguards Rule (16 CFR 314.4(h)). Anyone can use them as an outline:

  • The goals of the plan
  • Your internal process for responding
  • Clear roles, responsibilities and levels of decision-making authority
  • Communication inside and outside the organization
  • Fixing the weaknesses the incident exposed
  • Documenting and reporting the incident and the response
  • Reviewing and revising the plan after a security event

Breach notice laws and deadlines that may apply

Every state has a breach notice law, and they differ on who must comply, what counts as a breach, deadlines and exemptions. Below, Florida's law is the example, with federal rules that may also apply.

  • People in FloridaAs fast as practicable and within 30 days of determining or suspecting a breach, with the breach date, the data involved and how to reach you.
  • Florida Department of Legal AffairsWithin 30 days if 500 or more people in Florida are affected, with 15 more days possible for good cause given in writing.
  • Nationwide consumer reporting agenciesFlorida's law also requires telling them when more than 1,000 people must be notified at once.
  • The FTCFor covered financial businesses, no later than 30 days after discovering that unencrypted customer information of 500 or more consumers was acquired without authorization (16 CFR 314.4(j)).
  • People whose health data was exposedUnder the Health Insurance Portability and Accountability Act (HIPAA), without unreasonable delay and no later than 60 calendar days after discovery, in plain language (45 CFR 164.404).
  • Department of Health and Human ServicesFor HIPAA breaches of 500 or more people, at the same time as individual notices; smaller ones go in a yearly report within 60 days after year end (45 CFR 164.408).
  • Prominent mediaWhen a HIPAA breach involves more than 500 residents of a state, within the same 60 days (45 CFR 164.406).
  • Your vendorsFlorida gives a vendor holding your data 10 days to tell you, and HIPAA gives a business associate 60 days from discovery (45 CFR 164.410).

The breach notice clock starts at discovery

Most of these deadlines count from discovery, not from the end of your investigation, so the plan sets a reporting path: whoever notices a problem first knows whom to tell.

  • Under the FTC rule, the clock starts the first day the event is known to any employee, officer or other agent, except the person who committed the breach (16 CFR 314.4(j)(2)).
  • Under HIPAA, it starts the first day the breach is known, or would have been known with reasonable diligence. A use or disclosure the rule does not permit is presumed to be a breach unless a risk assessment shows a low probability of compromise (45 CFR 164.402, 164.404).
  • Florida lets you skip notice to individuals only if, after investigating and consulting law enforcement, you reasonably decide identity theft or other financial harm is unlikely. You must put that decision in writing, keep it for at least 5 years and send it to the Department of Legal Affairs within 30 days.
  • Encryption can change whether notice is required, within narrow limits: Florida excludes data that is encrypted or made unusable, the FTC treats data as unencrypted if an unauthorized person accessed the key (16 CFR 314.2), and HIPAA covers only "unsecured" health information. Your lawyer decides how these exceptions apply.
  • Florida treats a violation as an unfair or deceptive trade practice, with civil penalties of up to $500,000 for notice violations.

What to do in the first hours of a data breach

Get the right people involved and protect the evidence.

  • NIST suggests naming an incident lead, contacting your incident response provider if you have one, estimating the incident's severity and urgency, and recording the actions taken.
  • The FTC's guide for businesses says to take affected equipment offline but not to turn machines off until forensic investigators arrive, and not to destroy evidence.
  • The FTC and the Cybersecurity and Infrastructure Security Agency (CISA) both say to consult legal counsel, and CISA lists your cyber insurer among the parties to notify.

CIRCIA incident reporting: status in 2026

Reports under the Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) are not required yet, and until the final rule takes effect CISA encourages voluntary sharing. The rule went to the White House Office of Management and Budget for review on October 1, 2026, and on November 17, 2026, it was still pending and unpublished.

Once it takes effect, covered entities will have to report covered cyber incidents to CISA within 72 hours of reasonably believing one occurred, and ransom payments within 24 hours of paying. The final rule will settle who is covered; the April 2024 proposal would apply it to certain entities in critical infrastructure sectors.

Critical infrastructure organizations connected to electric utilities should also see our IT-scoped program for NERC CIP (the North American Electric Reliability Corporation's Critical Infrastructure Protection standards).

What we provide for data breach readiness

  • Data Breach Readiness ProgramWe map the customer and employee data you hold and the state breach laws that may apply, and build a response plan your team has practiced.
  • Incident Response ReadinessA response plan and practice drills, so everyone knows their role.
  • Incident Response SupportHands-on help to contain an incident and coordinate the recovery.
  • Business Continuity PlanningA plan for what comes back first when something goes down.

How we build and practice your response plan

  1. 01 MapWe find the customer and employee data you hold and list the breach laws that may apply, for your lawyer to confirm.
  2. 02 BuildWe write the plan with your decision makers and record the people, vendors and contacts it needs.
  3. 03 PracticeYour team walks through a breach scenario in a tabletop exercise, and we record what worked and what to change.
  4. 04 MaintainWe keep the plan current on a schedule and update it with the lessons from each exercise or incident.

What your breach readiness file holds

  • 01Sensitive data mapWhat customer and employee data you hold, where it is kept and which state breach laws may apply.
  • 02Response planRoles, who may shut down systems, the reporting path and who handles each message, kept in print and offline, as CISA advises.
  • 03Severity matrixThe levels you use to rank an incident's severity and urgency.
  • 04Contact sheetYour lawyer, cyber insurer, law enforcement and service providers, and what each provider may do for you.
  • 05Tabletop recordThe scenario you practiced, who took part and how the plan held up.
  • 06Lessons learnedWhat to fix after each exercise or incident, and the plan changes made.

What we do, What stays with you and your lawyer

CyberBlip

  • Map your customer and employee data and the breach laws that may apply
  • Write the response plan and keep it current
  • Run tabletop exercises and record the lessons learned
  • With Incident Response Support in place, lead technical triage, coordinate containment and recovery, and preserve evidence

You

  • Name the decision makers and approve the plan and contacts
  • Take part in the tabletop exercises
  • Authorize containment steps that disrupt the business
  • Decide with your lawyer whether to notify, what notices say and what to file with a regulator
  • Bring in your insurer and law enforcement as the plan directs

Data breach response plan questions

We're a small business. Do we really need a data breach response plan?

Breach notice duties can reach small businesses: Florida's law covers any business, sole proprietorships included, that holds the data it protects, such as a customer's or employee's name with a Social Security or driver's license number, or a user name or email address with its password. The FTC excuses covered financial businesses holding information on fewer than 5,000 consumers from the written plan, but not from notifying the FTC (16 CFR 314.6). Either way, someone must meet the deadlines, and the plan says who.

Who should be on our breach response team?

NIST's examples include leadership, incident handlers, technology staff, legal, public affairs, human resources, facilities and asset owners. Incident handlers can be your own staff, a contracted provider such as a managed security service provider, or one you call when needed.

Will you handle the breach for us, including the notices?

We handle the technical side through Incident Response Support, set up as a retainer or per incident. We lead triage, help contain the incident, coordinate the recovery and preserve evidence, and advanced forensics runs through a partner. Notices and regulator filings stay with you and your lawyer, and we do not promise to identify the attacker.

What happens in a tabletop exercise?

Your team talks through a realistic incident using the plan: who gets the first call, who decides, what evidence is kept and who must be told. NIST counts tabletop discussions among the exercises that prepare staff and outside parties.

Can we just use a data breach response plan template?

A template is a start. The plan still has to name your people, vendors and contacts, fit the notice laws for the data you hold, and be practiced. Two public guides to read first: NIST Special Publication 800-61 Revision 3 and the FTC's Data Breach Response: A Guide for Business.

Sources

Show all 13 sourcesHide sources
  1. 2025 IC3 Annual Report FBI Internet Crime Complaint Center (IC3), 2026-04-16
  2. SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile NIST, 2025-04-03
  3. 16 CFR 314.4, Elements (FTC Safeguards Rule) eCFR, 2026-11-13
  4. 16 CFR 314.2, Definitions (FTC Safeguards Rule) eCFR, 2026-11-13
  5. 16 CFR 314.6, Exceptions (FTC Safeguards Rule) eCFR, 2026-11-13
  6. 45 CFR Part 164 Subpart D, Notification in the case of breach of unsecured protected health information eCFR, 2026-11-13
  7. Section 501.171, Security of confidential personal information (2026 Florida Statutes) Florida Legislature, 2026
  8. Security Breach Notification Laws National Conference of State Legislatures, 2022-01-17
  9. Data Breach Response: A Guide for Business Federal Trade Commission, 2023-08
  10. #StopRansomware Guide CISA, 2023-09
  11. CIRCIA Reporting Requirements, proposed rule (89 FR 23644) Federal Register, 2024-04-04
  12. Executive Order Submissions Under Review: RIN 1670-AA04, CIRCIA final rule, received October 1, 2026 Office of Information and Regulatory Affairs (reginfo.gov), 2026-11-17
  13. Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA) CISA

Next step

Find out where you stand

Tell us how we can best support you.

Icons: Tabler Icons, MIT License. License text: /licenses/tabler-icons.txt