Ransomware Recovery Checklist for Manufacturers Under 500 Employees
A step-by-step ransomware recovery checklist for small manufacturers: contain the attack, call the right people, restore in order, and restart the plant safely.
It's 5:40 on a Tuesday morning and your second-shift lead calls. The ERP won't load, the file server shows a ransom note on every share, and the scheduling screen at the front of the plant is black. Trucks are booked for 10 a.m. Everyone is looking at you. If you run IT for a manufacturer, having a ransomware recovery checklist for manufacturing before that call is the difference between a rough week and a lost quarter.
I've spent 15 years on networks, and my partner Mukesh has spent 25 in cybersecurity. The pattern we see is consistent: the companies that recover fastest aren't the ones with the fanciest tools. They're the ones who decided ahead of time who does what, in what order, and wrote it down.
This guide is that written-down version. It's built for plants with under 500 employees, a small IT team (sometimes a team of one), and a mix of office IT and shop-floor equipment. Print it, adapt it, and walk through it with your leadership before you need it.
In this guide
- The first hour: contain without making it worse
- Who to call, and in what order
- Assess the damage across IT and OT
- Ransomware recovery checklist for manufacturing: restore in the right order
- Get the plant running again safely
- After recovery: close the gaps so it doesn't happen twice
- Frequently asked questions
The first hour: contain without making it worse
The first hour is about stopping the spread and protecting evidence. It is not about fixing anything yet. Most of the expensive mistakes I've seen happen here, usually from good people moving too fast.
Isolate, don't power off
Pull network cables or disable switch ports for infected machines, and turn off Wi-Fi on affected laptops. Avoid shutting machines down if you can help it. Memory on a running system can hold clues (and sometimes encryption keys) that your forensics team will want.
- Disconnect affected servers and workstations from the network.
- Block internet access at the firewall if the spread looks broad.
- Disable VPN and remote access until you know how the attacker got in.
- Disconnect backup systems from the network if they are still clean.
Protect your backups first
Attackers go after backups on purpose, because a company with clean backups doesn't pay. If your backup server or NAS is still reachable, cut it off now. Change the backup admin credentials from a machine you trust, not one on the infected network.
Start a written log
Assign one person to keep a timeline: what was noticed, when, who did what. Use paper or a phone if you have to. Your insurer, your forensic firm and, for defense suppliers, the DoD will all ask for this later.
Don't touch the ransom note
Take a photo of the note, then leave it. Don't contact the attackers, don't click their links, and don't delete encrypted files. Those files may be decryptable later, and they're evidence.
Who to call, and in what order
Call order matters because your cyber insurance policy may require you to use their approved vendors. If you hire your own forensic firm first, you could end up paying for it yourself.
- Your cyber insurance carrier's breach hotline. It's usually on the policy declarations page. They'll assign a breach coach (typically a law firm) and approved incident response vendors.
- The breach coach / outside counsel. Bringing in counsel early helps keep the forensic work under legal privilege. Let them direct communications.
- Your incident response or MSP partner. Whoever knows your network best should be on the bridge call, working with the carrier's forensic firm.
- Law enforcement. Report to the FBI through IC3 (ic3.gov) or your local FBI field office. You can also report to CISA. Agencies sometimes have decryption keys or intelligence on the group involved.
- Leadership and key staff. Owner, plant manager, finance, HR. Keep the group small and use a channel outside company email, which may be compromised.
Extra steps for defense suppliers
If you handle Controlled Unclassified Information under DFARS clause 252.204-7012, you must report a cyber incident to the DoD through the DIBNet portal within 72 hours of discovery. You need a DoD-approved medium assurance certificate to file, so get one before you ever need it. The clause also requires you to preserve images of affected systems for at least 90 days.
Federal reporting rules are changing, too. CISA's rules under the Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) have been in the works for years and will add new reporting duties for many critical infrastructure companies once finalized. Confirm your current obligations with your attorney or compliance assessor rather than relying on a blog post, including this one.
If you're still sorting out where you land on CMMC, our breakdown of CMMC Level 1 vs. Level 2 is a good starting point.
Assess the damage across IT and OT
Before restoring anything, figure out how far the attacker got. Restoring onto a network where they still have access is how companies get hit twice in the same month.
Questions your team needs to answer
- Which systems are encrypted, and which are just unreachable?
- Which accounts did the attacker use? Assume domain admin until proven otherwise.
- Was data stolen before encryption? Many groups steal data first and threaten to leak it.
- Did the attack reach the plant floor, or did it stay on the office network?
- Are your backups clean, complete and recent enough to be useful?
Check the shop floor separately
On a lot of plants, the HMI workstations, historians and engineering laptops run Windows and sit on a flat network with the office. If that's you, assume they may be affected. PLCs themselves are rarely encrypted by commodity ransomware, but the Windows machines that program and monitor them often are.
Walk the floor with your maintenance lead. List every Windows box connected to production equipment and check each one. If your OT network is properly segmented, this step goes much faster. Our guide on securing shop-floor (OT) networks without stopping production covers how to get there.
Ransomware recovery checklist for manufacturing: restore in the right order
This is the core of the plan. Restore in dependency order, not in order of who is yelling loudest. Each layer depends on the one before it.
Step 1: Build a clean environment
- Rebuild or restore domain controllers from a known-good backup, or build fresh ones.
- Reset every privileged account password, including service accounts.
- Reset the KRBTGT account password twice (with time between resets) if Active Directory was compromised. Your forensic team will advise on timing.
- Patch the entry point. If it was an exposed RDP port or an unpatched VPN appliance, fix it before anything goes back online.
Step 2: Restore core infrastructure
- DNS, DHCP and network management.
- Firewalls and switches (verify configs haven't been changed).
- Endpoint protection (EDR) on every server before it reconnects.
Step 3: Restore business-critical systems
For most manufacturers, the order looks something like this:
- ERP / MRP system and its database
- Shipping and receiving systems, including label printers
- Production scheduling and MES
- Quality systems and records you need for customer or regulatory traceability
- Email and file shares
- Everything else
Step 4: Verify every restore
- Scan restored systems before reconnecting them.
- Check that restored data is complete. Look at the last few transactions in the ERP.
- Bring systems back on an isolated network segment first, then reconnect in stages.
- Watch for signs of the attacker coming back: new admin accounts, odd logins, unexpected scheduled tasks.
Should you pay the ransom?
That's a business and legal decision, not an IT one, and it belongs with leadership, counsel and your insurer. Paying doesn't guarantee working decryption, and it doesn't stop a leak of stolen data. Payments to sanctioned groups can also create legal exposure under U.S. Treasury (OFAC) rules, which is another reason counsel needs to be involved.
Get the plant running again safely
Production pressure is real. Customers want parts, and every idle hour costs money. But rushing machines back online before the network is clean can put you right back where you started.
Run on manual while IT recovers
Decide ahead of time what the plant can do without IT. Can you run jobs from printed travelers? Can shipping hand-write bills of lading? Can you track production on whiteboards for a few days? Many plants can keep going at reduced output if they planned for it.
- Keep printed copies of current work orders, BOMs and customer specs for top jobs.
- Keep a paper copy of key contact lists: customers, suppliers, carriers, employees.
- Know which machines can run standalone without a network connection.
Bring production equipment back one cell at a time
Reconnect one line or cell, confirm it behaves normally, then move to the next. Have engineering confirm that PLC programs and recipes haven't been altered. Compare them to known-good copies stored offline.
Communicate with customers early
A short, honest message to key customers ("we're dealing with a system outage and expect delays of X days") builds more trust than silence. Have your breach coach review the wording before anything goes out, especially if data may have been stolen.
After recovery: close the gaps so it doesn't happen twice
Once the dust settles, hold a review within two weeks while memories are fresh. Ask what worked, what didn't and what you'd change. Then fix the root causes.
The fixes we see matter most
- MFA everywhere it can go: email, VPN, remote access tools and admin accounts.
- Immutable or offline backups: at least one copy the attacker can't delete, even with admin credentials. Test restores on a schedule.
- EDR with 24/7 monitoring: a tool nobody watches at 2 a.m. won't stop an attack at 2 a.m.
- Segment the plant floor from the office network so a phishing click in accounting can't reach the HMIs.
- Remove exposed RDP and replace it with a secured VPN or remote access tool.
- Patch internet-facing devices first: firewalls, VPN appliances, email servers.
- Tighten admin rights: people use separate accounts for admin work, and fewer people have domain admin.
If you want a broader baseline, our list of 10 steps to protect your company applies to plants of any size.
Run a tabletop exercise
Once a year, sit leadership down for an hour and walk through a ransomware scenario using this checklist. Who makes the call to shut down the network? Who calls the insurer? Where's the policy number? You'll find gaps in a conference room that are far cheaper to fix than gaps found at 5:40 a.m.
Your printable checklist
- [Before] Insurance hotline number and policy number on paper
- [Before] Offline or immutable backup tested in the last 90 days
- [Before] DIBNet medium assurance certificate (defense suppliers)
- [Before] Manual operating procedures for shipping and production
- [Hour 1] Isolate infected systems; protect backups; start the log
- [Hour 1–4] Call insurer, counsel, IR partner, FBI/CISA
- [Day 1] Scope the attack across IT and OT; preserve evidence
- [Day 1–3] Rebuild identity and core infrastructure; patch the entry point
- [Day 2+] Restore ERP, shipping, MES in order; verify each
- [Week 2] Lessons-learned review and fixes
Frequently asked questions
How long does it take a manufacturer to recover from ransomware?
It varies widely. With clean, tested backups and a plan, core systems can often be back within several days. Without usable backups, recovery commonly stretches into weeks, and some data may never come back.
Should we shut down all computers when we find ransomware?
Disconnect them from the network instead of powering them off when you can. Unplugging the network cable or disabling Wi-Fi stops the spread while keeping evidence in memory. If you can't isolate quickly and encryption is spreading fast, shutting down is better than letting it reach more systems.
Does cyber insurance cover ransomware recovery?
Many cyber policies cover forensic investigation, legal counsel, restoration costs and business interruption, and some cover ransom payments. Coverage depends heavily on your policy and on whether you met its security requirements, like MFA. Call your carrier's breach hotline first so you don't accidentally void coverage by using unapproved vendors.
Do we have to report a ransomware attack?
It depends on your industry, contracts and the data involved. Defense contractors under DFARS 252.204-7012 must report within 72 hours, and state breach notification laws may apply if personal data was exposed. Talk with your breach coach or attorney about your specific obligations.
Can ransomware affect PLCs and production machines?
Most ransomware targets Windows systems, so PLCs are rarely encrypted directly. The bigger risk is to the HMIs, historians and engineering workstations that run Windows. Without those, you may not be able to monitor or change production safely.
Don't wait for the 5:40 a.m. call
A ransomware plan doesn't have to be a 60-page binder. It needs to answer a few questions clearly: who decides, who calls whom, what gets restored first, and how the plant keeps moving in the meantime.
If you're not sure your backups would survive an attack, or whether your shop floor is reachable from the office network, that's exactly what our free cybersecurity assessment is for. Mukesh and I will look at your setup and give you a plain-English list of what to fix first. Request your free cybersecurity assessment.
Related reading
- How to Secure Shop-Floor (OT) Networks Without Stopping Production
- CMMC Level 1 vs. Level 2: Which One Does Your Manufacturing Shop Need?
- MSP vs. Hiring a Full-Time IT Person: A Real Cost Breakdown
Harsha is a co-founder of SoftwarePac Technologies in Roanoke, VA, and a network engineer with 15 years of experience.




