Not legal advice. Read anyway.
Data Breach: What to Do in the First Hours, Before Anyone Wipes the Evidence
The first instinct after a breach is to make it disappear: wipe the server, reset everything, restore yesterday's backup and never speak of it again. That instinct destroys the evidence your attorney, your insurer and the police will ask to see.
November 19, 2026 · 10 min read
The short answer
Take affected systems offline without turning them off, keep every log, and call your attorney, your insurer and your local police. The FTC's August 2023 guide for business says to mobilize a response team right away and not destroy forensic evidence. Deadlines depend on state law; in Texas, as of November 2026, individuals must be told not later than the 60th day after the breach is determined. Not legal advice.
On this page
- Before any developer: your attorney, your insurer and the police
- The first hours, in the order the FTC's guide sets out
- What the technical person should touch, and what to leave alone
- Texas notice deadlines, as the statute reads in November 2026
- Closing the hole without erasing the trail
- Where a web studio helps, and where it does not belong
Before any developer: your attorney, your insurer and the police
The Federal Trade Commission's Data Breach Response: A Guide for Business, published in August 2023, is the plainest official starting point we know of, and it does not begin with a developer. Among its first instructions: "Call your local police department immediately," and "Check state and federal laws or regulations for any specific requirements for your business." That second sentence is a job for counsel.
Call your insurer early too, before you hire outside help, and ask what your policy requires. Then call your attorney, if the insurer has not already pointed you to one. A developer comes after those calls, working under counsel's direction, because what a technical person does in the first hour can either preserve the record of what happened or erase it.
If what you have is a defaced or hijacked website rather than stolen customer data, our page on a hacked website emergency is the closer match. The two overlap, and when in doubt, treat it as a breach until counsel says otherwise.
The first hours, in the order the FTC's guide sets out
The FTC's guide is organized under three headings: Secure Your Operations, Fix Vulnerabilities, and Notify Appropriate Parties. The steps below follow its first section, quoted where the wording matters. The order is deliberate: contain the damage without disturbing the evidence.
- 1
Assemble the people
The FTC says to "Mobilize your breach response team right away to prevent additional data loss." For a small business that may be the owner, the office manager, your IT provider, your attorney and someone from the insurer.
- 2
Secure the physical side
"Secure physical areas potentially related to the breach." Lock the room where the server or affected computers sit and limit who goes in. If a former employee is involved, change door codes and collect keys.
- 3
Disconnect, do not power down
The guide says to "Take all affected equipment offline immediately" and also: "don't turn any machines off until the forensic experts arrive." Unplug the network, not the power.
- 4
Take exposed data down
"Remove improperly posted information from the web." If customer records are sitting on a public page or an open file share, close it, and write down exactly what was exposed and where.
- 5
Talk to whoever found it
"Interview people who discovered the breach." Write down what they saw, when, and what they clicked or changed afterward, while memories are fresh.
- 6
Preserve everything
"Don't destroy any forensic evidence in the course of your investigation and remediation." No wiping, no reinstalling, no restoring backups over affected systems until counsel and the forensic team agree.
- 7
Keep a written timeline
Our practice, not the FTC's wording: one shared document with every action, who took it and the time. Notice deadlines in Texas run from when the breach is determined, so that date matters.
What the technical person should touch, and what to leave alone
Do, with counsel's agreement
- Copy server, application and access logs to storage the attacker cannot reach
- Disable accounts the attacker used, after recording what they are and what they did
- Rotate passwords, API keys and database credentials, noting each change and its time
- Put a holding page in front of an affected website, served from outside the compromised server
- List every system that stores customer data and who can reach it
Do not
- Wipe and reinstall the affected server before it has been examined
- Restore a backup over a compromised system
- Power machines off before forensic experts say so
- Delete the attacker's files or accounts before they are documented
- Email customers or post publicly before your attorney has seen the wording

