← Back to Security Tips
Incident Response

What to Do in the First Hour
After a Security Breach

Discovering that your business has been compromised is one of the most disorienting moments a business owner can face. The natural reactions — panic, the urge to immediately wipe everything, uncertainty about who to call — are understandable. They are also dangerous. What you do in the first hour after a breach can determine whether you contain the damage or make it significantly worse. Read this guide now, while things are calm, so you know exactly what to do if the moment comes.

First: Breathe and Assess

Not every alarming situation is a confirmed breach. An employee clicking a suspicious link, a strange login alert, or an unusual charge on a company card are all warning signs worth taking seriously — but they do not necessarily mean you have been fully compromised. Take sixty seconds to assess: What specifically happened? Which system or account is affected? Who was involved and when?

The goal is not to slow down the response. It is to make sure your response is targeted. Shutting down your entire operation when a single email account may have been phished is an overreaction that causes unnecessary disruption. Act proportionately to what you actually know, and gather more information as you go.

Step 1: Isolate the Affected Systems

If you have identified a specific device or system that is compromised, disconnect it from the network immediately. Unplug the network cable, or disable Wi-Fi on the device. Do not turn it off — powering down a machine can destroy volatile memory that may contain evidence needed to understand what happened.

Isolation prevents the attacker from continuing to operate through the compromised system and stops malware from spreading laterally to other machines on your network. If you are dealing with ransomware that is actively encrypting files, disconnecting from the network stops the encryption from spreading — even if the original machine is already lost.

Step 2: Do Not Delete Anything

This is the mistake that causes the most long-term damage. When people discover a breach, the instinct is often to delete suspicious emails, wipe compromised machines, or remove malware immediately. Resist that instinct.

Evidence — logs, emails, files, browser history — is what allows investigators, law enforcement, and your legal team to understand exactly what happened, what was accessed, and who was responsible. Deleting evidence before it is documented can also create legal liability, particularly if your business is subject to breach notification laws. Preserve everything until a professional has reviewed it.

Step 3: Change Credentials From a Clean Device

Once you have isolated the affected system, change passwords for any accounts that may have been exposed — but do this from a device you are confident is not compromised. If the breach involved a compromised machine or email account, changing passwords from that same machine may simply hand the attacker the new credentials.

Prioritize in this order: email accounts, banking and financial platforms, any accounts that use the same password as the compromised one, cloud storage, and any account with access to client data. Enable or re-confirm two-factor authentication on each one as you go.

Step 4: Document Everything With Timestamps

As events unfold, write everything down. When did you first notice something was wrong? What did you see? Who was notified and when? What actions were taken and in what order? This documentation serves multiple purposes: it helps you reconstruct the timeline, it is required for any insurance claims, it supports legal proceedings if they become necessary, and it is required for breach notification filings in most states.

Use a separate device — your phone, a personal computer — to take notes so that your documentation itself is not on a potentially compromised system.

Step 5: Contact Your Security Provider or IT Team

This call should happen as early as possible — ideally within the first fifteen minutes if you have a provider. A security professional can help you accurately assess what happened, guide your response in real time, preserve evidence correctly, and begin the process of understanding the full scope of the incident.

If you do not have a security provider, this is the moment to find one. Many firms offer emergency incident response services. The cost is significant — but it is a fraction of what an uncontrolled breach costs in the end.

Most states have breach notification laws that require you to notify affected individuals within a specified timeframe — often 30 to 72 hours after discovery. In some industries, regulatory bodies must also be notified. Knowing your obligations before a breach happens means you will not miss a legal deadline in the chaos of responding to one.

Step 6: Notify the Appropriate Parties

Depending on what was accessed, you may have legal obligations to notify clients, employees, business partners, or regulators. Do not attempt to determine these obligations on your own in the middle of an incident — contact an attorney who handles data breach matters.

Also notify your bank if financial accounts may have been compromised. Banks have fraud departments that can place holds on wire transfers, flag suspicious activity, and in some cases claw back fraudulent payments if notified quickly enough.

Mistakes That Make Everything Worse

  • Turning off the compromised machine. Powering down destroys volatile memory and may delete the only record of what happened.
  • Trying to clean the system yourself. Amateur malware removal often misses persistence mechanisms that allow the attacker to regain access after you think they are gone.
  • Paying a ransom without professional guidance. There is no guarantee payment restores your files. Payment funds criminal operations. And in some cases, paying certain threat actors is illegal. Get professional advice first.
  • Telling no one. Keeping a breach quiet to avoid embarrassment delays necessary notifications and allows the damage to compound. It can also create legal liability if mandatory notifications are missed.
  • Continuing business as usual on potentially compromised systems. Until you know what was accessed and the intrusion has been fully remediated, treat all data on the affected systems as potentially exposed.

Prepare Before You Need This Guide

The businesses that respond best to breaches are the ones that prepared before it happened. That means having emergency contact numbers for your IT provider and an attorney in your phone. It means knowing where your cyber insurance policy is and what it covers. It means having a basic incident response plan — even a one-page document — so that when the moment comes, you are not making decisions from scratch under pressure.

Action Steps — Do These Now, Before You Need Them

  1. Save your IT provider's or security firm's emergency contact number in your phone. If you do not have a provider, research incident response firms in your area and save a contact today.
  2. Identify an attorney who handles data breach matters and save their number. Many offer free initial consultations for incident response situations.
  3. Locate your cyber insurance policy and confirm what incidents are covered and what the reporting window is.
  4. Look up your state's breach notification law and know the timeframe and threshold for required notifications in your industry.
  5. Write a one-page incident response plan: who to call, what to isolate, what to document, what not to do. Keep a printed copy somewhere accessible.
Incident Response

If Something Goes Wrong, You Need a Plan.

We help clients prepare incident response plans before they are needed — and we are available to our clients around the clock when something goes wrong. The time to prepare is now.