Two operators at a control-room desk with a row of monitors, a laptop and keyboards

OT/ICS security

OT/ICS security for small and mid-sized manufacturers: where to start with no dedicated team

Last updated:

OT/ICS security for a small manufacturer with no dedicated team should start with a passive asset inventory of the shop floor, move next to a handful of CISA's prioritized Cross-Sector Cybersecurity Performance Goals, and treat IEC 62443-2-1 as the longer-term growth path — in that order, and without installing agents on a 15-year-old controller. A food processor with one PLC-driven line, a parts machine shop with three CNC cells, or a regional utility workshop usually has no one whose job title includes "OT security." Most OT/ICS guidance, including the long-running NIST SP 800-82 and the IEC 62443 series, is written at a scale that assumes a security team, a budget line and a segmented network already exist; this guide is for the plant that has none of those yet.

Key takeaways

  • Because every later decision depends on the list.
  • The instinct to run the same vulnerability scanner used on office laptops against the shop floor is a common and risky mistake.
  • Copy traffic from one switch, record it, and leave production alone.
  • Treat the CPGs as a floor, not a finish line: CISA is explicit that they are "a floor — not a ceiling" of protections, and they are voluntary guidance, not a legal requirement.

Why start with what you have, not what you should buy?

Because every later decision depends on the list. CISA's own OT asset-inventory guidance puts it directly: "without an inventory, organizations do not know what they have and what should be secured." Before any framework, tool or policy, a small manufacturer needs a current list of what is actually on the shop-floor network: PLC models and firmware versions, HMI software, drives, gateways, remote-access devices, and how they are connected. Asset inventory is itself one of CISA's own Cross-Sector Cybersecurity Performance Goals (CPGs), not an optional preliminary step.

Why is "just scan it" the wrong first move?

The instinct to run the same vulnerability scanner used on office laptops against the shop floor is a common and risky mistake. Many PLCs, drives and legacy gateways were built decades ago with a minimal network stack, and were never tested against the kind of traffic an IT-style active scanner generates. Industry practice built around NIST SP 800-82 Rev. 3 treats active scanning of a live OT network as a real availability and safety risk, since it can overload or crash a legacy device's network stack, and instead favours passive, non-intrusive discovery — reading a copy of network traffic from a SPAN port or a network TAP — as the safer way to build an inventory and watch for anomalies without touching production. Active scanning, where it is used at all, is normally kept to a scheduled maintenance window or a test bench, not the live line.

This is also why "install an agent on every device" rarely works in OT the way it does in IT: most PLCs and drives have no supported way to run one.

How do you run a passive capture without touching the line?

Copy traffic from one switch, record it, and leave production alone. A workable first capture for a small plant:

  1. Pick the switchwhere the cell controllers, HMIs and the engineering PC meet. On a flat network that is usually the core switch.
  2. Mirror, don't routeConfigure a SPAN (port mirror) on a managed switch, or insert a passive TAP on the uplink if the switch cannot mirror. Either way the recorder only listens.
  3. Record across a normal production cycle, including a shift change and, if possible, a vendor remote-support session, so the capture shows real traffic rather than an idle weekend.
  4. Write down what the capture cannot see: serial links, 4-20mA loops, wireless meshes and anything on another switch.
  5. Turn the capture into a list: hosts, the protocols each one speaks, who initiates sessions, and every connection that leaves the plant.

Have the maintenance lead or integrator check the switch change. Port mirroring is low-risk, but it is still a change to production equipment.

What sequence works for a plant with no OT security team?

Step What it is Why first
1. Passive asset inventory Read mirrored shop-floor traffic (SPAN/TAP) to list devices, protocols, firmware versions You cannot secure what you have not identified; CISA treats this as foundational, not optional
2. Pick a small set of CPGs Start from CISA's prioritized, cross-sector list rather than a full framework CISA designed the CPGs specifically to be achievable for small and medium organizations with limited resources
3. Segment and restrict remote access Separate the OT network from the office network; lock down vendor/contractor remote-access paths The highest-value, lowest-cost control once you know what is connected
4. Add monitoring, still passive Watch for new devices or unusual traffic patterns against the baseline from step 1 Builds on the same non-intrusive technique, no new risk to production
5. Grow into IEC 62443-2-1 Build a documented cybersecurity management system (CSMS) as the plant matures The structured next step once basics are in place, not a starting point

How do CISA's Cross-Sector Performance Goals fit this gap?

The Cross-Sector Cybersecurity Performance Goals (CPGs) exist specifically because CISA recognised most critical-infrastructure operators, manufacturing among them, are not large enough to run a full NIST CSF programme on day one. CISA's own description frames them as a tool to help "small- and medium-sized organizations kickstart their cybersecurity efforts," and its CPG 2.0 report (December 2025) states its goal-selection criteria require every goal to be "reasonably straightforward and not cost-prohibitive for small- and medium-sized entities to successfully implement." The 2.0 revision also merged what used to be separate IT and OT goal lists into one shared set, specifically so a small manufacturer running both an office network and a shop floor does not need two frameworks.

