Supply chain as the weakest link in OT cybersecurity
A modern factory is not an isolated entity — it is a node in an extensive network of component suppliers, system integrators, SCADA software vendors and service companies. Each of these entities has potential access to the production network, and compromising just one opens a path to all its customers.
Supply chain attacks have become the preferred method for advanced APT groups and cybercriminals. Instead of attacking a well-protected factory directly, it is sufficient to compromise a smaller supplier with weaker security — and deliver malicious code through a trusted update channel.
Supply chain attack vectors in manufacturing
Compromised OT software
SCADA, DCS and MES vendors regularly deliver updates to their customers. Taking over the update infrastructure enables distribution of malicious code to hundreds of factories simultaneously. The SolarWinds attack (2020) demonstrated this technique in IT — in OT the consequences can be physical.
Malicious controller firmware
PLC and RTU controllers receive firmware updates from manufacturers. Compromising the firmware build process or distribution channel enables uploading modified software that manipulates physical processes. The Stuxnet attack used exactly this vector — modified code on Siemens S7-300 controllers destroyed Iranian centrifuges.
Infected service tools
Service companies and integrators use diagnostic laptops and tools that connect directly to OT networks. An infected service technician’s laptop is a direct bypass of all firewalls and segmentation.
Subcontractors with remote access
Many OT vendors require remote access to systems for monitoring, diagnostics and updates. Each such VPN connection is a potential gateway to the production network — if the vendor is compromised.
Real supply chain incidents in manufacturing
Toyota and Kojima Industries (2022)
A ransomware attack on Kojima Industries — a small plastic component supplier — forced Toyota to halt all 14 factories in Japan. Kojima had a direct connection to Toyota’s just-in-time systems. One day of downtime = 13,000 cars not produced.
NotPetya and Maersk/Mondelez (2017)
An attack on Ukrainian tax software MeDoc spread globally. Maersk lost $300M, Mondelez $188M. Cadbury chocolate factories in Australia and Tasmania were halted — all because of an infected accounting software update.
ASUS Shadow Hammer (2019)
Compromising the ASUS Live Update system affected a large number of users, including workstations in industrial environments. This shows that even hardware updates can be attack vectors.
OT supply chain protection strategies
Supplier inventory and classification
The first step is a complete supply chain map from a cybersecurity perspective:
- Tier 1 (critical): suppliers with direct OT network access — SCADA vendors, integrators, service companies
- Tier 2 (important): component suppliers, firmware manufacturers, software vendors
- Tier 3 (indirect): sub-suppliers of Tier 1 and 2
Cybersecurity requirements in contracts
Every contract with a supplier that has OT access should include:
- Certification requirements (ISO 27001, IEC 62443)
- Obligation to report security incidents
- Right to cybersecurity audit
- Update security requirements (digital signing, integrity verification)
- Liability clauses for security breaches
Supplier access control to OT
Technical protection measures:
- Jump server as the only entry point for supplier remote access
- Session recording — full logging of all service activities
- Temporary access — VPN activated only during service, not permanently
- Individual accounts for each technician with granular access
- Media verification — scanning laptops and USB drives before connecting to OT
Software and firmware integrity verification
- Requiring digital signatures for all OT updates
- Testing updates in a lab environment before production deployment
- Monitoring PLC configuration changes and comparing against baseline (golden config)
- Software Bill of Materials (SBOM) from software vendors
External connection monitoring
A SOC with OT competencies should monitor:
- All remote access connections to the OT network
- Traffic to/from supplier update infrastructure
- Anomalies in industrial protocols after updates
- Unauthorized connections to external IP addresses
NIS2 supply chain requirements
The NIS2 directive directly addresses supply chain security. Important entities (including manufacturing) must:
- Conduct ICT supplier risk assessments
- Include cybersecurity in supplier selection processes
- Continuously monitor supplier security
- Report supply chain incidents within 24 hours
Supply chain security audit
The nFlo OT/ICS security audit includes supply chain assessment:
- Mapping all external connections to the OT network
- Evaluating update channel security
- Verifying supplier access controls
- Analyzing contracts for cybersecurity requirements
- Implementation recommendations with prioritization
Do you know how many suppliers have access to your OT network? Schedule a security audit — we will identify risks in your supply chain.
Cybersecurity for Your Industry
Learn more about cybersecurity in your industry:
Related topics
See also:
Frequently asked questions
What is a supply chain attack in manufacturing?
A cyberattack where criminals compromise a supplier — component manufacturer, SCADA software vendor or service company — to deliver malicious code through a trusted channel into the victim's production network.
Why are supply chain attacks difficult to detect?
Malicious code arrives from a trusted source — as a software update, new controller firmware or diagnostic tool. Traditional security systems treat these channels as trusted and do not scan their content.
How does NIS2 regulate supply chain security?
NIS2 requires important entities (including manufacturing) to assess supplier risks, include cybersecurity requirements in contracts and monitor security across the entire supply chain.
Where to start securing supply chain in a manufacturing company?
Start with an inventory of all suppliers with OT network access, assess their cybersecurity maturity and implement security requirements in contracts. Then segment access and monitor external connections.
