A staff member says their files suddenly have strange names. Another gets an MFA prompt they didn't trigger. The controller calls because a vendor's bank details just changed by email. Nobody knows yet whether these events are connected, but someone has to decide what happens next.
That first hour is hard because the facts are incomplete. You may need to keep the business running, protect customer information, and stop an attacker before you can say exactly what happened. Knowing what to do if your business gets hacked comes down to a steady sequence: preserve what you can, contain what you must, and bring the right people into each decision.
At a glance
- Take a credible sign of compromise seriously, and hold off on calling it a full breach until the facts support it.
- Call your incident response lead, trusted IT team, insurer, and counsel, then isolate affected access while preserving evidence.
- Restore only after the intrusion path and recovery environment have been assessed, and review notification duties with qualified legal advice.
First, make the call that starts your response
Someone needs to own the incident. That might be the CEO, an operations leader, the internal IT manager, or a designated incident coordinator. The owner should start a record right away: what was reported, when it was discovered, who is affected, and which business services may be at risk. If business email might be compromised, use a trusted phone number or another channel.
Call your established IT or incident response provider and describe what people actually observed. Leave the diagnosis to them. If you have cyber insurance, notify the insurer promptly and follow the policy's incident assistance process. Many policies require specific vendors or approvals for certain expenses. Bring legal counsel into decisions about preservation, notifications, contracts, and law enforcement.
You don't need a complete forensic report before you stop obvious, ongoing harm. You also shouldn't make irreversible technical changes just to show urgency.
What to do if your business gets hacked: the first hour
Record what people actually saw
Ask staff to stay away from unfamiliar tools and avoid investigating on their own. Have them write down suspicious messages, unexpected account prompts, timing, affected devices, visible errors, and which business activities stopped working. Preserve relevant messages, screenshots, logs, and vendor notifications through the response team. Keep confirmed facts separate from assumptions. A ransomware note, an account takeover, and a fraudulent invoice each call for different containment.
Contain the affected path with help
A trained responder may isolate a device from the network, disable a compromised identity, revoke active sessions, block malicious traffic, or restrict remote access. The right move depends on the threat and on what evidence needs to be kept. Unplugging the entire network or disabling every administrator account without understanding the business impact can create a second emergency.
Hold off on wiping, resetting, or rebooting a suspected device. Volatile evidence can be lost, and the root cause gets harder to find. Incident response guidance stresses preserving evidence while you make containment decisions. If destructive activity is still underway, the response lead may decide immediate containment comes first. Follow that judgment and write it down.
Protect payment and communications workflows
If an email compromise may have redirected a wire or payment, call your bank right away using an independently verified number and follow its fraud recall process. Ignore any contact details in the suspicious email. If business email can't be trusted, move incident coordination to a separate, secure channel and confirm requests for sensitive information by voice.
Find out whether backups are actually safe
Ask where your independently protected copies live, who controls them, and when they last passed a restore test. Keep a clean backup environment away from a compromised identity or network until there's a recovery plan. A backup taken after the intrusion began may contain infected files or accounts the attacker created.
The next 24 hours: establish scope and decisions
Your incident team should map the affected accounts, devices, applications, files, service providers, and business processes. Decide what has to stay available: payroll, customer service, production, banking, orders, or critical communications. If the company has a single IT generalist, outside forensic expertise may be needed to tell the original entry point apart from symptoms elsewhere.
Keep an incident log with times, decisions, approvals, and where evidence is stored. Record when accounts were isolated, credentials changed, systems examined, and customers or partners contacted. The log supports recovery and later review, and it prevents conflicting stories as word of the incident spreads inside the company.
You're trying to answer three separate questions. Can the attacker still act? What data or services may have been affected? What needs to be restored, and from which trusted state? One reassuring antivirus scan doesn't answer any of them.
What not to do under pressure
Don't delete suspicious messages and logs. They may show where an account was accessed or how an attacker changed payment instructions. Preserve them through the incident team's process.
Don't immediately reimage every machine. Some systems may need forensic collection first. Reimaging before you understand the scope can destroy the timeline and leave the original weakness in place somewhere else.
Don't restore everything into the same exposed environment. Check identity, privileged access, security updates, network paths, and backup integrity first so the compromise doesn't simply come back.
Don't send a confident company-wide explanation based on a rumor. Staff need clear instructions, but public and customer statements should be coordinated with counsel and stick to verified information.
Don't assume the insurer handles every compliance duty. Insurance assistance and legal notification obligations are separate responsibilities. The company still needs accountable decisions and records.
Massachusetts companies should assess breach notification early
If your business holds personal information about Massachusetts residents, the state's data breach law may require notification when defined conditions are met. Massachusetts guidance covers notice to affected residents and to state authorities, including the Attorney General's Office and the Office of Consumer Affairs and Business Regulation. The facts and legal thresholds matter, and incidents involving residents of other states or regulated data can trigger additional requirements.
Have counsel assess the information involved, the affected individuals, applicable contracts, industry rules, and timing. An operational disruption isn't automatically a reportable personal-data breach, and a quiet incident can still be one. IT's job is to preserve reliable records and get the facts to counsel quickly enough for sound legal decisions.
How to recover without repeating the incident
Once the response lead has defined containment and a trusted recovery path, prioritize critical functions. Some devices can wait. Restore identity and administrative control first, then essential applications, then less critical services. Test business workflows along with the servers. Can staff process an order? Can finance verify banking details? Can customer service pull up authorized records?
Use recovery time and recovery point objectives to explain the tradeoffs to leadership. A three-hour recovery time objective is a target, and only an actual restore test shows whether you can hit it. A one-day recovery point means some recent changes could be lost. Spell those consequences out in plain language so nobody is surprised.
After service returns, document which control failed, whether monitoring caught the event, what you learned about provider responsibilities, and how you'll prevent a repeat. NIST's 2025 incident response guidance treats response and recovery as part of an ongoing cybersecurity risk management program, with lessons feeding back into everyday operations.
A short preparedness list for next time
Keep an incident contact list you can reach outside your primary email. Know your insurer's reporting procedure. Know who owns the administrator accounts and the domain registrar. Maintain centralized logs with usable retention, and test a recovery path that doesn't depend on the environment you'd suspect first. Decide in advance which business services can pause and which can't.
None of this is the glamorous part of cybersecurity. It's what turns the next bad morning into something you can manage.
Get control first, then decide what to change
At CTP, our security work is shaped by more than two decades of hands-on incident experience and an architecture that keeps identity, monitoring, backup, and infrastructure separate. During a suspected compromise, the first goal is to regain reliable control and understand what happened. New technology may make sense later, once the facts are in.
If you're dealing with a suspected incident right now, follow your emergency response arrangements first. When you're ready to talk about preparedness and architecture, see how we work with small and mid-size businesses or schedule a conversation.

