Incident response, step by step
What happens in the first hour, first day and first week after a cyberattack
Most incidents move through four lanes: contain, assess, recover and notify. Your organization and its counsel decide whether and when to notify anyone. Every incident is different and the steps often overlap. First hour, first day and first week describe the usual order of work, not a schedule or a promise.
- Contain
- Assess
- Recover
- Notify
Active incident line
Still happening? Call now.
After-hours emergency support is available. You do not need to be an existing client.
Contained, or not sure? Book an incident call.
Talk through what happened and what comes next with our incident team. If anything is still spreading, call instead. The booking form asks for your company or practice name and a few picked answers; please leave patient, client and customer details out.
The four lanes
Contain, assess, recover, notify
Containment and investigation often run together, and notification questions can come up at any point.
01
Contain (first hour)
Stop the spread and keep the evidence.
02
Assess (first day)
Find out what happened, what it touched and who needs to be involved.
03
Recover (first week)
Bring systems back in a controlled order, checked before use, and close the way in.
04
Notify
See what the HIPAA Breach Notification Rule says, and who decides.
Contain
First hour: contain
Stop the spread, keep the evidence and get the right people on the phone.
| Who | Contain |
|---|---|
| Your organization does | Choose one person who can approve actions today. Call our incident line at 1-650-300-7557 (after-hours emergency support is available), or book an incident call if it is contained. Disconnect affected computers from the network by unplugging the cable or turning off Wi-Fi, without powering them off, wiping or reimaging them. Leave the ransom note, suspicious emails, inbox rules, files and logs where they are. If money may have moved, call your bank’s fraud line. Coordinate by phone or from a separate, known-clean device. Write down what you noticed, when, and who noticed. Then work through the full first-steps checklist. |
| What ACS Cyber does once you reach us | We listen and help you triage: what is happening, what is at stake and what to do first. We agree the first containment actions with the person who can approve them. We tell you what to keep and what not to touch, so evidence survives. We help you decide who to bring in: insurer, counsel, bank. We work alongside your IT provider, with clear roles. |
| You will be asked | What happened: ransomware, a fake invoice or changed bank details, a hacked email or Microsoft 365 account, exposed data, malware or unusual computer behavior, or not sure. Whether it is still happening. When it started or was first noticed: today, in the last few days, longer ago, or not sure. How much seems affected: one computer or account, several, or a whole office. Whether money moved. Whether you have cyber insurance. Who can approve actions (a role, said on the call). |
| Please do not | Pay, reply to or negotiate with the attacker. Power off, wipe, reimage or restore anything yet. Delete emails, files, inbox rules or logs. Send passwords, patient information, logs or files to anyone by email or chat, including us. Post or announce anything before the facts are known. |
Assess
First day: assess
Find out what happened and how far it reaches, and bring in your insurer and counsel.
| Who | Assess |
|---|---|
| Your organization does | Call your cyber insurer’s claims line and check the policy’s notice requirements; some policies require approved vendors or the carrier’s consent before costs are incurred. Bring in legal counsel early. Decide with us which systems stay off and how the front desk works in the meantime. Keep the timeline going. |
| What ACS Cyber does once you reach us | We identify the affected users, systems and data, and how far the activity reaches. Alongside containment, we investigate how the attacker got in and how far it reached, and we preserve the evidence and document who handled it. We work alongside an insurer-assigned response firm where your policy permits. You get regular updates in plain language. Scope, approach and costs are discussed with an authorized decision maker before work begins. |
| You will be asked | Whether your insurer knows: yes, not yet, or no policy. Whether counsel is involved: yes or not yet. Which systems are involved: email or Microsoft 365, practice software or its server, workstations, backups, phones, cloud apps, or not sure. Whether an outside IT provider is involved. |
| Please do not | Restore from backups before the attacker’s access is removed. Make large changes nobody has agreed; they can destroy evidence. Discuss the incident over email or chat the attacker may be watching. |
Recover
First week: recover
Bring systems back in a controlled order and close the way in.
| Who | Recover |
|---|---|
| Your organization does | Approve the order in which systems come back. Work through the notification questions with counsel (see what the rule says). Agree staff and patient communications with counsel. Tell staff what to watch for. |
| What ACS Cyber does once you reach us | We remove malicious access, persistence and the weaknesses that allowed it. We help restore systems, accounts and data in a controlled order, from clean backups or clean rebuilds, checked before use; where rebuilds are needed, the IT operations team at Atlantic Computer Systems can carry them out. You receive a documented timeline, plain-language findings and an affected-data analysis for leadership, insurer and counsel. We recommend and help implement changes that reduce the chance of a repeat. |
| You will be asked | Which systems matter most to bring back first: scheduling, imaging, billing, email or phones. Whether backups exist: offline copies, not sure, or none. |
| Please do not | Bring a system back before it is checked. Treat the incident as closed before the root cause is known. Delete the investigation record. |
Notify
What the HIPAA Breach Notification Rule says
The rule applies to HIPAA covered entities and their business associates. Whether it applies to your practice and to this incident, and what to do, is decided by your practice with its counsel. Here is what the regulation says, quoted from the eCFR.
| Topic | What the rule says | Citation |
|---|---|---|
| When an incident counts as a breach | “Except as provided in paragraph (1) of this definition, an acquisition, access, use, or disclosure of protected health information in a manner not permitted under subpart E is presumed to be a breach unless the covered entity or business associate, as applicable, demonstrates that there is a low probability that the protected health information has been compromised based on a risk assessment of at least the following factors: (i) The nature and extent of the protected health information involved, including the types of identifiers and the likelihood of re-identification; (ii) The unauthorized person who used the protected health information or to whom the disclosure was made; (iii) Whether the protected health information was actually acquired or viewed; and (iv) The extent to which the risk to the protected health information has been mitigated.” The definition also lists exclusions (paragraph (1)). | 45 CFR 164.402, definition of “Breach”, paragraph (2) |
| When the clock starts | “a breach shall be treated as discovered by a covered entity as of the first day on which such breach is known to the covered entity, or, by exercising reasonable diligence would have been known to the covered entity. A covered entity shall be deemed to have knowledge of a breach if such breach is known, or by exercising reasonable diligence would have been known, to any person, other than the person committing the breach, who is a workforce member or agent of the covered entity (determined in accordance with the federal common law of agency).” | 45 CFR 164.404(a)(2) |
| Notice to individuals | “Except as provided in § 164.412, a covered entity shall provide the notification required by paragraph (a) of this section without unreasonable delay and in no case later than 60 calendar days after discovery of a breach.” | 45 CFR 164.404(b) |
| Notice to the media | “For a breach of unsecured protected health information involving more than 500 residents of a State or jurisdiction, a covered entity shall, following the discovery of the breach as provided in § 164.404(a)(2), notify prominent media outlets serving the State or jurisdiction.” Timing: “Except as provided in § 164.412, a covered entity shall provide the notification required by paragraph (a) of this section without unreasonable delay and in no case later than 60 calendar days after discovery of a breach.” | 45 CFR 164.406(a), (b) |
| Notice to HHS, 500 or more people | “A covered entity shall, following the discovery of a breach of unsecured protected health information as provided in § 164.404(a)(2), notify the Secretary.” And: “For breaches of unsecured protected health information involving 500 or more individuals, a covered entity shall, except as provided in § 164.412, provide the notification required by paragraph (a) of this section contemporaneously with the notice required by § 164.404(a) and in the manner specified on the HHS Web site.” | 45 CFR 164.408(a), (b) |
| Notice to HHS, fewer than 500 people | “For breaches of unsecured protected health information involving less than 500 individuals, a covered entity shall maintain a log or other documentation of such breaches and, not later than 60 days after the end of each calendar year, provide the notification required by paragraph (a) of this section for breaches discovered during the preceding calendar year, in the manner specified on the HHS web site.” | 45 CFR 164.408(c) |
| If the practice’s IT provider is a business associate | “A business associate shall, following the discovery of a breach of unsecured protected health information, notify the covered entity of such breach.” Timing: “Except as provided in § 164.412, a business associate shall provide the notification required by paragraph (a) of this section without unreasonable delay and in no case later than 60 calendar days after discovery of a breach.” | 45 CFR 164.410(a)(1), (b) |
| Law-enforcement delay | The timing rules in 45 CFR 164.404(b), 164.406(b) and 164.410(b) begin “Except as provided in § 164.412”, and 164.408(b) says “except as provided in § 164.412”. | 45 CFR 164.412 |
Source: 45 CFR part 164, subpart D, eCFR (snapshot of October 20, 2026, read October 26, 2026). Notice rules beyond HIPAA, such as the FTC rules and several state laws, are quoted on the notification rules page.
This section quotes the regulation and is not legal advice. State breach-notification laws, other federal rules and your contracts can set other duties and deadlines. Whether and when to notify is decided by your practice with its counsel. Our part is the evidence: what data was accessed, whose it was, how and when.
After recovery
Prevent it next time
Once your systems are back, the next job is keeping the way in closed. Atlantic Computer Systems, our parent company, runs fractional IT plans with security built in, so the fixes from the incident stay in place.
See the fractional IT plans (Atlantic Computer Systems site) Start with a cyber security assessment (Atlantic Computer Systems site)
IT for your kind of organization
- Medical practices (Atlantic Computer Systems site)
- Dental practices (Atlantic Computer Systems site)
- Law firms (Atlantic Computer Systems site)
- Accounting and CPA firms (Atlantic Computer Systems site)
- Financial services (Atlantic Computer Systems site)
- Have your own IT team? Co-managed IT (Atlantic Computer Systems site)
- Any other organization: the plans (Atlantic Computer Systems site)
Coordination
Who else is involved, and who decides
If you have cyber insurance, contact your carrier early and follow its notice requirements. If your insurer assigns a response firm, we work alongside that firm where your policy permits.
Legal counsel advises on notification obligations, contracts and communications. We support counsel with evidence, timelines and affected-data analysis, and we coordinate with your insurer when you authorize it. We do not provide legal advice or make notification decisions.
If your IT provider is involved, we work alongside them with clear roles so work is not duplicated or undone. When records may have been exposed, see data breach response, or go back to start here.
Who decides what
- Your organization: which actions to approve, and the order in which systems come back
- Your counsel: notification questions and communications
- Your insurer: what the policy requires, and which firms it approves
- Your bank: whether a payment can be stopped or recalled
- ACS Cyber: the evidence, the investigation and the recovery work you authorize
FAQ
Questions about the first hour, day and week
The first hour is about containment: one person who can approve actions, a call for help, affected computers disconnected without being wiped, and the evidence left where it is. If money may have moved, the bank’s fraud line comes next.
Every incident is different, and this describes the usual order of work, not a schedule.
It depends on what was affected, how far the attacker got and whether clean backups exist, so there is no standard length. Systems come back in an order your organization approves, each checked before use, and you get regular updates in plain language along the way.
The rule says a covered entity “shall, following the discovery of a breach of unsecured protected health information as provided in § 164.404(a)(2), notify the Secretary” (45 CFR 164.408(a)). The table above quotes the timing rules for 500 or more and for fewer than 500 individuals. Whether it applies to you is decided with your counsel.
The rule says “a breach shall be treated as discovered by a covered entity as of the first day on which such breach is known to the covered entity, or, by exercising reasonable diligence would have been known to the covered entity” (45 CFR 164.404(a)(2)). The timing rule for notice to individuals reads “without unreasonable delay and in no case later than 60 calendar days after discovery of a breach” (164.404(b)). Whether it applies to you is decided with your counsel.
The rule says that for breaches “involving less than 500 individuals, a covered entity shall maintain a log or other documentation of such breaches and, not later than 60 days after the end of each calendar year, provide the notification required by paragraph (a) of this section for breaches discovered during the preceding calendar year” (45 CFR 164.408(c)). Notice to individuals has its own timing rule (164.404(b)), and state laws and contracts can set other duties. Whether it applies to you is decided with your counsel.
The rule says “A business associate shall, following the discovery of a breach of unsecured protected health information, notify the covered entity of such breach” (45 CFR 164.410(a)(1)), and on timing, “without unreasonable delay and in no case later than 60 calendar days after discovery of a breach” (164.410(b)). Whether it applies to you is decided with your counsel.
Next step
Contained? Book an incident call.
If anything is still spreading, call now instead. The booking form asks for your company or practice name and a few picked answers; please leave patient, client and customer details out.