Treat the CPGs as a floor, not a finish line: CISA is explicit that they are "a floor — not a ceiling" of protections, and they are voluntary guidance, not a legal requirement. A small manufacturer that also makes or integrates machinery sold into the EU may separately have legal obligations under the Machinery Regulation or the Cyber Resilience Act, which run on their own statutory timelines regardless of what voluntary programme a plant follows internally.

Which CPG 2.0 goals should a small plant pick first?

The ones CISA itself rates high impact and low or moderate cost. Every goal in the CPG 2.0 report carries a Cost, Impact and Ease of Implementation rating and, for most, an OT note. A short list for a plant with no team:

Goal CISA rating (cost / impact / ease) What the OT note asks
2.A Manage Organizational Assets Low / High / Moderate Update critical IT and OT assets "on a more frequent basis"
3.A Change Default Passwords Low / High / Simple Change defaults on existing OT systems; where hard-coded, document compensating controls and watch login attempts
2.E Document Network Topology Low / High / Moderate Cover all IT and OT networks; review annually
3.F Implement Multifactor Authentication Moderate / High / Moderate MFA on every remotely accessible account, including vendor accounts; if unavailable, remove remote access
3.O Maintain System Backups & Restoration Ability High / High / Moderate Back up "device configurations, roles, engineering drawings, and tools"; test at least yearly
2.B Mitigate Known Vulnerabilities High / High / Complex Where patching is unsafe, apply and record compensating controls such as segmentation and monitoring
3.S Secure Internet-Facing Devices Moderate / High / Complex Management interfaces "should never be exposed to the public internet"
3.I Implement Logical/Physical Network Segmentation High / High / Complex Physically segment OT enclaves where applicable

The first three are cheap and can start this month. 3.F and 3.S are where most small-plant incidents begin; see also CISA's directive on internet-exposed management interfaces.

Why are legacy devices and remote access the recurring weak points?

Two problems show up repeatedly in small manufacturing environments, and neither is solved by a tool alone:

  1. Legacy PLCs and drives with no security features to turn onCompensating controls — network segmentation, restricting who can reach the device, monitoring its traffic for anomalies, and physical access control — carry more of the load here than anything installed on the device itself, because there is often nothing to install.
  2. Vendor and integrator remote accessA machine builder's or OEM's remote-support VPN is frequently the least controlled path into the plant network: shared credentials, always-on tunnels, no session logging. Reviewing and tightening these connections is consistently one of the highest-value, lowest-cost steps a small plant can take, and it does not require new hardware.

Recent US federal guidance reinforces the same direction at a national-infrastructure scale: the April 2026 joint guide from CISA, the Department of War, DOE, FBI and DOS on applying zero-trust principles to OT describes the task as addressing "technology gaps from legacy infrastructure, operational constraints, and the safety requirements that come from the critical link between cybersecurity and physical processes" — the same constraints a small plant faces, just without the enterprise budget to match.

How do you lock down vendor remote access?

List every path, then give each one an owner, MFA and an off switch. A checklist built from CPG 3.F and 1.E (Manage Risks from Managed Service Providers):

  • Every path on one page: VPN accounts, remote-desktop tools, cellular routers in machine cabinets, cloud portals.
  • One named account per vendor technician, no shared logins, and MFA on each. If a path cannot do MFA, CPG 3.F says remove it or add segmentation.
  • Off by default. The tunnel opens for a ticketed session and closes afterwards.
  • Land in a jump host or DMZ, not on the control network itself.
  • Log sessions and keep the logs off the shop floor.
  • Write it into the contract. CPG 1.E asks that contracts "detail how and when MSPs notify the customer of an incident." For integrators, IEC 62443-2-4 sets service-provider requirements.

Worked example: a 60-person machine shop's first quarter

Synthetic example, not a real company. Six CNC cells, two PLC-driven assembly lines, one office network, no security staff. One person spends about half a day a week on this.

Month Work Result
1 One-week SPAN capture on the core switch; list hosts and protocols 48 OT hosts found, 9 more than the spreadsheet; one cellular router in a line cabinet
1 CPG 3.A: change default passwords on HMIs and switches Two HMIs with hard-coded passwords, so log watching instead
2 CPG 2.E: network drawing; separate office and OT VLANs with one firewall Office laptops can no longer reach PLCs
2 Vendor access per the checklist above Three always-on tunnels closed; one vendor moved to on-request sessions
3 CPG 3.O: offline copies of PLC programs, HMI projects and drive parameters; one test restore Restore took four hours, documented

What changes if you also build machines or devices?

You gain legal obligations as a manufacturer, separate from the voluntary CPGs. The EU Machinery Regulation (EU) 2023/1230 applies from 20 January 2027 and includes protection against corruption among its health and safety requirements; see the Machinery Regulation guide. The Cyber Resilience Act (EU) 2024/2847 covers products with digital elements: reporting of actively exploited vulnerabilities has applied since 11 September 2026, and the remaining obligations apply from 11 December 2027; start with the CRA checklist for device makers. The plant work above helps here too: the same inventory, default-password and remote-access habits are what customers will ask of your machines. CISA's own support resource for CPG 3.A is titled "How Manufacturers Can Protect Customers by Eliminating Default Passwords."

