About Us Solutions
Managed IT SupportCybersecurityRegulatoryProfessional ServicesCo-ManagedCMMC ComplianceData BackupCloud MigrationIT ConsultingAI ConsultingMicrosoft 365Microsoft CopilotSD-WAN Services
Industries
Accounting & CPA FirmsManufacturing & DefenseProfessional Services
Process Testimonials Resources Careers
Contact UsBook a Call
Article · 7 min read

How to improve manufacturing IT security in Minneapolis: close the three gaps attackers love

Walk into almost any midsized plant in the Twin Cities and you will find the same three things: a machine running software older than the newest hire, one network from front office to floor, and two people who know how it all fits together. Here is how to close those gaps in 90 days.

How to Improve Cybersecurity in Manufacturing cover
Download the PDF →Free · PDF · no form
Jump to a section
  1. The three gaps
  2. Gap one: legacy machines
  3. Gap two: flat networks
  4. Gap three: tribal knowledge
  5. The 90 day plan
  6. What to do next
  7. Questions people ask
The short version
  • Legacy machines cannot be fixed, only contained. Control what can reach the controller, block its internet access and keep a known good backup offline.
  • A flat network turns a phishing email in accounting into a production outage. Segmenting with switches you already own closes that path in weekends.
  • Tribal knowledge does not cause an attack, but it decides whether recovery takes four hours or four days. Write it down before you need it.
  • All three gaps close in 90 days with zero machines replaced: see everything, build the walls, prove recovery.

Manufacturing IT security in Minneapolis has three gaps

None of the three things above is a security problem on its own. Together they are the reason manufacturing has been the most attacked industry in the world for three years running, according to IBM's X Force Threat Intelligence Index 2024. Manufacturing IT security in Minneapolis, from the machine shops along I-494 to the food processors in the northern suburbs, comes down to closing those three gaps.

Attackers look for the easiest path to the systems that stop production, because stopped production is what gets a ransom paid. In Solution Builders manufacturing assessments across the metro, the gaps show up in a consistent order.

  • Legacy machines nobody can patch. The most common finding by far.
  • A flat network from office to floor. One VLAN, one fault, one outage.
  • Shared logins and vendor remote access. A standing VPN with one shared password.
  • Knowledge held by one or two people. The HMI password, the PLC program, the vendor to call.
  • No tested recovery for machine configurations. Backups of the office, nothing for the line.
The good news

This is a 90 day project, not a capital program

Closing all three gaps takes about one quarter, and almost none of it touches the machines themselves. You need a plan, a few weekends and someone who has done it before, not a new line or a shutdown.

Gap one: legacy equipment security when you cannot patch

A controller built in 2008 was never designed to sit on a network with the internet two hops away. The vendor may not exist anymore, the operating system stopped receiving updates years ago, and replacing it means replacing the machine it runs. So stop trying to fix the machine and start controlling what can reach it.

The old way

Try to fix the machine

  • Wait for a vendor patch that never comes
  • Install an endpoint agent the controller cannot run
  • Plan a replacement nobody will fund
  • Hope nothing finds it
The contained way

Control what can reach it

  • Only the engineering workstation and the historian can reach it
  • Internet access blocked entirely
  • Traffic mirrored to a monitoring tool
  • Known good configuration backup kept offline

A legacy controller talks to the same two or three devices every day of its life, so the first unusual connection is an unmistakable signal. Then keep a known good backup of every program and configuration, offline, so a compromised controller is a one hour rebuild instead of a week of calling retired engineers. Our backup and disaster recovery team treats PLC programs and HMI projects as first class backup targets, which is still rare among IT providers in Minnesota.

Page 2 of the article: gap one and gap two side by side, with the four step segmentation plan that does not stop production.
Page 2 of the article: gap one and gap two side by side, with the four step segmentation plan that does not stop production.

Gap two: network segmentation for manufacturers without stopping production

When accounting, email, the warehouse scanners and the CNC line all share one network, a phishing email in the front office is a production problem. Ransomware spreads sideways, and a flat network gives it nowhere to stop. Segmentation puts walls between zones: office, plant, each production cell, vendor access. Traffic that crosses a wall has to be allowed on purpose.

Most plants can do this with the firewall and switches they already own, plus a few weekends of planned cutovers.

  1. Inventory and mapPassive discovery of every device on the plant network, grouped by what it talks to.
  2. Define zonesOffice, plant core, production cells, vendor access, cameras and building systems. Six zones cover almost every plant.
  3. Build the wallsVLANs and firewall policies between zones, starting with office to plant. Cut over on weekends, one zone at a time.
  4. Monitor the crossingsAlert on any new conversation between zones. That alert is your early warning system.

Segmentation also makes compliance easier. CMMC and customer questionnaires ask how you protect systems that handle controlled information, and "they are in their own zone" is a very good answer. For the practices around the walls, read our companion piece on cybersecurity best practices for manufacturing companies.

Gap three: the knowledge that lives in two heads

The third gap turns an incident into a crisis. Ask who knows the password to the HMI on line three, where the latest PLC program is saved, or which vendor to call when the packaging line faults. If the answer is a person instead of a document, you have found the gap. Closing it is unglamorous, and it is mostly a list.

  • A credential vault for every machine, HMI and vendor portal login, instead of sticky notes.
  • A runbook for each critical machine: how it starts and stops, where its program lives, who to call.
  • A network diagram that matches reality, updated when the gap two walls go in.
  • A cross trained backup for every key role on the floor and in IT.
  • A vendor contact list that does not depend on one person's phone.
