{"id":1756,"date":"2026-11-04T00:00:31","date_gmt":"2026-11-04T00:00:31","guid":{"rendered":"https:\/\/mestric.com\/varnost-mes-sistema\/"},"modified":"2026-11-04T00:00:34","modified_gmt":"2026-11-04T00:00:34","slug":"varnost-mes-sistema","status":"publish","type":"post","link":"https:\/\/mestric.com\/sl\/varnost-mes-sistema\/","title":{"rendered":"MES security: how to protect your production system"},"content":{"rendered":"<\/p>\n<p>MES security means protecting the system that sits between your machines and your business network: who can log in, what it can change, how it connects to equipment, and how fast you can recover if something goes wrong. It is not the same as worker or machine safety, although a security failure can end up harming both. Below you will find the main risks, the controls that matter most, the Slovenian and EU rules to check, and a checklist for assessing any MES before you buy.<\/p>\n<div data-blg-cta=\"after_tldr\" data-blg-cta-layout=\"banner\" style=\"margin:28px 0;font-family:-apple-system, BlinkMacSystemFont, &apos;Segoe UI&apos;, Roboto, Helvetica, Arial, sans-serif\">\n<div style=\"border-radius:26px;padding:min(22px,3.2vw);background:radial-gradient(circle at 100% 0%,#e3eeec 0 150px,rgba(255,255,255,0) 151px),radial-gradient(circle at 0% 100%,#e3eeec 0 130px,rgba(255,255,255,0) 131px),linear-gradient(180deg,#edf3f2 0%,#f6f9f9 100%)\">\n<div style=\"background:#ffffff;border-radius:18px;overflow:hidden\">\n<div style=\"padding:34px 30px;text-align:center\">\n<div style=\"margin:0 0 18px\"><span style=\"display:inline-block;max-width:100%;border-radius:999px;padding:6px 13px;font-size:12px;font-weight:800;letter-spacing:0.1em;text-transform:uppercase;line-height:1.3;background:#669f94;color:#ffffff\">Mestric<\/span><\/div>\n<div style=\"font-size:26px;font-weight:800;line-height:1.2;letter-spacing:-0.01em;color:#1f2937;margin:0\">Keep Production Data in View<\/div>\n<div style=\"width:56px;height:6px;border-radius:3px;background:#669f94;margin:12px 0 14px;margin-left:auto;margin-right:auto\"><\/div>\n<div style=\"font-size:15px;line-height:1.55;color:#64748b;margin:0 0 24px;max-width:44em;margin-left:auto;margin-right:auto\">Mestric connects with manufacturing equipment to track performance, quality parameters and downtime, helping teams monitor production in real time.<\/div>\n<p><a href=\"https:\/\/mestric.com\/sl\/\" style=\"display:inline-flex;align-items:center;gap:9px;border-radius:10px;font-weight:700;font-size:15px;text-decoration:none;padding:13px 22px 13px 26px;background:#669f94;color:#ffffff\">Explore Mestric<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<h2 id=\"tldr\" tabindex=\"-1\">TL;DR<\/h2>\n<ul>\n<li>An MES is a sensitive target because it links the production floor with the corporate network, so a change in its data can affect real products.<\/li>\n<li>The core controls are network segmentation, multi-factor authentication, least-privilege access, tested patching and offline backups.<\/li>\n<li>In Slovenia, ZInfV-1 transposes NIS 2: if your company is in scope, you must apply risk-management measures and report significant incidents.<\/li>\n<li>Put security requirements into the MES specification and acceptance tests before go-live, including supplier and remote access.<\/li>\n<li>Test your incident response plan with a table-top exercise before you need it.<\/li>\n<\/ul>\n<h2 id=\"table-of-contents\" tabindex=\"-1\">Vsebina<\/h2>\n<ul>\n<li><a href=\"#what-mes-security-covers-and-what-it-does-not\">What MES security covers, and what it does not<\/a><\/li>\n<li><a href=\"#why-the-mes-is-a-special-target\">Why the MES is a special target<\/a><\/li>\n<li><a href=\"#risks-to-plan-for\">Risks to plan for<\/a><\/li>\n<li><a href=\"#controls-that-matter-most\">Controls that matter most<\/a><\/li>\n<li><a href=\"#slovenian-and-eu-rules-to-check\">Slovenian and EU rules to check<\/a><\/li>\n<li><a href=\"#assess-mes-security-before-you-buy\">Assess MES security before you buy<\/a><\/li>\n<li><a href=\"#monitor-respond-recover\">Monitor, respond, recover<\/a><\/li>\n<li><a href=\"#our-perspective\">Our perspective<\/a><\/li>\n<li><a href=\"#see-mestric-mes-in-a-real-production-setting\">See Mestric\u2122 MES in a real production setting<\/a><\/li>\n<li><a href=\"#faq\">Pogosto zastavljena vpra\u0161anja<\/a><\/li>\n<li><a href=\"#sources\">Sources<\/a><\/li>\n<\/ul>\n<h2 id=\"what-mes-security-covers-and-what-it-does-not\" tabindex=\"-1\">What MES security covers, and what it does not<\/h2>\n<p>Two meanings of \u201csecurity\u201d get mixed up in factories. Occupational and machine safety protects people from machines: guards, emergency stops, risk assessments. Cybersecurity protects the machines and the software from people, or from malware. The EU Machinery Regulation now addresses both sides: <a href=\"https:\/\/www.helmholz.de\/media\/pdf\/72\/04\/86\/Helmholz_Whitepaper_IndustrialSecurity_EN.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">it adds protection of machines from people to the older focus on protecting people from machinery<\/a>.<\/p>\n<p>The two meet in practice. NIST notes that <a href=\"https:\/\/nvlpubs.nist.gov\/nistpubs\/specialpublications\/NIST.SP.800-82r3.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">operational technology cybersecurity is essential to safe and reliable operations, because incidents can endanger human life, damage the environment or harm equipment<\/a>. So a security question about your MES is also a safety and quality question.<\/p>\n<p>In practice, MES security has five parts:<\/p>\n<ul>\n<li><strong>Access:<\/strong> who can sign in, from where, and what they may change.<\/li>\n<li><strong>Data integrity:<\/strong> recipes, process norms, work orders and quality records must not be altered without a trace.<\/li>\n<li><strong>Availability:<\/strong> the system must keep running, or production must continue safely without it.<\/li>\n<li><strong>Connectivity:<\/strong> every machine, gateway and remote session is a possible way in.<\/li>\n<li><strong>Recovery:<\/strong> backups, documentation and a plan that work when the main network does not.<\/li>\n<\/ul>\n<h2 id=\"why-the-mes-is-a-special-target\" tabindex=\"-1\">Why the MES is a special target<\/h2>\n<p>An ERP system holds business data. An MES holds business data and also talks to the machines. Researchers describing attacks on smart factories call the MES <a href=\"https:\/\/documents.trendmicro.com\/assets\/white_papers\/wp-attacks-on-smart-manufacturing-systems.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">the most sensitive endpoint, because it bridges the production floor and the corporate network<\/a>. The same paper points out that even a slight alteration of the MES database could damage manufactured goods.<\/p>\n<p>That last point is worth dwelling on. A stolen file is a data problem. A quietly changed tolerance, recipe parameter or batch record is a quality problem you may find only when a customer complains. This is why integrity deserves as much attention as confidentiality.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/mestric.com\/wp-content\/uploads\/2026\/11\/1793604796628_Why-the-MES-is-a-special-target.jpeg\" alt=\"Why the MES is a special target\"><\/p>\n<h2 id=\"risks-to-plan-for\" tabindex=\"-1\">Risks to plan for<\/h2>\n<h3 id=\"production-stoppage\" tabindex=\"-1\">Production stoppage<\/h3>\n<p>The same research describes <a href=\"https:\/\/documents.trendmicro.com\/assets\/white_papers\/wp-attacks-on-smart-manufacturing-systems.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">denial-of-service attacks from malicious industrial IoT devices that can stop production<\/a>. Ransomware is the more familiar route: Dragos reports that <a href=\"https:\/\/innetworktech.com\/wp-content\/uploads\/2024\/08\/Dragos_WP_ManufacturingThreatScenarios_0923.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">ransomware can affect the MES and plant operations through IT and OT dependencies<\/a>. How badly depends partly on whether you can isolate the network and run operations independently of IT.<\/p>\n<h3 id=\"more-ways-in-as-networks-connect\" tabindex=\"-1\">More ways in as networks connect<\/h3>\n<p>Connecting machines to a live MES is the point of digital manufacturing, but it removes the old separation between office and plant. The research notes that <a href=\"https:\/\/documents.trendmicro.com\/assets\/white_papers\/wp-attacks-on-smart-manufacturing-systems.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">remote entry opportunities grow as IT and OT isolation decreases<\/a>, and that lateral movement from IT to OT can worsen the consequences of an attack.<\/p>\n<h3 id=\"weak-credentials-in-industrial-software\" tabindex=\"-1\">Weak credentials in industrial software<\/h3>\n<p>Vulnerabilities in industrial products are regularly published, including in Slovenia. In 2026 SI-CERT reported that <a href=\"https:\/\/www.cert.si\/en\/cve-2026-25600\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">a hard-coded secret in an industrial database component could let an attacker with local high privileges recover administrative credentials<\/a> and potentially manipulate industrial processes or disrupt operations. The lesson is general: ask every supplier how it handles credentials and how quickly it publishes fixes. For a wider catalogue of threats, see our overview of the <a href=\"https:\/\/mestric.com\/sl\/types-of-industrial-data-security-risks\/\" target=\"_blank\" rel=\"noopener\">types of industrial data security risks every plant must track<\/a>.<\/p>\n<h2 id=\"controls-that-matter-most\" tabindex=\"-1\">Controls that matter most<\/h2>\n<p>NIST\u2019s guide to OT security recommends defence in depth. For an MES, that translates into the following.<\/p>\n<table>\n<thead>\n<tr>\n<th>Area<\/th>\n<th>What to do<\/th>\n<th>Why it helps<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Network<\/td>\n<td>Segment IT and OT, with a DMZ between them<\/td>\n<td>Limits how far an intruder can move<\/td>\n<\/tr>\n<tr>\n<td>Access<\/td>\n<td>Multi-factor authentication and least privilege<\/td>\n<td>A stolen password alone is not enough, and users can change only what their job needs<\/td>\n<\/tr>\n<tr>\n<td>Ports and services<\/td>\n<td>Disable what is unused<\/td>\n<td>Fewer entry points<\/td>\n<\/tr>\n<tr>\n<td>Patching<\/td>\n<td>Risk-based, tested, planned in maintenance windows<\/td>\n<td>Fixes arrive without surprise downtime<\/td>\n<\/tr>\n<tr>\n<td>Backups<\/td>\n<td>Secure, out-of-band, with offline copies of critical systems<\/td>\n<td>Recovery does not depend on the compromised network<\/td>\n<\/tr>\n<tr>\n<td>Supply chain<\/td>\n<td>Manage supplier risk and restrict physical and logical access<\/td>\n<td>Third parties are a common route in<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These controls come from <a href=\"https:\/\/nvlpubs.nist.gov\/nistpubs\/specialpublications\/NIST.SP.800-82r3.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">NIST\u2019s Guide to Operational Technology Security<\/a>, which covers segmentation with DMZs, MFA, least privilege, disabling unused ports, out-of-band backups and a tested patch strategy.<\/p>\n<h3 id=\"patching-without-stopping-the-line\" tabindex=\"-1\">Patching without stopping the line<\/h3>\n<p>On the shop floor you cannot restart a system whenever a patch appears. Dragos notes that <a href=\"https:\/\/innetworktech.com\/wp-content\/uploads\/2024\/08\/Dragos_WP_ManufacturingThreatScenarios_0923.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">OT patching can require downtime, so risk-based alternative mitigations may be needed until a maintenance window<\/a>. In practice: keep an inventory of versions, rank vulnerabilities by their effect on your process, test patches on a copy, and schedule them with production planning. Where a patch must wait, tighten network rules around the affected system in the meantime.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/mestric.com\/wp-content\/uploads\/2026\/11\/1793604772603_Five-steps-for-patching-OT-systems-safely.jpeg\" alt=\"Five steps for patching OT systems safely\"><\/p>\n<h3 id=\"machine-connections\" tabindex=\"-1\">Machine connections<\/h3>\n<p>Every machine linked to the MES should have a defined, documented communication path: which device talks to which, on which port, in which direction. Anything outside that map should be blocked. If you are still planning the integration, our guide to <a href=\"https:\/\/mestric.com\/sl\/how-to-streamline-manufacturing-processes\/#step-2-integrate-digital-mes-solutions-with-equipment\" target=\"_blank\" rel=\"noopener\">integrating a digital MES with equipment<\/a> explains the connection step, and the <a href=\"https:\/\/mestric.com\/sl\/role-iot-manufacturing-boosting-efficiency-2026\/\" target=\"_blank\" rel=\"noopener\">role of IoT in manufacturing<\/a> shows where connected devices add value and where they add exposure.<\/p>\n<h2 id=\"slovenian-and-eu-rules-to-check\" tabindex=\"-1\">Slovenian and EU rules to check<\/h2>\n<p>Which rules apply depends on your company and your products. Here is the landscape as it stands.<\/p>\n<h3 id=\"zinfv-1-and-nis-2\" tabindex=\"-1\">ZInfV-1 and NIS 2<\/h3>\n<p>Slovenia\u2019s new Information Security Act, ZInfV-1, <a href=\"https:\/\/www.gov.si\/novice\/2025-05-23-drzavni-zbor-republike-slovenije-sprejel-nov-zakon-o-informacijski-varnosti-zinfv-1\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">transposes NIS 2 and requires in-scope entities to implement risk-management measures and report significant incidents<\/a>. The national authority is URSIV, which <a href=\"https:\/\/www.gov.si\/teme\/obveznosti-in-podpora-zavezancem-po-zakonu-o-informacijski-varnosti-zinfv-1\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">provides guidance and support, while its inspectorate supervises the act<\/a>. The same page notes that the act makes management responsible for supporting cybersecurity, integrating it into business planning and putting security documentation and risk measures in place. The full text is in the <a href=\"https:\/\/pisrs.si\/pregledPredpisa?id=ZAKO8934\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">state legal register<\/a>. Whether your plant is in scope is a question for your legal or compliance adviser and for URSIV\u2019s guidance for obliged entities.<\/p>\n<p>For in-scope manufacturers, one practitioner roadmap summarises NIS 2 as <a href=\"https:\/\/www.nis-2-templates.com\/manufacturing-compliance\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">ten Article 21 risk-management measures, with IEC 62443-2-1 offering a method for OT security programmes<\/a>. The same source observes that NIS 2 does not address factory-floor specifics such as legacy PLCs and production continuity, so translating it to the plant is real compliance work. Treat that as a reason to involve your automation engineers early.<\/p>\n<h3 id=\"incident-reporting\" tabindex=\"-1\">Incident reporting<\/h3>\n<p>For in-scope entities, <a href=\"https:\/\/services.google.com\/fh\/files\/misc\/ot_security_blueprint_ociso2025.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">significant incidents must be reported to the national CSIRT within 24 hours of initial assessment, followed by a formal report within 72 hours<\/a>. The national CSIRT is SI-CERT, which <a href=\"https:\/\/www.cert.si\/o-nas\/rfc2350\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">handles incidents for in-scope entities as well as voluntary reports<\/a>; government networks report to SIGOV-CERT. Agree internally who makes that call at 3 a.m., and write their phone number into the plan.<\/p>\n<h3 id=\"machinery-regulation-and-cyber-resilience-act\" tabindex=\"-1\">Machinery Regulation and Cyber Resilience Act<\/h3>\n<p>If you build machines or digital products, further rules apply. The Machinery Regulation (EU 2023\/1230) <a href=\"https:\/\/www.helmholz.de\/media\/pdf\/72\/04\/86\/Helmholz_Whitepaper_IndustrialSecurity_EN.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">makes appropriate cybersecurity measures mandatory for those placing machines on the market<\/a>. The same whitepaper states that under the Cyber Resilience Act, manufacturers of digital products such as PLCs and industrial switches must confirm cybersecurity in their CE declaration, with compliance mandatory for products sold from December 2027.<\/p>\n<h2 id=\"assess-mes-security-before-you-buy\" tabindex=\"-1\">Assess MES security before you buy<\/h2>\n<p>The cheapest time to fix a security gap is before go-live. Google\u2019s OT guidance for manufacturers advises to <a href=\"https:\/\/services.google.com\/fh\/files\/misc\/ot_security_blueprint_ociso2025.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">include security requirements in design and in site or factory acceptance tests, map assets and communications, assess risks, govern approved vendors and secure remote access with MFA<\/a>. Turn that into questions for any MES supplier:<\/p>\n<ol>\n<li><strong>Access control:<\/strong> does the system support multi-factor authentication, role-based permissions and a full audit log of changes to recipes and norms?<\/li>\n<li><strong>Architecture:<\/strong> how does it connect to machines, and does it work with a segmented network and a DMZ?<\/li>\n<li><strong>Remote access:<\/strong> how does the supplier reach your system for support, who approves it, and is every session logged?<\/li>\n<li><strong>Updates:<\/strong> how are vulnerabilities announced, and can updates be scheduled around your maintenance windows?<\/li>\n<li><strong>Backup and recovery:<\/strong> what is backed up, how often, and how long does a restore take?<\/li>\n<li><strong>Data:<\/strong> where is data stored, who can see it, and what happens to it when the contract ends?<\/li>\n<li><strong>Acceptance:<\/strong> will security checks be part of the factory and site acceptance tests?<\/li>\n<\/ol>\n<p>Ask for answers in writing and keep them with your project documentation. They also help the compliance work described above.<\/p>\n<h2 id=\"monitor-respond-recover\" tabindex=\"-1\">Monitor, respond, recover<\/h2>\n<p>Security does not end at go-live. Three habits make the biggest difference.<\/p>\n<ul>\n<li><strong>Watch the system.<\/strong> Review user accounts and the audit log regularly, and look for new devices on the OT network.<\/li>\n<li><strong>Rehearse.<\/strong> An incident response plan should be tested through table-top exercises, and the guidance recommends <a href=\"https:\/\/services.google.com\/fh\/files\/misc\/ot_security_blueprint_ociso2025.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">keeping documentation independent of the affected network and using out-of-band tools for recovery<\/a>. Print the contact list and network diagrams or keep them offline.<\/li>\n<li><strong>Know your manual fallback.<\/strong> Decide in advance how you will run orders, record quality and trace batches on paper if the MES is unavailable, and who authorises restarting once it is back.<\/li>\n<\/ul>\n<h2 id=\"our-perspective\" tabindex=\"-1\">Our perspective<\/h2>\n<blockquote>\n<p>Security is easier to build into an MES than to add afterwards. That is why we think the first question to ask is not \u201cwhich features does it have?\u201d but \u201chow does it connect, and who can change what?\u201d<\/p>\n<p>Mestric\u2122 is designed to connect directly with manufacturing equipment and collect data automatically. That reduces manual errors, and it gives you one place where production data, KPIs, downtime and quality parameters are visible. For security, a single, consistent view is an advantage: it is easier to define who sees and changes what in one system than across spreadsheets, paper records and unmanaged exports.<\/p>\n<p>We would encourage every plant to treat the MES rollout as the moment to map machines, data flows and responsibilities. You need that map for good optimisation anyway, and it is the same map you need for network segmentation, access control and incident response. Real-time visibility also helps you spot abnormal behaviour, such as unexpected downtime or quality drift, sooner.<\/p>\n<p>Our advice is to see the system working in a real production environment, bring your automation engineer and your IT lead to the same demonstration, and put your security questions on the table from the first meeting.<\/p>\n<p><em>Andra\u017e<\/em><\/p>\n<\/blockquote>\n<h2 id=\"see-mestric-mes-in-a-real-production-setting\" tabindex=\"-1\">See Mestric\u2122 MES in a real production setting<\/h2>\n<p>If you are comparing MES platforms, we can show you how Mestric\u2122 connects to machines and presents live KPIs, downtime, quality parameters and cost analysis, in a demonstration at our demo centre. Bring your security questions from the checklist above. You can read more on the <a href=\"https:\/\/mestric.com\/sl\/o-resitvi\/\" target=\"_blank\" rel=\"noopener\">Mestric\u2122 MES solution page<\/a> or start from <a href=\"https:\/\/mestric.com\/sl\/\" target=\"_blank\" rel=\"noopener\">mestric.com<\/a>.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/mestric.com\/wp-content\/uploads\/2026\/09\/1771068359718_mestric.jpg\" alt=\"Mestric\"><\/p>\n<p>For background on how an MES differs from older ways of working, read <a href=\"https:\/\/mestric.com\/sl\/mes-vs-traditional-manufacturing-boost-efficiency-2026\/\" target=\"_blank\" rel=\"noopener\">MES vs traditional manufacturing<\/a>.<\/p>\n<h2 id=\"faq\" tabindex=\"-1\">Pogosto zastavljena vpra\u0161anja<\/h2>\n<h3 id=\"is-mes-security-the-same-as-machine-safety\" tabindex=\"-1\">Is MES security the same as machine safety?<\/h3>\n<p>No. Machine safety protects people from hazards such as moving parts, while MES security protects systems and data from unauthorised access or tampering. They overlap because, as NIST notes, OT incidents can endanger people, the environment and equipment. Treat them as two linked programmes with shared owners.<\/p>\n<h3 id=\"does-zinfv-1-apply-to-my-factory\" tabindex=\"-1\">Does ZInfV-1 apply to my factory?<\/h3>\n<p>It depends on whether your company is an in-scope entity under the act, which transposes NIS 2 in Slovenia. URSIV publishes guidance for obliged entities, and your legal or compliance adviser can confirm your status. If you are in scope, you must apply risk-management measures and report significant incidents.<\/p>\n<h3 id=\"what-is-the-first-control-to-put-in-place\" tabindex=\"-1\">What is the first control to put in place?<\/h3>\n<p>Start with what you can see and control: an inventory of machines and connections, then multi-factor authentication and least-privilege accounts on the MES. Network segmentation between IT and OT follows, ideally with a DMZ. NIST lists these among its core recommendations.<\/p>\n<h3 id=\"how-quickly-must-a-significant-incident-be-reported\" tabindex=\"-1\">How quickly must a significant incident be reported?<\/h3>\n<p>For in-scope entities in Slovenia, the national CSIRT (SI-CERT, or SIGOV-CERT for government networks) must be told within 24 hours of initial assessment, followed by a formal report within 72 hours. Check URSIV\u2019s guidance for the current procedure and forms.<\/p>\n<h2 id=\"sources\" tabindex=\"-1\">Sources<\/h2>\n<ul>\n<li><a href=\"https:\/\/nvlpubs.nist.gov\/nistpubs\/specialpublications\/NIST.SP.800-82r3.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Guide to Operational Technology (OT) Security, NIST SP 800-82r3<\/a><\/li>\n<li><a href=\"https:\/\/www.helmholz.de\/media\/pdf\/72\/04\/86\/Helmholz_Whitepaper_IndustrialSecurity_EN.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Industrial Security whitepaper, Helmholz<\/a><\/li>\n<li><a href=\"https:\/\/documents.trendmicro.com\/assets\/white_papers\/wp-attacks-on-smart-manufacturing-systems.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Attacks on Smart Manufacturing Systems: A Forward-looking Security Analysis<\/a><\/li>\n<li><a href=\"https:\/\/innetworktech.com\/wp-content\/uploads\/2024\/08\/Dragos_WP_ManufacturingThreatScenarios_0923.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Cyber Threat Scenarios and Protection Steps for Manufacturing, Dragos<\/a><\/li>\n<li><a href=\"https:\/\/www.cert.si\/en\/cve-2026-25600\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">CVE-2026-25600, SI-CERT<\/a><\/li>\n<li><a href=\"https:\/\/www.gov.si\/novice\/2025-05-23-drzavni-zbor-republike-slovenije-sprejel-nov-zakon-o-informacijski-varnosti-zinfv-1\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Dr\u017eavni zbor sprejel nov Zakon o informacijski varnosti (ZInfV-1), gov.si<\/a><\/li>\n<li><a href=\"https:\/\/www.gov.si\/teme\/obveznosti-in-podpora-zavezancem-po-zakonu-o-informacijski-varnosti-zinfv-1\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Obveznosti in podpora zavezancem po ZInfV-1, gov.si<\/a><\/li>\n<li><a href=\"https:\/\/pisrs.si\/pregledPredpisa?id=ZAKO8934\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Zakon o informacijski varnosti (ZInfV-1), PISRS<\/a><\/li>\n<li><a href=\"https:\/\/www.nis-2-templates.com\/manufacturing-compliance\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">NIS2 Manufacturing Compliance: The 10-Measure Roadmap<\/a><\/li>\n<li><a href=\"https:\/\/services.google.com\/fh\/files\/misc\/ot_security_blueprint_ociso2025.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Manufacturing OT Security Guidance, Google Cloud OCISO<\/a><\/li>\n<li><a href=\"https:\/\/www.cert.si\/o-nas\/rfc2350\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">RFC2350, SI-CERT<\/a><\/li>\n<\/ul>\n<h2 id=\"recommended\" tabindex=\"-1\">Priporo\u010deno<\/h2>\n<ul>\n<li><a href=\"https:\/\/mestric.com\/sl\/types-of-industrial-data-security-risks\/\" target=\"_blank\" rel=\"noopener\">Types of industrial data security risks every plant must track<\/a><\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"<p>What MES security covers, which risks reach the shop floor, the controls to apply and the Slovenian and EU rules (ZInfV-1, NIS 2) that may apply to you.<\/p>","protected":false},"author":1,"featured_media":1757,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1756","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-learn"],"acf":[],"_links":{"self":[{"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/posts\/1756","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/comments?post=1756"}],"version-history":[{"count":1,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/posts\/1756\/revisions"}],"predecessor-version":[{"id":1760,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/posts\/1756\/revisions\/1760"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/media\/1757"}],"wp:attachment":[{"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/media?parent=1756"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/categories?post=1756"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mestric.com\/sl\/wp-json\/wp\/v2\/tags?post=1756"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}