What should a small manufacturer do this quarter?

  1. Get a passive read of the shop-floor networkbefore buying anything — you need the device list before you can prioritize.
  2. Pick 3-5 CPGs that match your biggest gaps, not the full list; CISA designed them to be implemented incrementally.
  3. Separate the OT network from the office networkif it is not already, and inventory every remote-access path a vendor or integrator uses.
  4. Document what you find, even informally — it is the starting evidence for IEC 62443-2-1 later and for any customer or insurer questionnaire today.

SoftWSP's OT Snapshot works from Zeek and ICSNPP logs of a passive capture, so nothing is installed on the OT network and nothing is actively scanned. It builds a host-by-port inventory, labels hosts that speak Modbus, S7comm, DNP3, EtherNet/IP or BACnet, and lists remote-access sessions (SSH, Telnet, RDP, VNC) that cross from outside the private address range. A capture does not reveal firmware versions reliably; from a component list, SoftWSP matches models and versions against NVD, CISA KEV, FIRST EPSS and CISA ICS advisories. An engineer reviews every report. For the device-maker side of the supply chain feeding into your plant, see device firmware security.

What are the common pitfalls?

  • Buying a monitoring product before the inventory exists.
  • Running an IT vulnerability scanner against the live line.
  • A "temporary" vendor tunnel that stays open for years.
  • Backups of PLC programs that were never restored once.
  • Treating the CPGs as a certificate. They are a floor.

This guide is general information, not a substitute for a site-specific risk assessment.

Put this guide to work

Frequently asked questions

Our factory has no dedicated OT security team. Where do we actually start?

With an asset inventory, not a tool purchase. CISA's own OT asset inventory guidance states plainly that "without an inventory, organizations do not know what they have and what should be secured," and treats building one as one of its Cross-Sector Cybersecurity Performance Goals (CPGs). For a small manufacturer, the practical starting point is a passive read of shop-floor network traffic — PLCs, HMIs, drives and their IP addresses, protocols and firmware versions — before deciding what, if anything, to install.

Can we just apply the same enterprise IT security tools we already use in the office?

Not directly to the OT network. CISA's own framing of the Cross-Sector Cybersecurity Performance Goals is that they are designed to help "small- and medium-sized organizations kickstart their cybersecurity efforts" with a small number of high-impact actions, rather than a comprehensive enterprise programme — CPG 2.0 explicitly merged separate IT and OT goal sets into shared ones so a small organization can use one framework "without confusion over domain-specific goals." Even so, OT devices themselves differ from IT endpoints: many PLCs and drives cannot safely run a host agent or tolerate an unplanned reboot, which is why discovery methods matter as much as the framework chosen.

Why does passive network monitoring come up so often for OT instead of just scanning the network?

Because many OT devices are old, resource-constrained, and were never built to handle unexpected network traffic gracefully. Industry practice built around NIST SP 800-82 treats active, IT-style scanning of a live OT network as a risk to availability and even safety, since it can overload a legacy controller's network stack, and instead favours passive, non-intrusive techniques — reading mirrored traffic from a SPAN port or network TAP — as the safer default for building an inventory and watching for anomalies, reserving active scanning for maintenance windows or a test bench.

Are the CISA Cross-Sector Cybersecurity Performance Goals mandatory for a small manufacturer?

No. CISA's own CPG 2.0 report (December 2025) describes the CPGs as "a prioritized subset of IT and OT cybersecurity practices" and states CISA intends them to be "a floor — not a ceiling." They are voluntary, cross-sector guidance, not a regulation; a small manufacturer selling machines or components into the EU may separately need to meet the Machinery Regulation or Cyber Resilience Act, which are legal obligations with their own timelines.

We outgrow the basics — what's the next step up from CPGs?

IEC 62443-2-1, the part of the IEC 62443 series that sets out an asset owner's security program (a cybersecurity management system, not a single checklist), is the usual next step once a plant has its inventory and basic controls in place. It is a much larger undertaking than the CPGs, graded by a maturity model rather than a pass/fail check, so most small manufacturers use it as a direction to grow into rather than a near-term target.

Sources

  1. CISA: Foundations for OT Cybersecurity — Asset Inventory Guidance for Owners and Operators
  2. CISA: Cross-Sector Cybersecurity Performance Goals
  3. CISA: Cross-Sector Cybersecurity Performance Goals, Version 2.0 (PDF, December 2025)
  4. CISA, DoW, DOE, FBI, DOS: Adapting Zero Trust Principles to Operational Technology (29 April 2026)
  5. NIST SP 800-82 Revision 3: Guide to Operational Technology (OT) Security
Was this guide helpful?

In this cluster

OT/ICS security for small and mid-sized manufacturers: where to start with no dedicated team