The payoff is speed

Documentation decides how long recovery takes

Documentation does not stop an attack. It decides whether recovery takes four hours or four days. In every manufacturing incident we have worked, the plants with current runbooks and offline configuration backups were back in production first.

This is where a co-managed IT partner earns its keep for a plant with one or two internal IT people. A partner cannot support what is undocumented, so documentation gets built as routine, and your IT lead stops being a single point of failure.

Page 3 of the article: gap three, the 90 day plan and the two numbers that matter, 90 days and zero machines replaced.
Page 3 of the article: gap three, the 90 day plan and the two numbers that matter, 90 days and zero machines replaced.

A 90 day plan to close all three gaps, zero machines replaced

Here is the plan we run with manufacturers from Bloomington to St. Cloud: visibility first, walls second, proof of recovery third.

90days to close all three gaps
0machines replaced to get there
PhaseWhat gets doneWhat you can say afterward
Days 1 to 30: see everythingAsset inventory, network map, credential vault, MFA on every account that can reach the plantWe know what is on the floor and who can reach it
Days 31 to 60: build the wallsOffice to plant segmentation, vendor access through a brokered jump host, internet blocked for controllersA phishing email in accounting cannot reach a PLC
Days 61 to 90: prove recoveryImmutable backups of every machine configuration, one real restore test, runbooks for the top ten systemsWe can rebuild any machine configuration in an hour
OngoingManaged detection on every Windows device, a 24/7 response team, a quarterly review of the three gapsSomeone is watching on Friday night

The ongoing row is where most plants need help, which is why our cybersecurity services pair managed XDR on every Windows device with human analysts who can isolate a machine at 2 a.m.

Where IT support for Twin Cities manufacturers starts

Three moves this month, none requiring a purchase order.

  1. Ask the three questionsWho knows the HMI password on your most important line? Can a laptop in accounting ping a controller? When was a machine configuration last restored from backup?
  2. Pick the first wallOffice to plant is the first segment. Put it on the calendar for a weekend in the next 60 days and name the owner.
  3. Get an outside readA free 30 minute Security Readiness Snapshot with Solution Builders tells you which of the three gaps is open in your plant before an attacker finds out, whether or not you ever work with us.
You do not have to modernize the plant to secure it. You have to contain what is old, separate what is connected and write down what is in people's heads.Solution Builders Security Practice

Solution Builders has provided IT support for manufacturers across the Twin Cities and Greater Minnesota since 1995, from Bloomington. Our 50+ engineers and 24/7 security operations center serve plants with 25 to 500 employees, and the Secure pillar of our RISE framework is built around these three gaps.

Page 4 of the article: three free playbooks that go deeper, including the Co-Managed IT Playbook on eliminating key person risk.
Page 4 of the article: three free playbooks that go deeper, including the Co-Managed IT Playbook on eliminating key person risk.

Plant floor security for Twin Cities manufacturers

Solution Builders has worked on Minnesota plant floors since 1995. From Bloomington, our 50+ engineers and 24/7 security operations center support manufacturers with 25 to 500 employees across Minneapolis, St. Paul and Greater Minnesota, including defense suppliers, food processors and medical device makers with a plant outside the metro and an office inside it. Related services: Cybersecurity, Data Backup and Disaster Recovery, Co-Managed IT, CMMC Compliance. Contact us or book a 30 minute call.

Free download

Get the three gaps guide as a PDF

Four pages you can hand to your plant manager and your IT lead: the three gaps explained, the segmentation plan that does not stop production, the 90 day checklist and pointers to three free playbooks that go deeper.

  • The three gaps, with the fix for each
  • A four step segmentation plan for a live floor
  • The 90 day checklist, phase by phase
  • Links to the CMMC and Co-Managed IT playbooks

No form, no gate. Share it with your leadership team.

How to Improve Cybersecurity in Manufacturing preview
FAQ

Questions Twin Cities leaders ask about plant floor security.

Contain what you cannot patch, separate what is connected and document what lives in people's heads. Put legacy controllers behind firewall rules that allow only known devices, block their internet access and keep offline configuration backups. Segment the office from the plant with switches you own. Build a credential vault and runbooks for critical machines. All of it fits in 90 days with zero machines replaced.
Segmentation divides one flat network into zones such as office, plant core, production cells and vendor access, with a firewall policy deciding what can cross between them. For a midsized plant it usually takes a few weekends of planned cutovers using the switches already in place. The first wall, office to plant, stops a phishing email in accounting from becoming a production outage.
A good program covers the plant floor, not just the office: passive asset discovery, OT to IT segmentation, brokered vendor remote access, managed XDR with a 24/7 response team, immutable backups of machine configurations with restore tests, and documentation so recovery does not depend on one person. Solution Builders delivers this from Bloomington for Twin Cities manufacturers for a fixed monthly fee.
Tribal knowledge risk is when critical information, such as an HMI password, the latest PLC program or the right vendor to call, exists only in one or two people's heads. It does not cause attacks, but it stretches every outage. Reduce it with a credential vault, a runbook per critical machine, an accurate network diagram and a cross trained backup for each key role.