Data breach response explained: the FTC's step-by-step guide for businesses
Secure the systems, fix what failed, then notify. The FTC's breach-response guide for businesses, condensed: what to do, who to call, and what to tell the people affected.
Your business has been breached - hackers in a server, an insider walking out with customer data, or personal information exposed on your own website by mistake. What you do next, and how fast, shapes how bad it gets. The US Federal Trade Commission's Data Breach Response guide for businesses lays the response out in three moves: secure your operations, fix the vulnerabilities, and notify the right parties - though notify is not a last step that waits for the cleanup, because legal deadlines can run while remediation is still underway. This is that guide, condensed.
Secure your operations
The FTC's opening line is blunt: the only thing worse than a data breach is multiple data breaches. Move quickly to secure your systems and fix the weaknesses that let the attacker in - and take affected equipment offline immediately. Counterintuitively, do not turn the machines off until your forensic experts arrive: evidence can live in memory, and the guide is explicit that nothing should be destroyed. Monitor entry and exit points, swap in clean machines if you can, and update the credentials of authorized users - stolen passwords keep the door open even after the attacker's tools are gone. If personal information ended up posted on your own website, take it down, and remember that search engines cache pages, so ask them not to archive it; check other sites for copies too.
Assemble the response team early. Depending on the size of the business, that can mean forensics, legal, IT, operations, HR, communications and management - and the FTC suggests considering independent forensic investigators to capture images of affected systems and map the scope. Interview the people who discovered the breach, document the investigation, and talk to legal counsel about the federal and state laws that apply.
Fix what failed
With the immediate loss stopped, find the hole. If service providers were involved, review what personal information they can reach and change their access if needed - and verify that their claimed fixes actually happened rather than taking their word for it. Check whether your network segmentation actually contained the breach to one server or site. Work through the forensic findings: was encryption on, who had access to the data at the time, who still has access and no longer needs it. The guide's test is simple - once the forensic report lands, take its recommended remedial steps as soon as possible.
Notify the right parties
Then tell people - and "then" does not mean "once everything is fixed". Notification duties run on their own timetable, which is why the guide pairs them with an early step: determine your legal requirements. The FTC's guide is written for US businesses - every US state, plus DC, Puerto Rico and the Virgin Islands, has a breach-notification law covering personal information, and the details vary. Other countries have their own regimes with their own clocks, so jurisdiction-specific legal advice is part of the response, not an optional extra. For law enforcement, the FTC points to local police, the FBI or the Secret Service - and the Postal Inspection Service if mail theft is involved. If the breach touches electronic personal health records, separate rules can apply: the FTC's Health Breach Notification Rule and, for covered entities, the HHS HIPAA rule, each with its own notification duties.
Notify affected businesses too. If account numbers were stolen from you but the accounts live elsewhere, tell the institution that holds them so it can watch for fraud; if you store personal information for other businesses, tell them. Stolen Social Security numbers warrant a call to the major credit bureaus - Equifax, Experian and TransUnion - especially if a large group of people is affected.
Notifying individuals is where the guide is most specific. Coordinate timing with law enforcement so you don't impede the investigation. Designate one point person with the latest information. Reach people by letter, website and toll-free number, and consider offering at least a year of free credit monitoring or identity-theft support - particularly when financial information or Social Security numbers were exposed. The notice itself should say what happened, what information was taken, what you know about its misuse, what you have done, and how to reach you - plus what people can do themselves, from fraud alerts and credit freezes at the bureaus to a recovery plan at IdentityTheft.gov. One detail worth copying from the FTC's model letter: tell people exactly how you will contact them in future. That helps victims spot the phishing scams that can follow a breach, and protects your credibility while you rebuild it.
The calm version
A breach is a bad week, not necessarily the end of the business. The response the FTC describes is unglamorous - contain, investigate, repair, disclose, in overlapping phases rather than a strict queue - and nearly all of it can be thought through in advance, which is the point. The only thing worse than a data breach, the FTC says, is multiple data breaches.
Sources: the FTC's "Data Breach Response: A Guide for Business" - securing operations, fixing vulnerabilities, notification duties, the credit bureaus' contact points, and the model notification letter. The FTC points breach victims to IdentityTheft.gov for recovery steps.
Frequently asked questions
Do I legally have to notify people after a data breach?
In the US, usually yes - every state, DC, Puerto Rico and the Virgin Islands has a breach-notification law for personal information, each with its own scope and timing. Electronic health records can add federal duties under the FTC's Health Breach Notification Rule or the HHS HIPAA rule. Outside the US, other laws apply with their own notification windows - and those deadlines can run before the cleanup is done, so which laws govern your incident is a question for legal counsel, asked early.
Should I turn off the hacked server right away?
Take affected equipment offline, but don't power it down until forensic experts arrive - evidence can be lost when a machine shuts off. The FTC is explicit: don't destroy evidence during the investigation and cleanup.
What should a breach notice actually say?
Per the FTC: what happened and when, what information was taken, how it has been misused if you know, what you are doing to fix the situation and protect people, and how to reach you. Add what individuals can do themselves - fraud alerts or credit freezes at the credit bureaus, and IdentityTheft.gov for recovery steps - and say how you will contact people in future, so they can spot impostors.
Do we have to offer credit monitoring?
It is a recommendation, not a blanket requirement. The FTC suggests considering at least a year of free credit monitoring, identity-theft protection or restoration services - particularly when financial information or Social Security numbers were exposed.