ISO 27001 Content Hub
ISO 27001 in Manufacturing
Relevant controls, OEM expectations, TISAX differentiation, and realistic time and budget frames for manufacturing companies.
Manufacturing companies are facing a compliance pressure in 2026 unlike anything before. OEMs and Tier-1 suppliers demand watertight information security from their supply chains, cyber attacks on mid-market manufacturers have doubled within two years, and with NIS2 a significant share of industrial production is now directly regulated for the first time. ISO 27001 in this environment is no longer just a quality signal; it is often the formal prerequisite for remaining in a bidding process at all.
At the same time, manufacturing has specifics that make ISO 27001 adoption look different from a pure IT service provider. The convergence of IT and OT, historically grown shop-floor networks, long machine life cycles, and a dense network of external service providers are the reality you work with. This guide shows you which controls have the greatest leverage in manufacturing, what you should realistically plan for in time and budget, and how ISO 27001 interlocks with TISAX and NIS2.
Why ISO 27001 in Manufacturing
Pressure comes from three directions simultaneously. First, automotive OEMs such as Volkswagen, BMW, or Daimler require TISAX from strategic suppliers, which is itself built on ISO 27001. Second, pharmaceutical and aerospace OEMs expect ISO 27001 directly as a supplier gate, often as part of Tier-1 or Tier-2 qualification. Third, NIS2 applies to manufacturers falling under Annexes I and II of the directive, from chemicals to machine building to food. Any company with more than EUR 10 million in annual revenue and more than 50 employees is often directly affected.
Operational risk adds to the picture. A ransomware incident in a production environment does not only take IT down; it halts manufacturing. Every day of downtime costs a mid-sized manufacturer a six-figure amount. ISO 27001 forces you to tackle exactly the topics that decide the scale of damage in an emergency, such as backup strategy, network segmentation, and business continuity.
Relevant Controls for Manufacturing
Not every one of the 93 Annex A controls carries equal weight in manufacturing. The following eight controls deserve particular care, because they address exactly the risks where manufacturing companies regularly stumble during audits.
A.5.19 to A.5.23
Supplier and Supply Chain
From contract to audits to cloud use. Manufacturers typically operate 30 to 80 external service providers, from maintenance firms to MES vendors. Every one of them is an attack surface.
A.8.9
Configuration Management
A sore point for shop-floor systems. Machine controllers often still run on Windows 7 or XP, unpatched, with default credentials. Auditors look here very closely.
A.8.22
Network Segmentation
Separation of office IT, production network, and remote access for maintenance. A flat network is the horror scenario both in the audit and in a real incident.
A.7.1 to A.7.4
Physical Security
Access controls to production halls, server rooms, external warehouses. Companies handling prototypes or sensitive customer drawings need to do significantly more than an average office setup.
A.8.13
Backups
Not just documented but tested. 3-2-1 rule, offline copies, regular restore tests. In a ransomware incident, that decides between one day of downtime and three weeks.
A.5.30
Business Continuity
How do you keep producing when the ERP fails? Sounds trivial, but in practice it is the biggest weak point for many mid-market manufacturers during an audit.
A.5.7
Threat Intelligence
Relevant for all manufacturers in NIS2-regulated sectors. BSI bulletins and industry-specific warnings must be processed in a documented way.
A.5.24 to A.5.27
Incident Management
NIS2 reporting duties within 24 hours. Without a rehearsed process that is unrealistic. Audits check whether your processes actually work in an emergency.
Timeline and Budget
For a mid-sized manufacturer with 100 to 500 employees, an ISO 27001 implementation realistically takes 10 to 14 months. If you already hold a TISAX assessment or maintain a well-kept IT-Grundschutz compendium, you land at the lower end. Starting from zero is more likely 14 to 18 months.
Costs fall into three blocks. The certification auditor costs between EUR 8,000 and EUR 20,000 for Stage 1 plus Stage 2 depending on company size, plus annual surveillance audits of EUR 3,000 to EUR 5,000. Internal effort is realistically 120 to 200 person-days spread across CISO, IT, HR, and business units. External consulting is optional and costs between EUR 15,000 and EUR 60,000 depending on maturity and scope. Self-service with a platform like Kopexa reduces the consulting share significantly but does not replace internal effort.
Overall, you land at EUR 30,000 to EUR 100,000 in the first year, depending on how much is bought externally. Afterwards, expect EUR 5,000 to EUR 15,000 per year. Detailed numbers are in our ISO 27001 cost overview.
Framework Synergies: ISO 27001, TISAX and NIS2
The most frequent question manufacturing customers ask us is: ISO 27001 or TISAX. The honest answer is, it depends on your customers. TISAX is effectively mandatory in the German automotive environment, ISO 27001 is internationally recognised and covers a considerably broader scope. For most manufacturers, the combination makes sense because TISAX builds on ISO 27001 as a foundation and you collect both proofs in parallel.
Our comparison ISO 27001 vs. TISAX lays out in detail which proof covers which use case. If you fall under NIS2, an ISO 27001 ISMS already covers around 85 percent of the requirements from Art. 21 NIS2UmsuCG. The remaining 15 percent are mainly reporting duties and management responsibility, which you express as additional clauses in ISO terms.
Typical Pitfalls in Manufacturing
- 1.Shop floor declared "out of scope": Rarely works. If production systems communicate with the office IT or process production data, they belong in scope. Anything else puts you in an awkward position during the audit.
- 2.Maintenance access forgotten: VPN access for external maintenance firms is often set up ad hoc and never controlled again. In audits, that is a classic major finding. Every external access belongs in a structured access management process.
- 3.Legacy machines without patch strategy: A 20-year-old CNC machine cannot be patched. The solution is not to declare control A.8.9 as "not applicable" but to document compensating measures such as network segmentation and strict access control.
- 4.Business continuity remains theoretical: A BCM document without exercises is worthless in the audit. At least one annual tabletop exercise with documented results is the minimum standard.
FAQ: ISO 27001 in Manufacturing
Do I need ISO 27001 or TISAX as a supplier?
It depends on your customer. Automotive OEMs typically require TISAX; other industries such as pharma, aerospace, or machine building accept ISO 27001 directly. For a broader international footprint, ISO 27001 is the better choice, and you add TISAX when needed. See our comparison.
Does OT have to be in scope?
Not necessarily every machine, but every system that communicates with office IT or processes business-critical data. In practice that means: MES, SCADA gateways, engineering workstations, and maintenance access almost always belong in scope. Kopexa is your GRC tool for documentation and evidence collection, not an OT monitoring product.
How much does ISO 27001 cost for a mid-sized company with 250 employees?
Realistically EUR 40,000 to EUR 80,000 in the first year including certification and limited external consulting, plus 150 to 200 internal person-days. Afterwards, EUR 8,000 to EUR 12,000 per year for surveillance audits and running operations. With a self-service platform, tool costs alone start at EUR 249 per month.
Is ISO 27001 enough for NIS2?
ISO 27001 covers around 85 percent of NIS2 requirements. The remaining gaps are mainly NIS2-specific reporting duties (early warning within 24 hours, threat assessment within 72 hours) and the personal responsibility of management. Those can be cleanly integrated into an existing ISMS.
How do I handle legacy machines that cannot be patched?
Do not declare them "not applicable" in the Statement of Applicability; document compensating measures instead: strict network segmentation, no internet access, access control, monitoring. That is an auditable path. Details in our SoA guide.
Next Step
Start here:
Want to implement ISO 27001 with Kopexa?
14-day free trial, ISMS, risks, vendors, and audit workflows in one platform, hosted in Germany, from EUR 249 per month. Self-service or with a partner, whichever fits you.
Start for freeMore ISO 27001 Topics
Start
Certification
Industry Applications
Framework Mapping
Let's talk about your ISO 27001 implementation
Free & non-binding