For an affected website, Google's web.dev guide to quarantining a site, read in November 2026, gives the same advice in web terms: take the site offline "so that it no longer serves content to users," note that "The 503 status code is a useful signal that your site is down temporarily," and say the response "should occur from outside your compromised server or site." It also says to "Contact your hoster" and "Change the passwords for all site users and accounts," including FTP, database, administrator and CMS logins. If the breach came through an application integration, our page on API integration failures explains how to rotate keys without breaking the connection again.
Texas notice deadlines, as the statute reads in November 2026
Texas law defines a "breach of system security" in Section 521.053 of the Business and Commerce Code, read on the Texas Legislature's statutes site in November 2026, as "unauthorized acquisition of computerized data that compromises the security, confidentiality, or integrity of sensitive personal information maintained by a person, including data that is encrypted if the person accessing the data has the key required to decrypt the data." Note that last clause: encrypted data counts if the key went with it.
| When | What the statute says | |
|---|---|---|
| Affected individuals | "without unreasonable delay and in each case not later than the 60th day after the date on which the person determines that the breach occurred" | Exceptions for a law enforcement delay or "as necessary to determine the scope of the breach and restore the reasonable integrity of the data system" |
| Texas Attorney General | "as soon as practicable and not later than the 30th day" after the breach is determined | Applies when the breach "involves at least 250 residents of this state"; submitted electronically on the Attorney General's form |
| Consumer reporting agencies | When notifying "more than 10,000 persons" at one time | Each nationwide agency must be told "of the timing, distribution, and content of the notices" |
| The data's owner, if you hold it for someone else | "immediately after discovering the breach" | Notice can be delayed at a law enforcement agency's request if it "will impede a criminal investigation" |
The notice to the Attorney General must include a description of the breach, the number of Texas residents affected, how many were already notified directly, the measures taken and planned, and whether law enforcement is investigating, per Sec. 521.053(i). The Attorney General posts a public listing of the notices it receives, without sensitive personal information. Under Sec. 521.002, sensitive personal information includes a name with an unencrypted Social Security number, driver's license or government ID number, or a financial account or card number with its access code, as well as information that identifies a person and relates to health care or payment for it.
The penalties in Sec. 521.151, as of November 2026, run "at least $2,000 but not more than $50,000 for each violation," plus up to "$100 for each individual to whom notification is due" for each consecutive day of failing to notify, capped at "$250,000 for all individuals" after a single breach. These are Texas rules only. Other states have their own deadlines and thresholds, and Sec. 521.053(b-1) lets notice to a resident of another state follow that state's law. Your attorney decides which apply.
Closing the hole without erasing the trail
The FTC's second heading is Fix Vulnerabilities, and its advice is pointed: "If your service providers say they have remedied vulnerabilities, verify that they really fixed things," and "Check your network segmentation." In plain terms, do not take a vendor's word for it, and find out whether the attacker could move from the system they entered to the ones that hold customer data.
- Preserve first, patch second: copy what the forensic team needs before changing the system they will examine.
- Find the door, not just the damage. A cleaned server with the original hole still open will be entered again.
- Rebuild affected systems from clean sources once they have been examined, rather than scrubbing the compromised copy.
- Check every place the stolen credentials worked, including email, hosting, the registrar and payment dashboards.
- Test the rebuilt system's money paths, login and forms before it goes back online.
For websites, the signs of compromise checklist in our PHP section is a useful read, and our malware removal service handles infected sites. If customer card data may be involved, read payment processing failures and contact your payment provider. If the leak came through a script on your checkout, see what to do about a tampered script. The FTC also notes that if you store personal information on behalf of other businesses, you should notify them, and that early notice means people "can take steps to reduce the chance that their information will be misused."
Where a web studio helps, and where it does not belong
Our part is the technical work around the website or application, done under your attorney's direction: preserving logs, closing the hole, rotating keys and credentials, rebuilding affected systems from clean sources, testing them, and writing down every step for counsel and the insurer. We do not give legal advice, draft notices to customers or regulators, or stand in for a forensic investigator your insurer or attorney appoints.
We respond the same business day; our hours are on the contact page. This work falls under our emergency software repair service, from $575, depending on complexity, with a written estimate before work starts. The emergency pricing page explains what moves that figure. We make no promise that every trace of an attacker can be found or that data can be recovered, and we will say so plainly.
If the breach began with a former contractor who still holds logins, our page on a developer who disappeared covers getting accounts back. If a database was altered, read the database emergency page before anyone restores. For the longer job of rebuilding a system with security designed in, see our custom software and web app development work, or bring in a fractional CTO to own security decisions. DataCram is a San Antonio web studio, building since 1999 (about); the emergency repair hub lists every other emergency we take on.
Questions owners ask in an emergency
Not yet. The FTC's August 2023 guide for business says to take all affected equipment offline immediately, but not to turn any machines off until the forensic experts arrive. Disconnect them from the network instead. Powering down can destroy information an investigator needs. Ask your attorney and insurer who the forensic experts will be.
Your attorney, your insurer and your local police. The FTC's guide says to call your local police department immediately and to check state and federal laws for requirements that apply to your business. Ask your insurer what the policy requires before hiring outside help. A developer comes after those calls, working under your attorney's direction.
Under Texas Business and Commerce Code Sec. 521.053, as of November 2026, notice must be made without unreasonable delay and not later than the 60th day after the business determines the breach occurred, with exceptions for law enforcement delays and determining the scope. Other states have different rules. This is not legal advice; confirm your obligations with your attorney.
When a breach involves at least 250 Texas residents, Sec. 521.053(i) requires notice to the Attorney General as soon as practicable and not later than the 30th day after the breach is determined, as of November 2026. It is submitted electronically through a form on the Attorney General's website. Your attorney should prepare and file it.
Under Texas law, it can. The statute's definition of a breach of system security includes encrypted data if the person accessing it has the key required to decrypt it. Whether a particular incident triggers notice depends on the facts, the data involved and every state where affected people live, so that question belongs with your attorney.
No, and one who offers to should worry you. A developer can preserve logs, close the hole, rotate credentials, rebuild systems from clean sources and document the work. Legal advice, notices to customers and regulators, and forensic investigation belong to your attorney, your insurer and the specialists they appoint. We do the technical part under their direction.
Keep reading
- Contain first, clean secondHacked Website Emergency: Contain It, Keep the Evidence, Then CleanYour website was hacked. How to contain it, keep the evidence, lock every login, follow Google's quarantine and review steps, and know when to call counsel.
- Incident checkPHP2Shell Signs of Compromise: How to Tell Whether Anyone Got InThe published warning signs of a PHP2Shell attack, where to find them in logs and files, and what to do if you find one: evidence, new keys, a clean rebuild.
- The website offerEmergency Website Repair: Who to Call When the Site Is Down, and What Happens After You DoWebsite down and no one to call? A same-business-day reply, fixed WordPress repair prices, from $575 for other platforms, and the checks before we sign off.
- The software offerEmergency Software Repair: Triage, Containment and a Written Root Cause for Broken Custom SoftwareCustom software or a web app broken today? Triage, stop the damage, restore, find the root cause, and a written estimate first. From $575, depending on scope.
- The mobile offerEmergency App Repair: An iOS and Android Developer for Crashes, Store Trouble and Expired CertificatesApp crashing, rejected or pulled from the store? Crash triage, store fixes, certificates and the access we need, from $575 with a written estimate first.
- Follow the money, literallyCheckout Not Working? When Customers Can't Pay, Walk the Money Path YourselfCustomers can't pay on your website. Buy from your own store, check the provider, webhooks and certificate, and skip the card-number workaround that bites.
- Everything in Emergency RepairSee the section
From the Insights desk
- Why Your WordPress Form Gets Spammed — and the Fix That Doesn't Annoy Real CustomersForm spam isn't the problem — it's what the spam does: buried leads, a poisoned CRM, and an inbox you've learned to ignore. Why CAPTCHAs make it worse, and the silent fix that stops bots without costing you real customers.
- Next.js or PHP? The Better Question Is Who Patches Your SiteApache, NGINX and PHP all shipped urgent fixes between November 11 and 19, 2026. PHP is not the villain, and Next.js has patch days too. The real difference is who installs the fix, how fast, and how much of your site runs code at all.
Get the technical side contained, by the book
Tell us what happened, what systems are involved and who your attorney is. We reply the same business day and work under counsel's direction, preserving evidence before anything changes.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.