<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Centro de Ciberseguridad Industrial</title>
	<atom:link href="https://www.cci-es.org/en/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.cci-es.org</link>
	<description>El ecosistema global para compartir experiencias y conocimiento</description>
	<lastBuildDate>Wed, 11 Mar 2026 12:07:18 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.cci-es.org/wp-content/uploads/cci_logo-ico-neg-150x150.png</url>
	<title>Centro de Ciberseguridad Industrial</title>
	<link>https://www.cci-es.org</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Operations Role: Know where you are weak before the incident occurs</title>
		<link>https://www.cci-es.org/en/operations-role-know-where-you-are-weak-before-the-incident-occurs/</link>
		
		<dc:creator><![CDATA[Isabel Bellon]]></dc:creator>
		<pubDate>Wed, 11 Mar 2026 12:07:18 +0000</pubDate>
				<category><![CDATA[English]]></category>
		<guid isPermaLink="false">https://www.cci-es.org/?p=25423</guid>

					<description><![CDATA[How many times have we heard on the plant floor “that’s an IT thing” or “as long as the plant is running and production doesn’t stop, everything is fine.” We embrace the dangerous assumption that we are safe. The problem does not begin on the day of the attack but before, when we do not [&#8230;]]]></description>
										<content:encoded><![CDATA[<p data-path-to-node="1"><span class=""><img fetchpriority="high" decoding="async" class="aligncenter wp-image-25422 size-large" src="https://www.cci-es.org/wp-content/uploads/Post-Blog-Jose-3-1024x512.jpg" alt="Industrial cybersecurity and operational resilience in OT plants with network segmentation and critical assets" width="1024" height="512" srcset="https://www.cci-es.org/wp-content/uploads/Post-Blog-Jose-3-1024x512.jpg 1024w, https://www.cci-es.org/wp-content/uploads/Post-Blog-Jose-3-300x150.jpg 300w, https://www.cci-es.org/wp-content/uploads/Post-Blog-Jose-3-768x384.jpg 768w, https://www.cci-es.org/wp-content/uploads/Post-Blog-Jose-3-1536x768.jpg 1536w, https://www.cci-es.org/wp-content/uploads/Post-Blog-Jose-3-1920x960.jpg 1920w" sizes="(max-width: 1024px) 100vw, 1024px" /></span></p>
<p data-path-to-node="1"><span class="">How many times have we heard on the plant floor </span><b class="" data-path-to-node="1" data-index-in-node="48">“that’s an IT thing”</b><span class=""> or </span><b class="" data-path-to-node="1" data-index-in-node="72">“as long as the plant is running and production doesn’t stop, everything is fine.”</b><span class=""> We embrace the dangerous assumption that we are safe.</span></p>
<p data-path-to-node="2"><span class="">The problem does not begin on the day of the attack but before,</span><span class=""> when we do not truly know </span><b class="" data-path-to-node="2" data-index-in-node="90">where we are vulnerable.</b></p>
<h2><strong>In a real industrial incident, it is not just about how many specific industrial cybersecurity tools you have deployed on the plant floor.</strong></h2>
<div class="container">
<div id="model-response-message-contentr_c8f019556ae1ba68" class="markdown markdown-main-panel enable-updated-hr-color" dir="ltr" aria-live="polite" aria-busy="false">
<p data-path-to-node="0">Or whether you have <b data-path-to-node="0" data-index-in-node="20">IDS, IPS, OT EDR agents, or firewalls</b> deployed segmenting the industrial network; it is also about knowing which of your <b data-path-to-node="0" data-index-in-node="141">critical plant processes</b> are which, and which one will stop first if something fails.</p>
<p data-path-to-node="0">Do you have this <b data-path-to-node="0" data-index-in-node="244">command of your industrial plant</b>?</p>
<ul>
<li><strong>Visibility</strong>: You know all your industrial assets, you have identified your organization&#8217;s critical assets and the actual dependencies between them.</li>
<li><strong>Priorities:</strong> Which of your lines or systems cannot stop for even 5 minutes.</li>
<li><strong>Coordination:</strong> You know who to turn to if you detect an incident.</li>
<li><strong>Decision:</strong> You are prepared to isolate a system, even if it means temporary loss of production.</li>
</ul>
<h3><strong>In OT, we cannot focus solely on regulatory compliance.</strong></h3>
<p><span class="">We need to be clear about what our </span><b class="" data-path-to-node="0" data-index-in-node="35">weak points</b><span class=""> are,</span><span class=""> which systems are connected to more things than we think,</span><span class=""> which </span><b class="" data-path-to-node="0" data-index-in-node="116">external provider</b><span class=""> could become an </span><b class="" data-path-to-node="0" data-index-in-node="150">entry vector</b><span class="">,</span><span class=""> and what we can do to improve our </span><b class="" data-path-to-node="0" data-index-in-node="198">cybersecurity posture</b><span class="">.</span></p>
<p><span class="">Because once a real incident occurs,</span><span class=""> there is no longer time to map dependencies or debate priorities or responsibilities; we will only have room to </span><b class="" data-path-to-node="0" data-index-in-node="370">make decisions</b><span class="">.</span><span class=""> However,</span><span class=""> I know that many organizations choose to operate this way every day.</span></p>
<div class="container">
<div id="model-response-message-contentr_e7ce388895b7b907" class="markdown markdown-main-panel enable-updated-hr-color" dir="ltr" aria-live="polite" aria-busy="false">
<h3 data-path-to-node="0"></h3>
<h3 data-path-to-node="0"><strong>Operational resilience, which has been talked about so much lately, does not start with the incident response but much earlier.</strong></h3>
<p>How we manage to <b data-path-to-node="0" data-index-in-node="17">identify the weaknesses</b> and know where we are most fragile before someone else discovers it for us.</p>
<p>With <b data-path-to-node="0" data-index-in-node="122">MACIN</b>, we can obtain a vision of our <b data-path-to-node="0" data-index-in-node="159">operational resilience</b>, which practices are solid, where we have organizational or technical vulnerabilities, and what we should reinforce first based on our results to prevent an incident from ultimately impacting us.</p>
<p><strong><span class="">I think we can sum it up quite nicely:</span><span class=""> if you don’t know where you are weak or what those weaknesses are,</span><span class=""> you are not prepared,</span><span class=""> and in OT,</span> improvisation<span class=""> causes us to acquire a </span>technical debt<span class=""> that sooner or later ends up being paid off with </span>production<span class="">.</span></strong></p>
</div>
</div>
</div>
<h3></h3>
<div id="model-response-message-contentr_c8f019556ae1ba68" class="markdown markdown-main-panel enable-updated-hr-color" dir="ltr" aria-live="polite" aria-busy="false">
<div class="container">
<div id="model-response-message-contentr_e7ce388895b7b907" class="markdown markdown-main-panel enable-updated-hr-color" dir="ltr" aria-live="polite" aria-busy="false">
<h3 style="text-align: center;"><a href="https://www.linkedin.com/in/juli-lizcano/" rel="nofollow noopener" target="_blank"><span style="font-weight: 400;">Juli Lizcano</span></a></h3>
<h3 style="text-align: center;" data-prosemirror-content-type="node" data-prosemirror-node-name="paragraph" data-prosemirror-node-block="true" data-pm-slice="1 1 []">OT/ICS/IoT Cybersecurity Senior Consultant</h3>
<h3 style="text-align: center;"><strong> – –</strong></h3>
<h3 style="text-align: center;"><em>More information about MACIN Platform <a href="https://www.cci-es.org/landing-macin/">here</a></em></h3>
</div>
</div>
</div>
</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>The New Role of the Auditor: Beyond Compliance in Industrial Cybersecurity</title>
		<link>https://www.cci-es.org/en/the-new-role-of-the-auditor-beyond-compliance-in-industrial-cybersecurity/</link>
		
		<dc:creator><![CDATA[Isabel Bellon]]></dc:creator>
		<pubDate>Wed, 04 Mar 2026 08:23:21 +0000</pubDate>
				<category><![CDATA[English]]></category>
		<guid isPermaLink="false">https://www.cci-es.org/?p=25366</guid>

					<description><![CDATA[Historically, traditional auditing has been limited to certifying an organization&#8217;s compliance with certain standards or regulations, a mere formality that can be summed up in the phrase: &#8220;We need to get them to certify that we comply.&#8221; However, modern industrial cybersecurity auditing has evolved to go far beyond simple certification. The strategic approach of the [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><img decoding="async" class="wp-image-25363 size-large" src="https://www.cci-es.org/wp-content/uploads/Post-Blog-Erik-2-1024x512.jpg" alt="" width="1024" height="512" srcset="https://www.cci-es.org/wp-content/uploads/Post-Blog-Erik-2-1024x512.jpg 1024w, https://www.cci-es.org/wp-content/uploads/Post-Blog-Erik-2-300x150.jpg 300w, https://www.cci-es.org/wp-content/uploads/Post-Blog-Erik-2-768x384.jpg 768w, https://www.cci-es.org/wp-content/uploads/Post-Blog-Erik-2-1536x768.jpg 1536w, https://www.cci-es.org/wp-content/uploads/Post-Blog-Erik-2-1920x960.jpg 1920w" sizes="(max-width: 1024px) 100vw, 1024px" /></p>
<p>Historically,<strong> traditional auditing</strong> has been limited to certifying an organization&#8217;s compliance with certain standards or regulations, a mere formality that can be summed up in the phrase: &#8220;We need to get them to certify that we comply.&#8221; However, <strong>modern industrial cybersecurity auditing</strong> has evolved to go far beyond simple certification.</p>
<h2><strong>The strategic approach of the current Audit</strong></h2>
<p>Today, <strong>auditors</strong> not only review standards, but also analyze a conceptual flow focused on <strong>process sustainability</strong>, with the following phases:</p>
<ol>
<li style="font-weight: 400;" aria-level="1"><strong>Review and justify</strong> the organization&#8217;s Risk Map.</li>
<li style="font-weight: 400;" aria-level="1"><strong>Analyze the mitigating controls</strong> assigned to that Map, based on standards such as ISO 62443, NIST, or SGCI.</li>
<li style="font-weight: 400;" aria-level="1"><strong>Evaluate the implementation</strong> and actual and effective functioning of these controls.</li>
<li style="font-weight: 400;" aria-level="1"><strong>Issue an Audit Report</strong> that identifies the<strong> root causes</strong> of the weaknesses and deficiencies observed, so as not to focus solely on the symptoms.</li>
</ol>
<p>Ultimately, this process translates into a <strong>maturity assessment</strong>. The ultimate goal is to reach the <strong>&#8220;Optimized&#8221;</strong> level, the only one that guarantees the organization&#8217;s true <strong>long-term sustainability</strong>.</p>
<h3><strong>To carry out this maturity assessment, both during audits and as a preventive measure, we rely on powerful tools such as MACIN. </strong></h3>
<p>This application, offered and developed by the <strong>CCI</strong>, reviews the organizational structure, the scheme of roles, responsibilities, and capacities for action, analyzing in detail:</p>
<ul>
<li style="font-weight: 400;" aria-level="1"><strong>10 domains and 45 logical cybersecurity</strong> objectives.</li>
<li style="font-weight: 400;" aria-level="1"><strong>175 practices</strong> evaluated across four key dimensions: Processes, Technology, People, and Results.</li>
<li style="font-weight: 400;" aria-level="1"><strong>5 maturity levels</strong>: Initial (1), Repeatable (2), Defined (3), Managed (4), and Optimized (5).</li>
</ul>
<p><img decoding="async" class="aligncenter wp-image-25364 size-medium" src="https://www.cci-es.org/wp-content/uploads/logo-macin-512-2-300x255.png" alt="" width="300" height="255" srcset="https://www.cci-es.org/wp-content/uploads/logo-macin-512-2-300x255.png 300w, https://www.cci-es.org/wp-content/uploads/logo-macin-512-2.png 512w" sizes="(max-width: 300px) 100vw, 300px" /></p>
<h2></h2>
<h2><strong>Value for Senior Management</strong></h2>
<p>The use of the <strong>MACIN</strong> tool provides a provisional <strong>Maturity Level</strong>, which the auditor is responsible for confirming with evidence.</p>
<p>It is a <strong>very valuable tool</strong>, both for the manager of an <strong>industrial facility</strong> and for the <strong>industrial control systems auditor.</strong> It allows both to obtain a strategic <strong>vision based on verifiable data.</strong></p>
<p>With the help of <strong>MACIN</strong>, the <strong>Audit Report</strong> has two well-documented parts: on the one hand, it details the Significant Events (findings and operational weaknesses) and, on the other, it indicates the <strong>Level of Maturity to Senior Management</strong> in a justified manner, providing a clear strategic vision of the barriers that must be overcome to achieve <strong>resilient and sustainable industrial cybersecurity.</strong></p>
<h3 style="text-align: center;" data-prosemirror-content-type="node" data-prosemirror-node-name="paragraph" data-prosemirror-node-block="true" data-pm-slice="1 1 []"><b><a href="https://www.linkedin.com/in/erik-de-pablo-martinez-a4916220/" rel="nofollow noopener" target="_blank">Erik De Pablo</a></b></h3>
<h3 style="text-align: center;">Cybersecurity Audit Expert</h3>
<h3 style="text-align: center;"><strong> – –</strong></h3>
<h3 style="text-align: center;"><em>More information about MACIN Platform <a href="https://www.cci-es.org/landing-macin/">here</a></em></h3>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>ICSO role: Data, not opinions</title>
		<link>https://www.cci-es.org/en/icso-role-data-not-opinions/</link>
		
		<dc:creator><![CDATA[Maite Carli]]></dc:creator>
		<pubDate>Thu, 19 Feb 2026 18:22:10 +0000</pubDate>
				<category><![CDATA[English]]></category>
		<guid isPermaLink="false">https://www.cci-es.org/?p=25292</guid>

					<description><![CDATA[&#160; For years in industrial cybersecurity, I’ve heard phrases like “I think we’re fine,” “the audit went well,” or “we have many controls in place.” And yet, when a real incident happens, those phrases disappear. Because at that moment, opinions no longer matter. Only data does. Complying with standards does not mean being prepared for [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><img loading="lazy" decoding="async" class="aligncenter wp-image-25287 size-large" src="https://www.cci-es.org/wp-content/uploads/Post-Blog-Jose-2-1024x512.jpg" alt="Ciberseguridad Industrial ICSO" width="1024" height="512" srcset="https://www.cci-es.org/wp-content/uploads/Post-Blog-Jose-2-1024x512.jpg 1024w, https://www.cci-es.org/wp-content/uploads/Post-Blog-Jose-2-300x150.jpg 300w, https://www.cci-es.org/wp-content/uploads/Post-Blog-Jose-2-768x384.jpg 768w, https://www.cci-es.org/wp-content/uploads/Post-Blog-Jose-2-1536x768.jpg 1536w, https://www.cci-es.org/wp-content/uploads/Post-Blog-Jose-2-1920x960.jpg 1920w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></p>
<p><!--StartFragment --></p>
<p>&nbsp;</p>
<p>For years in industrial cybersecurity, I’ve heard phrases like “I think we’re fine,” “the audit went well,” or “we have many controls in place.” And yet, when a real incident happens, those phrases disappear. Because at that moment, opinions no longer matter. <strong>Only data does</strong>.</p>
<h2>Complying with standards does not mean being prepared for a cyber incident.</h2>
<p>I recently wrote about something uncomfortable but necessary: complying with standards does not mean <strong>being prepared for a cyber incident</strong>. Compliance brings order, helps, and is necessary, but <strong>preparedness is something else</strong>. Being prepared means proving that when something fails, the organization keeps operating.</p>
<h3>An audit is a snapshot, while maturity is a movie.</h3>
<p>We’ve also talked about <strong>organizational maturity</strong>. And here’s another uncomfortable truth: an audit is a snapshot, while maturity is a movie. An audit can tell you how you were on that specific day. Maturity tells you how you evolve, how you react, and how you survive when the context changes.</p>
<h2>Having a procedure does not mean knowing how to execute it under pressure.</h2>
<p>And then there’s the checklist. We all need checklists, they’re useful and necessary but having something on a checklist does not mean <strong>having real capability</strong>. Having a procedure does not mean knowing how to execute it under pressure, and having technology does not mean knowing how to <strong>use it during a real incident.</strong></p>
<h3>The ICSO should not bring opinions to the board; it should bring evidence.</h3>
<p>This is where the <strong>ICSO role</strong> changes. It’s no longer just someone who explains cybersecurity; it’s someone who makes <strong>security measurable.</strong> The ICSO should not bring opinions to the board, but evidence, <strong>trends, and preparedness</strong> metrics in short, data that enables decision-making.</p>
<p>Because the right conversation is not “do we have this implemented?” The right conversation is “what would happen if this scenario occurred tomorrow?” And the next, even more important question: “do we have <strong>real capability to respond</strong>?”</p>
<h2>Maturity models and platforms like MACIN start to make sense.</h2>
<p>This is where maturity models and platforms like <strong>MACIN</strong> start to make sense. Not to assign labels or create rankings, but to truly understand where we stand, what gaps exist, and what impact they have on the <strong>business’s real resilience</strong>.</p>
<p>The future of industrial cybersecurity is not about having more or better controls. It needs more clarity, more evidence, and better demonstrable capability. It’s about being able to look the Board in the eye and speak in terms of <strong>real preparedness, not theoretical implementation</strong>.</p>
<p>Because in the end, in industry, <strong>cybersecurity is not an opinion, it’s a capability</strong>. And capabilities, just like physical safety or operational continuity, are demonstrated with data.</p>
<h3 style="text-align: center;" data-prosemirror-content-type="node" data-prosemirror-node-name="paragraph" data-prosemirror-node-block="true" data-pm-slice="1 1 []"><a href="https://www.linkedin.com/in/jvaliente/" rel="nofollow noopener" target="_blank"><b>José Valiente</b></a></h3>
<h3 style="text-align: center;" data-prosemirror-content-type="node" data-prosemirror-node-name="paragraph" data-prosemirror-node-block="true" data-pm-slice="1 1 [&quot;bulletList&quot;,{&quot;localId&quot;:null},&quot;listItem&quot;,{&quot;localId&quot;:null}]"> CCI General Director</h3>
<h3 style="text-align: center;"><strong> – –</strong></h3>
<h3 style="text-align: center;"><em>More information about MACIN Platform <a href="https://www.cci-es.org/landing-macin/">here </a></em></h3>
<p><!--EndFragment --></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Maturity is not demonstrated in an audit</title>
		<link>https://www.cci-es.org/en/maturity-is-not-demonstrated-in-an-audit/</link>
		
		<dc:creator><![CDATA[Maite Carli]]></dc:creator>
		<pubDate>Mon, 16 Feb 2026 19:23:08 +0000</pubDate>
				<category><![CDATA[English]]></category>
		<guid isPermaLink="false">https://www.cci-es.org/?p=25268</guid>

					<description><![CDATA[There is often a dangerous confusion between two vital concepts in business management: believing that regulatory compliance is the same as organizational maturity. Nothing could be further from the truth. We tend to think that passing an audit (compliance), as if it were the ultimate proof that we have ‘arrived’ at excellence, means we are [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><!--StartFragment --></p>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-25269 size-large" src="https://www.cci-es.org/wp-content/uploads/Conduciendo-hacia-el-futuro-al-atardecer-1024x683.png" alt="" width="1024" height="683" srcset="https://www.cci-es.org/wp-content/uploads/Conduciendo-hacia-el-futuro-al-atardecer-1024x683.png 1024w, https://www.cci-es.org/wp-content/uploads/Conduciendo-hacia-el-futuro-al-atardecer-300x200.png 300w, https://www.cci-es.org/wp-content/uploads/Conduciendo-hacia-el-futuro-al-atardecer-768x512.png 768w, https://www.cci-es.org/wp-content/uploads/Conduciendo-hacia-el-futuro-al-atardecer.png 1536w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></p>
<p>There is often a dangerous confusion between two vital concepts in business management: believing that <em>regulatory compliance</em> is the same as <em>organizational maturity</em>. Nothing could be further from the truth. We tend to think that passing an audit (compliance), as if it were the ultimate proof that we have ‘arrived’ at excellence, means we are ready to compete or face a crisis (maturity). It’s a common mistake in many organizations.</p>
<blockquote>
<p style="text-align: left;"><!--StartFragment --></p>
<p><strong>&#8220;Passing an inspection is not the same as having the ability to evolve.&#8221;</strong></p>
<p>We can have an immature company (chaotic, reactive, dependent on individual heroes) that, with a lot of effort and stress, manages to “tidy up the house” just in time to pass an audit. But… the very next day, the chaos returns.</p>
<p>If we look at Business Management as a journey along a highway (a visual analogy illustrated by the image accompanying this post), the difference becomes crystal clear<!--EndFragment --></p></blockquote>
<h2><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f6a8.png" alt="🚨" class="wp-smiley" style="height: 1em; max-height: 1em;" /> <strong>Compliance can be audited, but maturity is challenged.</strong></h2>
<p>An audit is like a medical <strong>check-up</strong> or a vehicle technical inspection (VTV in Argentina, ITV in Spain): it’s binary (black or white). It reviews <strong>the past and the present</strong> to confirm that there are no serious errors and that we comply with current regulations.</p>
<h2 style="text-align: left;"><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f697.png" alt="🚗" class="wp-smiley" style="height: 1em; max-height: 1em;" /> <strong>The audit is the traffic checkpoint</strong></h2>
<p style="text-align: left;">It acts as both the traffic checkpoint and the vehicle’s dashboard. It’s the control post that verifies we meet the rules required to circulate. And, crucially, it’s also the internal dashboard that checks the ‘health of the engine’ and provides a static snapshot of the present: Are we following the rules today? Do we have the minimum resources to operate right now without crashing? It verifies <strong>COMPLIANCE</strong> and the current state.</p>
<h2 style="text-align: left;"><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f31f.png" alt="🌟" class="wp-smiley" style="height: 1em; max-height: 1em;" /> <strong>The Maturity Assessment is the GPS.</strong></h2>
<p><!--StartFragment --></p>
<p>It doesn’t look for someone to blame, it looks for <strong>evolution</strong>. It’s like a skill test for an athlete: it measures how expert, trained, sophisticated, and efficient you are. It’s not about a ‘Yes/No,’ it’s not binary, it’s about climbing levels, improving, and surpassing yourself day by day.</p>
<p>It’s what confirms that, beyond the speed at which we’re traveling (set by the organization), we are on the <strong>RIGHT PATH</strong>. Maturity isn’t about ‘not getting fines’;<strong> it’s about clearly knowing where we’re going</strong> and having the ability to adapt if the road suddenly changes. We don’t aim merely to pass the checkpoint we aim to enjoy the journey,<strong> improve and optimize the process</strong>, and of course, reach the destination.</p>
<p><!--EndFragment --></p>
<h2 style="text-align: left;"><strong>Why is this difference crititcal?</strong></h2>
<p><!--StartFragment --></p>
<p>Because compliance brings order, but it’s in Incident Management where the truth comes to light. Many organizations suffer from <strong>‘analysis paralysis.</strong>’ They have perfect manuals for the auditor, but when a real incident occurs, no one knows what to do. That’s where maturity proves its value: <strong>it’s the ability to decide and act under pressure</strong>. Even for an auditor, a maturity assessment is a key tool, because it reveals gaps and improvement opportunities that simple compliance often hides.</p>
<p>By assessing maturity across its four dimensions <strong>(People, Processes, Technology, and Results)</strong>, we draw a roadmap toward the future.</p>
<p><strong>Don’t settle for merely ‘passing the checkpoint.’ Build the capability to enjoy the journey.</strong></p>
<p>We need both: Auditing and Maturity Assessment. <strong>We just shouldn’t confuse a ‘medical check-up’ with having the physical condition to run a marathon.</strong></p>
<p>Do you feel that sometimes too much energy is invested in the ‘audit snapshot’ and too little in the<em> ‘maturity movie’</em>? In your organization, is the focus more on passing the checkpoint or on adjusting the GPS?</p>
<p><!--EndFragment --></p>
<h2 class="UhTMnxhsoIuFualmaZbIxTNlsZCBwehXsE inline t-24 v-align-middle break-words" style="text-align: center;"><a href="https://www.linkedin.com/in/gfgg27/overlay/about-this-profile/?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base%3BIPJGcNfoQvKqpz75ESAfRA%3D%3D" target="_blank" rel="noopener nofollow">Gerardo Fabián González</a></h2>
<h2 class="UhTMnxhsoIuFualmaZbIxTNlsZCBwehXsE inline t-24 v-align-middle break-words" style="text-align: center;">Professor at the CCI &#8211; Industrial Cybersecurity Professional School</h2>
<p style="text-align: center;"><strong> &#8211; &#8211;</strong></p>
<h3 style="text-align: center;"><span style="color: #808080;"><em>More information about the Platform <span style="color: #800000;">MACIN</span><span style="color: #0000ff;"> <a style="color: #0000ff;" href="https://www.cci-es.org/landing-macin/">here</a></span></em></span></h3>
<p><!--EndFragment --></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>From checklist to real capability</title>
		<link>https://www.cci-es.org/en/industrial-cybersecurity-checklist-real-capability/</link>
		
		<dc:creator><![CDATA[Isabel Bellon]]></dc:creator>
		<pubDate>Thu, 29 Jan 2026 11:28:54 +0000</pubDate>
				<category><![CDATA[English]]></category>
		<guid isPermaLink="false">https://www.cci-es.org/?p=25214</guid>

					<description><![CDATA[How MACIN turns industrial cybersecurity into a strategic asset (with two practical cases) In industrial cybersecurity (OT/ICS), there is a very common trap: confusing “having controls” with “having capability”. Many organizations might “pass” a checklist because a procedure, a SOC, a ticketing tool, or a patching policy exists. But when a real incident arrives—with pressure [&#8230;]]]></description>
										<content:encoded><![CDATA[<h2><img loading="lazy" decoding="async" class="aligncenter wp-image-25212 size-large" src="https://www.cci-es.org/wp-content/uploads/Estrategia-de-Ciberseguridad-Industrial-1024x512.jpg" alt="Operator supervising HMI systems on the plant floor. Real Capability" width="1024" height="512" srcset="https://www.cci-es.org/wp-content/uploads/Estrategia-de-Ciberseguridad-Industrial-1024x512.jpg 1024w, https://www.cci-es.org/wp-content/uploads/Estrategia-de-Ciberseguridad-Industrial-300x150.jpg 300w, https://www.cci-es.org/wp-content/uploads/Estrategia-de-Ciberseguridad-Industrial-768x384.jpg 768w, https://www.cci-es.org/wp-content/uploads/Estrategia-de-Ciberseguridad-Industrial-1536x768.jpg 1536w, https://www.cci-es.org/wp-content/uploads/Estrategia-de-Ciberseguridad-Industrial-1920x960.jpg 1920w" sizes="auto, (max-width: 1024px) 100vw, 1024px" />How MACIN turns industrial cybersecurity into a strategic asset (with two practical cases)</h2>
<p><span data-path-to-node="5,1"><span class="citation-1631">In industrial cybersecurity (OT/ICS), there is a very common trap: confusing “having controls” with “having capability”</span></span><span data-path-to-node="5,3">. </span><span data-path-to-node="5,5"><span class="citation-1630">Many organizations might “pass” a checklist because a procedure, a SOC, a ticketing tool, or a patching policy exists</span></span><span data-path-to-node="5,7">. </span><span data-path-to-node="5,9"><span class="citation-1629">But when a real incident arrives—with pressure for continuity, legacy systems, connected third parties, and limited maintenance windows—the question that truly matters arises</span></span><span data-path-to-node="5,11">:</span></p>
<p>Does this work consistently on the plant floor… or does it only exist on paper?</p>
<p><span data-path-to-node="7,1"><span class="citation-1627 interactive-span-hovered">That is where </span><b data-path-to-node="7,1" data-index-in-node="14"><span class="citation-1627 interactive-span-hovered">MACIN</span></b><span class="citation-1627 interactive-span-hovered"> adds value: it helps you move from a binary verification (“yes/no”) to a </span><b data-path-to-node="7,1" data-index-in-node="93"><span class="citation-1627 interactive-span-hovered">maturity measurement</span></b><span class="citation-1627 interactive-span-hovered">that reflects if the organization has </span><b data-path-to-node="7,1" data-index-in-node="152"><span class="citation-1627 interactive-span-hovered">real, repeatable, and improvable capability</span></b></span><span data-path-to-node="7,3">. </span><span data-path-to-node="7,5"><span class="citation-1626">And that, for Management, has an immediate effect: </span><b data-path-to-node="7,5" data-index-in-node="51"><span class="citation-1626">prioritizing investments, justifying decisions, and demonstrating progress with evidence</span></b><span class="citation-1626">, not perceptions</span></span><span data-path-to-node="7,7">.</span></p>
<h2 class="source-inline-chip-container ng-star-inserted">Why does the checklist fall short in OT?</h2>
<p><span data-path-to-node="9,1"><span class="citation-1625">A checklist is useful to start, but it usually fails on three key points</span></span><span data-path-to-node="9,3">:</span></p>
<ol>
<li><b>Measures existence, not efficacy.</b> “There is a procedure” does not mean it is executed well under pressure, nor that it is adapted to OT.</li>
<li><b>Does not capture interdependencies.</b> In industrial environments, capability depends on processes + people + technology + results. If one leg fails, the control “doesn’t hold”.</li>
<li><b>Does not prioritize by operational impact.</b> Everything seems urgent; without maturity, it is easy to invest where it is most “visible,” not where risk is reduced the most</li>
</ol>
<p><span data-path-to-node="11,1"><span class="citation-1620">MACIN has been built by professionals with extensive experience and fieldwork to add value and turn it into a reporting lever for Management</span></span><span data-path-to-node="11,3">. </span></p>
<ul>
<li><span data-path-to-node="11,3">MACIN is not just another report; it is an instrument to govern an OT program. </span><span data-path-to-node="11,5"><span class="citation-1619">It allows you to</span></span><span data-path-to-node="11,7">:</span>
<ul>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="12,0,0,1"><span class="citation-1618">Obtain a clear </span><b data-path-to-node="12,0,0,1" data-index-in-node="15"><span class="citation-1618">baseline</span></b><span class="citation-1618"> (by domains and practices mapped against reference frameworks)</span></span></li>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="12,1,0,1"><span class="citation-1617">Identify “paper vs. operation” gaps</span></span></li>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="12,2,0,1"><span class="citation-1616">Build a </span><b data-path-to-node="12,2,0,1" data-index-in-node="8"><span class="citation-1616">prioritized roadmap</span></b><span class="citation-1616"> (what to do first and why)</span></span></li>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="12,3,0,1"><span class="citation-1615">Align OT, IT, and management with a common language</span></span><span data-path-to-node="12,3,0,3">.</span></li>
<li aria-level="1"><span data-path-to-node="12,4,0,1"><span class="citation-1614">Repeat the measurement to demonstrate </span><b data-path-to-node="12,4,0,1" data-index-in-node="38"><span class="citation-1614">continuous improvement</span></b></span></li>
</ul>
</li>
</ul>
<p data-path-to-node="13"><span data-path-to-node="13,1"><span class="citation-1613">Put in Management terms: it </span><b data-path-to-node="13,1" data-index-in-node="28"><span class="citation-1613">reduces uncertainty</span></b><span class="citation-1613">, improves decision-making, and helps protect continuity, safety, and production with traceable actions</span></span><span data-path-to-node="13,3">.</span></p>
<p data-path-to-node="13"><span data-path-to-node="14,1"><span class="citation-1612">And since the best way to prove this is with examples or use cases, let’s particularize its use in two contexts</span></span><span data-path-to-node="14,3">:</span></p>
<h2 data-path-to-node="13">Case 1: OT Incident Management</h2>
<h3>What a checklist “sees” vs. what maturity “sees” (MACIN – Domain 8)</h3>
<p><span data-path-to-node="18,0"><b data-path-to-node="18,0" data-index-in-node="0">Realistic scenario:</b> A vendor attempts to connect outside the maintenance window to an engineering station. The SOC detects anomalous activity. </span><span data-path-to-node="18,2"><span class="citation-1610">Operations asks for caution to avoid affecting production</span></span><span data-path-to-node="18,4">.</span></p>
<h4><span data-path-to-node="20,0"><span class="citation-1609">Checklist Vision (Binary)</span></span></h4>
<ol>
<li data-path-to-node="21,0,0"><span data-path-to-node="21,0,0,1"><span class="citation-1608"><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /> “Incident response procedure exists” </span></span></li>
<li data-path-to-node="21,1,0"><span data-path-to-node="21,1,0,1"><span class="citation-1607"><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /> “There is a SOC/CSIRT and escalation” </span></span></li>
<li data-path-to-node="21,2,0"><span data-path-to-node="21,2,0,1"><span class="citation-1606"><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /> “Incidents are registered in tickets” </span></span></li>
<li data-path-to-node="21,3,0"><span data-path-to-node="21,3,0,1"><span class="citation-1605"><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /> “A simulation was conducted”</span></span></li>
</ol>
<p><span data-path-to-node="23,0"><b data-path-to-node="23,0" data-index-in-node="0"><span class="citation-1604">Checklist conclusion:</span></b><span class="citation-1604"> “Incident management implemented”.</span></span></p>
<h4><span data-path-to-node="25,0"><span class="citation-1603">Analysis under MACIN maturity review logic (Real Capability)</span></span><span data-path-to-node="25,2">:</span></h4>
<p><span data-path-to-node="26,1"><span class="citation-1602">MACIN goes down to the detail of the capabilities that must work end-to-end</span></span><span data-path-to-node="26,3">:</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="27,0,1,0"><b data-path-to-node="27,0,1,0" data-index-in-node="0"><span class="citation-1601">Detection and triage with OT logic:</span></b><span class="citation-1601"> classification, severity, and interpretation with context (8.1.1 – 8.1.3)</span></span><span data-path-to-node="27,0,1,2">.</span></li>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="27,1,1,0"><b data-path-to-node="27,1,1,0" data-index-in-node="0"><span class="citation-1600">Decision and escalation without improvisation:</span></b><span class="citation-1600"> when an event becomes an incident, to whom it is escalated, and how the cycle is operated (8.2.1 – 8.2.5)</span></span><span data-path-to-node="27,1,1,2">.</span></li>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="27,2,1,0"><b data-path-to-node="27,2,1,0" data-index-in-node="0"><span class="citation-1599">Executable response in the plant:</span></b><span class="citation-1599"> trained roles, OT playbooks, activities by phase, and continuity criteria (8.3.1 – 8.3.4)</span></span><span data-path-to-node="27,2,1,2">.</span></li>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="27,3,1,0"><b data-path-to-node="27,3,1,0" data-index-in-node="0"><span class="citation-1598">Communication and coordination:</span></b><span class="citation-1598"> stakeholders, notification, and coordination with third parties while preserving evidence (8.4.1 – 8.4.3)</span></span><span data-path-to-node="27,3,1,2">.</span></li>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="27,4,1,0"><b data-path-to-node="27,4,1,0" data-index-in-node="0"><span class="citation-1597">Lessons learned:</span></b><span class="citation-1597"> proportional analysis, improvements that are closed, and exercises that validate efficacy (8.5.1 – 8.5.3)</span></span><span data-path-to-node="27,4,1,2">.</span></li>
</ul>
<p><span data-path-to-node="29,0"><b data-path-to-node="29,0" data-index-in-node="0"><span class="citation-1596">Key difference:</span></b><span class="citation-1596"> the checklist demonstrates that “a plan exists” </span></span><span data-path-to-node="29,3"><span class="citation-1595">; the maturity evidences if that plan </span><b data-path-to-node="29,3" data-index-in-node="38"><span class="citation-1595">can be executed</span></b><span class="citation-1595"> and if it improves with every cycle</span></span><span data-path-to-node="29,5">.</span></p>
<h2 class="source-inline-chip-container ng-star-inserted">Case 2: Vulnerability Management in OT</h2>
<h3>From “we have a patching policy” to “we know what to treat, when, and how” (MACIN – Domain 3)</h3>
<p><span data-path-to-node="33,0"><b data-path-to-node="33,0" data-index-in-node="0">Realistic scenario:</b> A critical vulnerability affecting HMI/engineering software is published. In OT, aggressive scanning is not possible, the patch requires a shutdown, and the vendor takes time to validate. </span><span data-path-to-node="33,2"><span class="citation-1593">Meanwhile, there is risk</span></span><span data-path-to-node="33,4">.</span><br style="font-weight: 400;" /><br style="font-weight: 400;" /></p>
<h4><span data-path-to-node="35,0"><b data-path-to-node="35,0" data-index-in-node="0"></b><span class="citation-1592">Checklist Vision (Binary)</span></span><span data-path-to-node="35,2">:</span></h4>
<ul>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;"><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /></span><span style="font-weight: 400;"> “We have a patching policy”</span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;"><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /></span><span style="font-weight: 400;"> “We perform periodic scans” </span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;"><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /></span><span style="font-weight: 400;"> <span data-path-to-node="36,2,0,1"><span class="citation-1589">“We have a vulnerability register” </span></span></span></li>
<li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;"><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2705.png" alt="✅" class="wp-smiley" style="height: 1em; max-height: 1em;" /></span><span style="font-weight: 400;"> “We apply patches when possible”</span></li>
</ul>
<p><span data-path-to-node="38,0"><b data-path-to-node="38,0" data-index-in-node="0"><span class="citation-1587 interactive-span-hovered">Checklist conclusion:</span></b><span class="citation-1587 interactive-span-hovered"> “Vulnerability management implemented”</span></span><span data-path-to-node="38,2">.</span></p>
<div class="source-inline-chip-container ng-star-inserted">
<h4 data-path-to-node="40"><span data-path-to-node="40,0"><span class="citation-1586">Analysis under MACIN maturity review logic (Real Capability)</span></span><span data-path-to-node="40,2">:</span></h4>
<div class="source-inline-chip-container ng-star-inserted"><span data-path-to-node="41,1"><span class="citation-1585">MACIN converts that situation into a set of practices that, if mature, avoid the “chaos” of every CVE</span></span><span data-path-to-node="41,3">:</span></div>
<div></div>
<div></div>
<div class="source-inline-chip-container ng-star-inserted">
<h5><b>1) Govern the process (not just react)</b></h5>
<ul>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="43,3"><span class="citation-1583">Define objectives, criteria, resources; document/approve the process; communicate and review needs (3.1.1 – 3.1.4)</span></span><span data-path-to-node="43,5">. </span><span data-path-to-node="43,7"><b data-path-to-node="43,7" data-index-in-node="0"><span class="citation-1582">Key question:</span></b><span class="citation-1582"> Do we have clear rules for OT (what can be scanned, what cannot, and how is it decided)?</span></span></li>
</ul>
<h5><b>2) Identify, evaluate, and prioritize with OT context</b></h5>
<ul>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="45,3"><span class="citation-1580">Information sources, continuous collection, safe manual/automated tests, interpretation, evaluations, and prioritization/communication (3.2.1 – 3.2.6)</span></span><span data-path-to-node="45,5">. </span><span data-path-to-node="45,7"><b data-path-to-node="45,7" data-index-in-node="0"><span class="citation-1579">Key question:</span></b><span class="citation-1579"> Do we prioritize by “high CVSS” or by real impact on the process (exposure, asset criticality, available compensations, maintenance window)? </span></span></li>
</ul>
<h5><b>3) Treat the vulnerability without disrupting operations </b></h5>
<ul>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="47,3"><span class="citation-1577">Analyze options and </span><b data-path-to-node="47,3" data-index-in-node="20"><span class="citation-1577">operational impact</span></b><span class="citation-1577">, treatment plans, execution of mitigations, exception logging, and residual risk communication (3.3.1 – 3.3.5)</span></span><span data-path-to-node="47,5">. </span><span data-path-to-node="47,7"><b data-path-to-node="47,7" data-index-in-node="0"><span class="citation-1576">Maturity example:</span></b><span class="citation-1576"> if patching is not immediately possible, treatment is defined: temporal segmentation, strict remote access control, hardening, specific rules, monitoring, and a formal exception with expiration and a plan</span></span></li>
</ul>
<h5><b>4) Measure effectiveness and improve</b></h5>
<ul>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="49,3"><span class="citation-1574">Monitor compliance/effectiveness, communicate status, and establish improvement plans (3.4.1 – 3.4.3)</span></span><span data-path-to-node="49,5">. </span><span data-path-to-node="49,7"><b data-path-to-node="49,7" data-index-in-node="0"><span class="citation-1573">Business result:</span></b><span class="citation-1573">fewer repeated “scares,” less invisible technical debt, and traceable decisions (why it is accepted, mitigated, or patched)</span></span><span data-path-to-node="49,9">.</span>
<div class="source-inline-chip-container ng-star-inserted"></div>
</li>
</ul>
<p><span data-path-to-node="51,0"><b data-path-to-node="51,0" data-index-in-node="0"><span class="citation-1572">Key difference:</span></b><span class="citation-1572"> the checklist tells you “there is a policy”; maturity tells you if a </span><b data-path-to-node="51,0" data-index-in-node="85"><span class="citation-1572">sustained capability</span></b><span class="citation-1572"> exists to manage OT vulnerabilities with operational realism, documented decisions, and measurable results</span></span></p>
<p><span data-path-to-node="52,1"><span class="citation-1571">These two cases can serve as examples to evidence the different visions provided by the Checklist-based review and the maturity evaluation</span></span><span data-path-to-node="52,3">. </span><span data-path-to-node="52,5"><span class="citation-1570">In this new MACIN update, maturity criteria have also been established for four essential pillars that must be coherent and consistent</span></span></p>
<h3><b>1) <span data-path-to-node="54,0"><span class="citation-1569">Processes: converting intention into repeatable operation</span></span><span data-path-to-node="54,2">.</span></b></h3>
<p><span data-path-to-node="54,2"><b data-path-to-node="54,2" data-index-in-node="2">What it brings:</b> the <b data-path-to-node="54,2" data-index-in-node="22">Processes</b> axis tells you if the organization has a <b data-path-to-node="54,2" data-index-in-node="73">standardized and governed</b> way of doing things (define, execute, review, improve). </span><span data-path-to-node="54,4"><span class="citation-1568">In OT this is critical because, if the process is weak, everything becomes “ad-hoc” when urgencies arise (shutdowns, incidents, changes, vendor support)</span></span><span data-path-to-node="54,6">. </span></p>
</div>
<div class="source-inline-chip-container ng-star-inserted"><span data-path-to-node="54,8"><b data-path-to-node="54,8" data-index-in-node="0"><span class="citation-1567">What it “unmasks” versus the checklist:</span></b><span class="citation-1567"> that “a procedure exists” does not imply there are clear criteria, phases, roles, escalation, review, and improvement</span></span><span data-path-to-node="54,10">. </span><span data-path-to-node="54,12"><span class="citation-1566">A mature process is noticeable because it </span><b data-path-to-node="54,12" data-index-in-node="42"><span class="citation-1566">reduces improvisation</span></b><span class="citation-1566"> and </span><b data-path-to-node="54,12" data-index-in-node="68"><span class="citation-1566">accelerates decisions</span></b><span class="citation-1566"> without breaking continuity</span></span></div>
<div></div>
<div class="source-inline-chip-container ng-star-inserted">
<h3><b>2)People: moving from heroes to institutional capabilities.</b></h3>
<p><span data-path-to-node="56,2"><b data-path-to-node="56,2" data-index-in-node="1">What it brings:</b> the <b data-path-to-node="56,2" data-index-in-node="21">People</b> axis measures if there are <b data-path-to-node="56,2" data-index-in-node="55">defined roles</b>, competencies, training, and sufficient drilling to execute the process (not just understand it). </span><span data-path-to-node="56,4"><span class="citation-1564">In industrial cybersecurity, the usual gap is not a “lack of people,” but a </span><b data-path-to-node="56,4" data-index-in-node="76"><span class="citation-1564">lack of cross-training</span></b><span class="citation-1564"> (SOC–OT–operations–maintenance) and dependence on key individuals</span></span><span data-path-to-node="56,6">. </span></p>
</div>
<div class="source-inline-chip-container ng-star-inserted"><span data-path-to-node="56,8"><b data-path-to-node="56,8" data-index-in-node="0"><span class="citation-1563">What it “unmasks” versus the checklist:</span></b><span class="citation-1563"> an org chart is not equivalent to a capability</span></span><span data-path-to-node="56,10">. </span><span data-path-to-node="56,12"><span class="citation-1562">Maturity in people is seen when the organization responds well even if “person X is not there” and when training is conducted for real OT scenarios</span></span><span data-path-to-node="56,14">.</span></div>
<div class="source-inline-chip-container ng-star-inserted"><span data-path-to-node="56,14"><br />
</span></p>
<h3><b>3) <span data-path-to-node="58,0"><span class="citation-1561">Technologies/Tools: having useful, integrated, and maintained means.</span></span></b></h3>
<p><span data-path-to-node="58,2"><b data-path-to-node="58,2" data-index-in-node="1">What it brings:</b> the <b data-path-to-node="58,2" data-index-in-node="21">Technologies</b> axis focuses on whether tools <b data-path-to-node="58,2" data-index-in-node="64">exist, are well configured, integrated, and kept alive</b>(use cases, rules, coverage, automation). </span><span data-path-to-node="58,4"><span class="citation-1560">In OT, it is frequent to have “legacy” or “underutilized” tools, or to use IT solutions without adapting them to OT constraints</span></span><span data-path-to-node="58,6">. </span></p>
</div>
<div class="source-inline-chip-container ng-star-inserted">
<p><span data-path-to-node="58,8"><b data-path-to-node="58,8" data-index-in-node="0"><span class="citation-1559">What it “unmasks” versus the checklist:</span></b><span class="citation-1559"> buying a tool does not create capability if there is no tuning, integration, operating procedures, and a deployment strategy by criticality</span></span><span data-path-to-node="58,10">.</span></p>
<h3><b>4)<span data-path-to-node="60,0"><span class="citation-1558">Results: demonstrating effectiveness (and being able to improve).</span></span></b></h3>
<p><span data-path-to-node="60,2"><b data-path-to-node="60,2" data-index-in-node="1">What it brings:</b> the <b data-path-to-node="60,2" data-index-in-node="21">Results</b> axis is the one that breaks most with the checklist: it forces looking at <b data-path-to-node="60,2" data-index-in-node="103">what is achieved</b> and how it is demonstrated (metrics, traceability, coverage, lessons learned, reduction of repetition). </span><span data-path-to-node="60,4"><span class="citation-1557">It is the “closing of the circle”: without results, there is no real feedback or evidence-based prioritization</span></span><span data-path-to-node="60,6">. </span></p>
</div>
<div class="source-inline-chip-container ng-star-inserted">
<p><span data-path-to-node="60,8"><b data-path-to-node="60,8" data-index-in-node="0"><span class="citation-1556">What it “unmasks” versus the checklist:</span></b><span class="citation-1556"> you can “comply” and still not know if you detect on time, if your response reduces impact, or if you repeat incidents due to the same causes</span></span><span data-path-to-node="60,10">.</span></p>
<p><span data-path-to-node="61,1"><span class="citation-1555">Therefore, as we have been able to see throughout the examples and the analysis of the pillars on which MACIN is based, we can obtain the following conclusions:</span></span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="62,0,1,0"><b data-path-to-node="62,0,1,0" data-index-in-node="0"><span class="citation-1554">MACIN helps you know where you truly are</span></b><span class="citation-1554"> (not where you think you are)</span></span><span data-path-to-node="62,0,1,2">.</span></li>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="62,1,1,0"><b data-path-to-node="62,1,1,0" data-index-in-node="0"><span class="citation-1553">It helps you decide what to do first</span></b><span class="citation-1553"> (prioritization with operational sense).</span></span></li>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="62,2,1,0"><b data-path-to-node="62,2,1,0" data-index-in-node="0"><span class="citation-1552">It helps you demonstrate progress</span></b><span class="citation-1552"> (evidence and continuous improvement)</span></span><span data-path-to-node="62,2,1,2">.</span></li>
<li style="font-weight: 400;" aria-level="1"><span data-path-to-node="62,3,1,0"><b data-path-to-node="62,3,1,0" data-index-in-node="0"><span class="citation-1551">It helps you align teams</span></b><span class="citation-1551"> (OT/IT/management, with a common framework)</span></span><span data-path-to-node="62,3,1,2">.</span>
<div class="source-inline-chip-container ng-star-inserted"></div>
</li>
</ul>
<p>&nbsp;</p>
<h3 style="text-align: center;" data-prosemirror-content-type="node" data-prosemirror-node-name="paragraph" data-prosemirror-node-block="true" data-pm-slice="1 1 []"><a href="https://www.linkedin.com/in/javiercao/" target="_blank" rel="nofollow noopener"><strong data-prosemirror-content-type="mark" data-prosemirror-mark-name="strong">Javier Cao Avellaneda</strong></a></h3>
<h3 style="text-align: center;" data-prosemirror-content-type="node" data-prosemirror-node-name="paragraph" data-prosemirror-node-block="true" data-pm-slice="1 1 []">Coordinator of the Industrial Cybersecurity Centre</h3>
<h3 style="text-align: center;"><strong> – –</strong></h3>
<h3 style="text-align: center;">Further information about the MACIN Platform can be found <a href="https://macin.cci-es.org/en/login">here.</a></h3>
<h3 style="text-align: center;"></h3>
</div>
<p>&nbsp;</p>
<p data-path-to-node="41">
</div>
<p>&nbsp;</p>
<p><br style="font-weight: 400;" /><br style="font-weight: 400;" /></p>
<div class="source-inline-chip-container ng-star-inserted"></div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>The power of sharing knowledge in industrial cybersecurity</title>
		<link>https://www.cci-es.org/en/the-power-of-sharing-knowledge-in-industrial-cybersecurity/</link>
		
		<dc:creator><![CDATA[Maite Carli]]></dc:creator>
		<pubDate>Tue, 16 Dec 2025 18:26:36 +0000</pubDate>
				<category><![CDATA[English]]></category>
		<guid isPermaLink="false">https://www.cci-es.org/?p=24939</guid>

					<description><![CDATA[In the world of industrial cybersecurity, progress is never achieved alone. The challenges are too complex, the systems too interconnected, and the threats too advanced to be faced in isolation. In this environment, sharing knowledge is not a courtesy it is a survival strategy and a collective responsibility. That’s why, at the Industrial Cybersecurity Center [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>In the world of industrial cybersecurity, <strong>progress is never achieved alone</strong>. The challenges are too complex, the systems too interconnected, and the threats too advanced to be faced in isolation. In this environment, sharing knowledge is not a courtesy it is a survival strategy and <strong>a collective responsibility</strong>.</p>
<p>That’s why, at the Industrial Cybersecurity Center (CCI), we use our holiday greeting to highlight a simple truth: <strong>industrial cybersecurity thrives when its community does.</strong></p>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-24940 size-full" src="https://www.cci-es.org/wp-content/uploads/Christmas-greetings-CCI-scaled.jpg" alt="" width="2560" height="1429" srcset="https://www.cci-es.org/wp-content/uploads/Christmas-greetings-CCI-scaled.jpg 2560w, https://www.cci-es.org/wp-content/uploads/Christmas-greetings-CCI-300x167.jpg 300w, https://www.cci-es.org/wp-content/uploads/Christmas-greetings-CCI-1024x572.jpg 1024w, https://www.cci-es.org/wp-content/uploads/Christmas-greetings-CCI-768x429.jpg 768w, https://www.cci-es.org/wp-content/uploads/Christmas-greetings-CCI-1536x857.jpg 1536w, https://www.cci-es.org/wp-content/uploads/Christmas-greetings-CCI-1920x1072.jpg 1920w" sizes="auto, (max-width: 2560px) 100vw, 2560px" /></p>
<p><!--StartFragment --></p>
<h2><strong>1. Knowledge is the gift that grows the most when shared</strong></h2>
<p>Industrial cybersecurity is always evolving, always demanding learning, and always requiring us to stay connected. That’s why sharing is not about losing an advantage—it’s about building one.</p>
<p>At CCI, we will continue to foster spaces, resources, and platforms where knowledge is exchanged: workshops, guides, high‑impact scenarios, the ICSOs community, “Voice of the Industry” gatherings, sectoral studies, and of course, our network of professionals, coordinators, and experts who make learning a mutual gift.</p>
<h2><strong>2. Evolving together</strong></h2>
<p>Every plant, every integrator, every supplier faces incidents, doubts, decisions, and lessons that can help others. What may be a single discovery for one organization can become a clue, a warning, or a solution for the community.</p>
<p>That journey—from data to information, and from information to intelligence—happens above all when knowledge is shared. The community is the engine that transforms isolated experiences into a common map of risks, trends, and best practices.</p>
<h2><strong>3. Sharing is protecting</strong></h2>
<p>In many fields, sharing information may be optional. In OT environments, it is not. Industry faces attacks with physical consequences: production stoppages, equipment damage, disruption of essential services, and risks to people. When someone uncovers a vulnerability, a poor practice, or an incident, sharing that lesson is as critical as applying a patch or strengthening a firewall.</p>
<p>Shared knowledge becomes a protective layer that no technology can provide on its own.</p>
<h2><strong>4. Collaboration reduces uncertainty and expands capabilities</strong></h2>
<p>Industrial cybersecurity teams are not unlimited—neither is their time or analytical capacity. As OT grows more complex and IT/OT convergence accelerates, no organization masters every dimension: regulations, architectures, threats, automation, training, incident response, supplier management…</p>
<p>Sharing knowledge enables us to:</p>
<ul>
<li><strong>Shorten investigation times</strong></li>
<li><strong>Make better strategic decisions</strong></li>
<li><strong>Accelerate the maturity of the entire industry</strong></li>
<li><strong>Enhance detection and response capabilities</strong></li>
</ul>
<p>Ultimately, <strong>collaboration is not a defensive option; it is the multiplier of competitiveness and resilience.</strong></p>
<h2><strong>5. Community is the greatest asset of industrial cybersecurity</strong></h2>
<p>Our holiday greeting reflects the journey of a professional who shares knowledge, evolves, collaborates, and feels part of something greater than their own organization.</p>
<p>In an environment where every link matters, community is the factor that turns engineers, integrators, manufacturers, and operators into a network capable of resisting and advancing.</p>
<p style="text-align: center;">This season, let’s celebrate what unites us: the spirit of community.</p>
<p><!--EndFragment --></p>
<p><img loading="lazy" decoding="async" class="size-medium wp-image-3917 aligncenter" src="https://www.cci-es.org/wp-content/uploads/CCI_Logo_Nombre-300x95.jpg" alt="" width="300" height="95" srcset="https://www.cci-es.org/wp-content/uploads/CCI_Logo_Nombre-300x95.jpg 300w, https://www.cci-es.org/wp-content/uploads/CCI_Logo_Nombre-1024x323.jpg 1024w, https://www.cci-es.org/wp-content/uploads/CCI_Logo_Nombre-768x242.jpg 768w, https://www.cci-es.org/wp-content/uploads/CCI_Logo_Nombre.jpg 1440w" sizes="auto, (max-width: 300px) 100vw, 300px" /></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>The Industrial Cybersecurity Center presents its 2026 events calendar</title>
		<link>https://www.cci-es.org/en/the-industrial-cybersecurity-center-presents-its-2026-events-calendar/</link>
		
		<dc:creator><![CDATA[Maite Carli]]></dc:creator>
		<pubDate>Mon, 01 Dec 2025 12:46:21 +0000</pubDate>
				<category><![CDATA[English]]></category>
		<guid isPermaLink="false">https://www.cci-es.org/?p=24774</guid>

					<description><![CDATA[At the Industrial Cybersecurity Center (CCI), we begin 2026 with the same energy that has defined us for more than a decade: creating spaces for meeting, collaboration, and knowledge sharing for Industrial Cybersecurity professionals. Our CCI Events Calendar 2026 is now available — an international journey through major industrial ecosystems where cybersecurity plays a strategic [&#8230;]]]></description>
										<content:encoded><![CDATA[<p data-start="128" data-end="366">At the <strong data-start="135" data-end="176">Industrial Cybersecurity Center (CCI)</strong>, we begin 2026 with the same energy that has defined us for more than a decade: creating spaces for meeting, collaboration, and knowledge sharing for Industrial Cybersecurity professionals.</p>
<p data-start="368" data-end="626">Our <strong data-start="372" data-end="400">CCI Events Calendar 2026</strong> is now available — an international journey through major industrial ecosystems where cybersecurity plays a strategic role. This year, we further strengthen our presence in Latin America, Europe, and key regions across Spain.</p>
<p data-start="628" data-end="1017">Our mission remains unchanged: <strong data-start="659" data-end="791">to foster synergies, share real-world experiences, and build a strong community around the protection of industrial environments</strong>. The events <em data-start="804" data-end="828">La Voz de la Industria</em> and our conferences <strong data-start="849" data-end="865">CCICON LATAM</strong> and <strong data-start="870" data-end="887">CCICON EUROPE</strong> will once again serve as essential meeting points for CISOs, OT leaders, manufacturers, integrators, and specialized consultants.</p>
<p data-start="1019" data-end="1054">Below, we share the official dates:</p>
<p data-start="1019" data-end="1054"><img loading="lazy" decoding="async" class="aligncenter wp-image-24775 size-full" src="https://www.cci-es.org/wp-content/uploads/ENG-infografia-eventos-CCI.png" alt="" width="526" height="741" srcset="https://www.cci-es.org/wp-content/uploads/ENG-infografia-eventos-CCI.png 526w, https://www.cci-es.org/wp-content/uploads/ENG-infografia-eventos-CCI-213x300.png 213w" sizes="auto, (max-width: 526px) 100vw, 526px" /></p>
<h2 data-start="1061" data-end="1075">Why attend?</h2>
<p data-start="1077" data-end="1119">Each of these events is designed to offer:</p>
<ul data-start="1121" data-end="1595">
<li data-start="1121" data-end="1196">
<p data-start="1123" data-end="1196"><strong data-start="1123" data-end="1166">Real-world cases and practical insights</strong> directly from the industry.</p>
</li>
<li data-start="1197" data-end="1394">
<p data-start="1199" data-end="1394"><strong data-start="1199" data-end="1223">Updated perspectives</strong> on regulations, best practices, and emerging trends (ISA/IEC 62443, IIoT, AI-driven cybersecurity, risk management, OT security, supply chain protection, among others).</p>
</li>
<li data-start="1395" data-end="1500">
<p data-start="1397" data-end="1500"><strong data-start="1397" data-end="1425">Networking opportunities</strong> to connect with professionals, organizations, and leaders in the sector.</p>
</li>
<li data-start="1501" data-end="1595">
<p data-start="1503" data-end="1595"><strong data-start="1503" data-end="1532">Technological innovations</strong> presented by specialized manufacturers and solution providers.</p>
</li>
</ul>
<h2 data-start="1602" data-end="1642">We look forward to seeing you in 2026</h2>
<p data-start="1644" data-end="1872">We invite you to save the dates and join us on this international journey focused on strengthening industrial cybersecurity. Each event is a unique opportunity to learn, collaborate, and advance the protection of our industries.</p>
<p data-start="1874" data-end="1933"><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f449.png" alt="👉" class="wp-smiley" style="height: 1em; max-height: 1em;" /> Find all updated information:</p>
<blockquote class="wp-embedded-content" data-secret="S3W4iB9mKO"><p><a href="https://www.cci-es.org/en/events/">Activities</a></p></blockquote>
<p><iframe loading="lazy" class="wp-embedded-content" sandbox="allow-scripts" security="restricted"  title="«Activities» — Centro de Ciberseguridad Industrial" src="https://www.cci-es.org/en/events/embed/#?secret=dVZmD3DcN0#?secret=S3W4iB9mKO" data-secret="S3W4iB9mKO" width="600" height="338" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe></p>
<p>&nbsp;</p>
<p data-start="1874" data-end="1933">
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>CRA: the industry needs an adaptation of the Cyber Resilience Regulation</title>
		<link>https://www.cci-es.org/en/cra-the-industry-needs-an-adaptation-of-the-cyber-resilience-regulation/</link>
		
		<dc:creator><![CDATA[Maite Carli]]></dc:creator>
		<pubDate>Tue, 25 Nov 2025 11:53:12 +0000</pubDate>
				<category><![CDATA[English]]></category>
		<guid isPermaLink="false">https://www.cci-es.org/?p=24746</guid>

					<description><![CDATA[&#8220;The approval of the Cyber Resilience Regulation (CRA) by the European Union marks a turning point in the security of products with digital elements. It is a historic step towards a safer, more transparent, and more robust market. But it also raises an essential question for our ecosystem: Can a regulation be directly applied to [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>&#8220;The approval of the Cyber Resilience Regulation (CRA) by the European Union marks a turning point in the security of products with digital elements. It is a historic step towards a safer, more transparent, and more robust market. But it also raises an essential question for our ecosystem: <strong>Can a regulation be directly applied to operational technologies whose lifecycle, operational constraints, and risks are completely different?</strong></p>
<p><em>At CCI, we believe the answer is clear: no. And that is precisely the motivation behind the new CRA Industrial Position Paper.</em></p>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-24733 size-full" src="https://www.cci-es.org/wp-content/uploads/Portada-CRA.png" alt="" width="522" height="735" srcset="https://www.cci-es.org/wp-content/uploads/Portada-CRA.png 522w, https://www.cci-es.org/wp-content/uploads/Portada-CRA-213x300.png 213w" sizes="auto, (max-width: 522px) 100vw, 522px" /></p>
<h2><strong>Why the industry needs an adapted CRA</strong></h2>
<p>Operational technology environments are not an extension of IT. They are critical systems that have been in operation for decades, with lifecycles of 15 to 30 years, highly customized integrations, and one non-negotiable requirement: <strong>operational availability is sacred. That is why, at CCI, we uphold a key idea: </strong></p>
<p><strong>without a specific adaptation for OT, the CRA cannot be applied effectively, efficiently, or fairly in the industry.</strong></p>
<h2><strong>What does CCI propose with the multisectoral Industrial CRA</strong></h2>
<p>The <em>Position Paper</em> proposes a structured, pragmatic adaptation aligned with European principles, based on key pillars:</p>
<ol>
<li>
<h3><strong>An approach based on real industrial risk</strong></h3>
</li>
</ol>
<p>CCI’s Industrial CRA proposes classifying products according to their level of threat and operational impact (Class I, II, or Critical), taking into account not only digital vulnerabilities but also physical security, service continuity, and the sector-specific regulatory environment.</p>
<ol start="2">
<li>
<h3><strong>Balance between cybersecurity and availability</strong></h3>
</li>
</ol>
<p>The goal is not to impose unfeasible requirements, but to ensure that any measure strengthens security <strong>without jeopardizing operations</strong>. For this reason, the concept of <strong>compensatory security plans is promoted,</strong> a key element in OT.</p>
<ol start="3">
<li>
<h3><strong>Gradualness and orderly transition</strong></h3>
</li>
</ol>
<p>The proposal sets out a realistic roadmap:</p>
<p><!--StartFragment --></p>
<ul>
<li>Start of Industrial CRA in 2026</li>
<li>Obligation for new products in 2027</li>
<li>Transition until 2032 for already operational products</li>
</ul>
<p><!--EndFragment --></p>
<ol start="4">
<li>
<h3><strong>Shared responsibility (manufacturer–integrator–operator)</strong></h3>
</li>
</ol>
<p>For the first time, a distributed compliance model is articulated that recognizes OT cybersecurity depends on the ecosystem, not just the manufacturer. This includes coordinated vulnerability management, commissioning validation, and continuous monitoring</p>
<ol start="5">
<li>
<h3><strong>Adaptation of Common Criteria to the OT world</strong></h3>
</li>
</ol>
<p>The document proposes concrete changes to EUCC and Common Criteria to make them viable in OT:</p>
<p><!--StartFragment --></p>
<ul>
<li>Protection profiles for PLCs, RTUs, IEDs, SCADA, or industrial gateways</li>
<li>Modular evaluations</li>
<li>Inclusion of real physical and operational threats</li>
<li>Integration with safety and sectoral regulations (IEC 61508, 61511…)</li>
</ul>
<h2><strong>The ultimate goal: a multisectoral guide for the entire industry</strong></h2>
<p>The Position Paper is the first step towards an Industrial <strong>CRA applied to sectors such as electricity, water, transport, chemicals, oil &amp; gas, food, healthcare, metallurgy, or manufacturing</strong>. It is a guide that will enable each stakeholder—manufacturer, integrator, and operator—to understand what is expected of them, how to comply, and how to do so without disruptions. The approach incorporates experiences from existing frameworks, such as the &#8216;substantial modification&#8217; mechanisms used in the railway or healthcare sectors, where technical and economic feasibility is part of the regulatory analysis.</p>
<p>&nbsp;</p>
<p><a href="https://www.cci-es.org/wp-content/uploads/CCI_Position-Paper-CRA-Industrial.pdf"><img loading="lazy" decoding="async" class="aligncenter wp-image-24747 size-medium" src="https://www.cci-es.org/wp-content/uploads/Access-document-BOTON-300x91.png" alt="" width="300" height="91" srcset="https://www.cci-es.org/wp-content/uploads/Access-document-BOTON-300x91.png 300w, https://www.cci-es.org/wp-content/uploads/Access-document-BOTON.png 364w" sizes="auto, (max-width: 300px) 100vw, 300px" /></a></p>
<p>&nbsp;</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How does the integration between the ESCIM and RECIN platforms work?</title>
		<link>https://www.cci-es.org/en/integration-escim-recin-platforms/</link>
		
		<dc:creator><![CDATA[Maite Carli]]></dc:creator>
		<pubDate>Fri, 27 Jun 2025 08:00:29 +0000</pubDate>
				<category><![CDATA[English]]></category>
		<guid isPermaLink="false">https://www.cci-es.org/?p=23694</guid>

					<description><![CDATA[What is RECIN and how does it model industrial architectures? In RECIN, as we already know, we can create an architecture based on Facilities, Zones, and Conduits, including the components present in each of them and defining criticality levels independently for availability, confidentiality, and integrity. If we log into ESCIM to characterize high-impact cyber incident scenarios [&#8230;]]]></description>
										<content:encoded><![CDATA[<article class="text-token-text-primary w-full" dir="auto" data-testid="conversation-turn-6" data-scroll-anchor="true">
<div class="text-base my-auto mx-auto py-5 [--thread-content-margin:--spacing(4)] @[37rem]:[--thread-content-margin:--spacing(6)] @[72rem]:[--thread-content-margin:--spacing(16)] px-(--thread-content-margin)">
<div class="[--thread-content-max-width:32rem] @[34rem]:[--thread-content-max-width:40rem] @[64rem]:[--thread-content-max-width:48rem] mx-auto flex max-w-(--thread-content-max-width) flex-1 text-base gap-4 md:gap-5 lg:gap-6 group/turn-messages focus-visible:outline-hidden" tabindex="-1">
<div class="group/conversation-turn relative flex w-full min-w-0 flex-col agent-turn">
<div>
<div>
<div dir="auto" data-message-author-role="assistant" data-message-id="f8da30de-5a08-499d-9c04-8dabca083600" data-message-model-slug="gpt-4o">
<div>
<div>
<h2 data-start="0" data-end="61">What is RECIN and how does it model industrial architectures?</h2>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</article>
<div></div>
<div>
<article class="text-token-text-primary w-full" dir="auto" data-testid="conversation-turn-8" data-scroll-anchor="true">
<div class="text-base my-auto mx-auto py-5 [--thread-content-margin:--spacing(4)] @[37rem]:[--thread-content-margin:--spacing(6)] @[72rem]:[--thread-content-margin:--spacing(16)] px-(--thread-content-margin)">
<div class="[--thread-content-max-width:32rem] @[34rem]:[--thread-content-max-width:40rem] @[64rem]:[--thread-content-max-width:48rem] mx-auto flex max-w-(--thread-content-max-width) flex-1 text-base gap-4 md:gap-5 lg:gap-6 group/turn-messages focus-visible:outline-hidden" tabindex="-1">
<div class="group/conversation-turn relative flex w-full min-w-0 flex-col agent-turn">
<div class="relative flex-col gap-1 md:gap-3">
<div class="flex max-w-full flex-col grow">
<div class="min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal [.text-message+&amp;]:mt-5" dir="auto" data-message-author-role="assistant" data-message-id="a4dc9597-041c-4bdd-aa7e-1d81f561950a" data-message-model-slug="gpt-4o">
<div class="flex w-full flex-col gap-1 empty:hidden first:pt-[3px]">
<div class="markdown prose dark:prose-invert w-full break-words light">
<p data-start="0" data-end="405" data-is-last-node="" data-is-only-node="">In <a href="https://recin.cci-es.org/" target="_blank" rel="noopener" data-saferedirecturl="https://www.google.com/url?q=https://recin.cci-es.org/&amp;source=gmail&amp;ust=1751011706231000&amp;usg=AOvVaw2DyRn1z4gA8uh6DXGEIWlN">RECIN</a>, as we already know, we can create an architecture based on Facilities, Zones, and Conduits, including the components present in each of them and defining criticality levels independently for availability, confidentiality, and integrity. If we log into <a href="https://escim.cci-es.org/" target="_blank" rel="noopener" data-saferedirecturl="https://www.google.com/url?q=https://escim.cci-es.org/&amp;source=gmail&amp;ust=1751011706231000&amp;usg=AOvVaw31TLBFM3YsKQFM5oshhuJ9">ESCIM</a> to characterize high-impact cyber incident scenarios using the same account we used in RECIN, upon selecting the &#8220;New Scenario&#8221; option&#8230;</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</article>
</div>
<div></div>
<div><img loading="lazy" decoding="async" class="wp-image-23695 size-full aligncenter" src="https://www.cci-es.org/wp-content/uploads/ESCIM-1.png" alt="" width="1007" height="104" srcset="https://www.cci-es.org/wp-content/uploads/ESCIM-1.png 1007w, https://www.cci-es.org/wp-content/uploads/ESCIM-1-300x31.png 300w, https://www.cci-es.org/wp-content/uploads/ESCIM-1-768x79.png 768w" sizes="auto, (max-width: 1007px) 100vw, 1007px" /></div>
<div></div>
<div>
<article class="text-token-text-primary w-full" dir="auto" data-testid="conversation-turn-10" data-scroll-anchor="true">
<div class="text-base my-auto mx-auto py-5 [--thread-content-margin:--spacing(4)] @[37rem]:[--thread-content-margin:--spacing(6)] @[72rem]:[--thread-content-margin:--spacing(16)] px-(--thread-content-margin)">
<div class="[--thread-content-max-width:32rem] @[34rem]:[--thread-content-max-width:40rem] @[64rem]:[--thread-content-max-width:48rem] mx-auto flex max-w-(--thread-content-max-width) flex-1 text-base gap-4 md:gap-5 lg:gap-6 group/turn-messages focus-visible:outline-hidden" tabindex="-1">
<div class="group/conversation-turn relative flex w-full min-w-0 flex-col agent-turn">
<div class="relative flex-col gap-1 md:gap-3">
<div class="flex max-w-full flex-col grow">
<div class="min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal [.text-message+&amp;]:mt-5" dir="auto" data-message-author-role="assistant" data-message-id="277339f1-c4af-471c-855b-be7cd39b8b73" data-message-model-slug="gpt-4o">
<div class="flex w-full flex-col gap-1 empty:hidden first:pt-[3px]">
<div class="markdown prose dark:prose-invert w-full break-words light">
<p data-start="0" data-end="238" data-is-last-node="" data-is-only-node="">we will have the option to complete all the information related to our scenario, including the zones and conduits that will be identified as &#8220;Impacted&#8221; and/or &#8220;Compromised.&#8221; However, we also have the option to &#8220;Import project from RECIN.&#8221;</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</article>
</div>
<article class="text-token-text-primary w-full" dir="auto" data-testid="conversation-turn-12" data-scroll-anchor="true">
<div class="text-base my-auto mx-auto py-5 [--thread-content-margin:--spacing(4)] @[37rem]:[--thread-content-margin:--spacing(6)] @[72rem]:[--thread-content-margin:--spacing(16)] px-(--thread-content-margin)">
<div class="[--thread-content-max-width:32rem] @[34rem]:[--thread-content-max-width:40rem] @[64rem]:[--thread-content-max-width:48rem] mx-auto flex max-w-(--thread-content-max-width) flex-1 text-base gap-4 md:gap-5 lg:gap-6 group/turn-messages focus-visible:outline-hidden" tabindex="-1">
<div class="group/conversation-turn relative flex w-full min-w-0 flex-col agent-turn">
<div class="relative flex-col gap-1 md:gap-3">
<div class="flex max-w-full flex-col grow">
<div class="min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal [.text-message+&amp;]:mt-5" dir="auto" data-message-author-role="assistant" data-message-id="07d89803-8cda-4da1-b3dc-fb4578893a70" data-message-model-slug="gpt-4o">
<div class="flex w-full flex-col gap-1 empty:hidden first:pt-[3px]">
<div class="markdown prose dark:prose-invert w-full break-words light">
<h2 data-start="0" data-end="42">Creating cyber incident scenarios in ESCIM</h2>
<p>&nbsp;</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</article>
<div></div>
<div><img loading="lazy" decoding="async" class="aligncenter wp-image-23696 size-full" src="https://www.cci-es.org/wp-content/uploads/ESCIM-2.png" alt="" width="1648" height="466" srcset="https://www.cci-es.org/wp-content/uploads/ESCIM-2.png 1648w, https://www.cci-es.org/wp-content/uploads/ESCIM-2-300x85.png 300w, https://www.cci-es.org/wp-content/uploads/ESCIM-2-1024x290.png 1024w, https://www.cci-es.org/wp-content/uploads/ESCIM-2-768x217.png 768w, https://www.cci-es.org/wp-content/uploads/ESCIM-2-1536x434.png 1536w" sizes="auto, (max-width: 1648px) 100vw, 1648px" /></div>
<div></div>
<article class="text-token-text-primary w-full" dir="auto" data-testid="conversation-turn-14" data-scroll-anchor="true">
<div class="text-base my-auto mx-auto py-5 [--thread-content-margin:--spacing(4)] @[37rem]:[--thread-content-margin:--spacing(6)] @[72rem]:[--thread-content-margin:--spacing(16)] px-(--thread-content-margin)">
<div class="[--thread-content-max-width:32rem] @[34rem]:[--thread-content-max-width:40rem] @[64rem]:[--thread-content-max-width:48rem] mx-auto flex max-w-(--thread-content-max-width) flex-1 text-base gap-4 md:gap-5 lg:gap-6 group/turn-messages focus-visible:outline-hidden" tabindex="-1">
<div class="group/conversation-turn relative flex w-full min-w-0 flex-col agent-turn">
<div class="relative flex-col gap-1 md:gap-3">
<div class="flex max-w-full flex-col grow">
<div class="min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal [.text-message+&amp;]:mt-5" dir="auto" data-message-author-role="assistant" data-message-id="cbe8af25-1afe-4eda-9986-64a6d594f1a9" data-message-model-slug="gpt-4o">
<div class="flex w-full flex-col gap-1 empty:hidden first:pt-[3px]">
<div class="markdown prose dark:prose-invert w-full break-words light">
<h2 data-start="0" data-end="42">Importing projects from RECIN step by step</h2>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</article>
<div class="pointer-events-none h-px w-px" aria-hidden="true" data-edge="true"></div>
<div></div>
<div>
<article class="text-token-text-primary w-full" dir="auto" data-testid="conversation-turn-16" data-scroll-anchor="true">
<div class="text-base my-auto mx-auto py-5 [--thread-content-margin:--spacing(4)] @[37rem]:[--thread-content-margin:--spacing(6)] @[72rem]:[--thread-content-margin:--spacing(16)] px-(--thread-content-margin)">
<div class="[--thread-content-max-width:32rem] @[34rem]:[--thread-content-max-width:40rem] @[64rem]:[--thread-content-max-width:48rem] mx-auto flex max-w-(--thread-content-max-width) flex-1 text-base gap-4 md:gap-5 lg:gap-6 group/turn-messages focus-visible:outline-hidden" tabindex="-1">
<div class="group/conversation-turn relative flex w-full min-w-0 flex-col agent-turn">
<div class="relative flex-col gap-1 md:gap-3">
<div class="flex max-w-full flex-col grow">
<div class="min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal [.text-message+&amp;]:mt-5" dir="auto" data-message-author-role="assistant" data-message-id="da4a87d1-8f17-4753-b4af-ef6ada36ebb4" data-message-model-slug="gpt-4o">
<div class="flex w-full flex-col gap-1 empty:hidden first:pt-[3px]">
<div class="markdown prose dark:prose-invert w-full break-words light">
<p data-start="0" data-end="106" data-is-last-node="" data-is-only-node="">When selecting that option, a window will open allowing us to choose one of our projects created in RECIN.</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</article>
<div class="pointer-events-none h-px w-px" aria-hidden="true" data-edge="true"></div>
</div>
<h2><img loading="lazy" decoding="async" class="aligncenter wp-image-23697 size-full" src="https://www.cci-es.org/wp-content/uploads/RECIN-3.png" alt="" width="879" height="335" srcset="https://www.cci-es.org/wp-content/uploads/RECIN-3.png 879w, https://www.cci-es.org/wp-content/uploads/RECIN-3-300x114.png 300w, https://www.cci-es.org/wp-content/uploads/RECIN-3-768x293.png 768w" sizes="auto, (max-width: 879px) 100vw, 879px" /></h2>
<h2></h2>
<article class="text-token-text-primary w-full" dir="auto" data-testid="conversation-turn-18" data-scroll-anchor="true">
<div class="text-base my-auto mx-auto py-5 [--thread-content-margin:--spacing(4)] @[37rem]:[--thread-content-margin:--spacing(6)] @[72rem]:[--thread-content-margin:--spacing(16)] px-(--thread-content-margin)">
<div class="[--thread-content-max-width:32rem] @[34rem]:[--thread-content-max-width:40rem] @[64rem]:[--thread-content-max-width:48rem] mx-auto flex max-w-(--thread-content-max-width) flex-1 text-base gap-4 md:gap-5 lg:gap-6 group/turn-messages focus-visible:outline-hidden" tabindex="-1">
<div class="group/conversation-turn relative flex w-full min-w-0 flex-col agent-turn">
<div class="relative flex-col gap-1 md:gap-3">
<div class="flex max-w-full flex-col grow">
<div class="min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal [.text-message+&amp;]:mt-5" dir="auto" data-message-author-role="assistant" data-message-id="9540428d-c215-4969-8f4e-e385bbfa8f82" data-message-model-slug="gpt-4o">
<div class="flex w-full flex-col gap-1 empty:hidden first:pt-[3px]">
<div class="markdown prose dark:prose-invert w-full break-words light">
<h2 data-start="0" data-end="53">Advantages of the integration between ESCIM and RECIN</h2>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</article>
<div>
<div></div>
<div>
<article class="text-token-text-primary w-full" dir="auto" data-testid="conversation-turn-20" data-scroll-anchor="true">
<div class="text-base my-auto mx-auto py-5 [--thread-content-margin:--spacing(4)] @[37rem]:[--thread-content-margin:--spacing(6)] @[72rem]:[--thread-content-margin:--spacing(16)] px-(--thread-content-margin)">
<div class="[--thread-content-max-width:32rem] @[34rem]:[--thread-content-max-width:40rem] @[64rem]:[--thread-content-max-width:48rem] mx-auto flex max-w-(--thread-content-max-width) flex-1 text-base gap-4 md:gap-5 lg:gap-6 group/turn-messages focus-visible:outline-hidden" tabindex="-1">
<div class="group/conversation-turn relative flex w-full min-w-0 flex-col agent-turn">
<div class="relative flex-col gap-1 md:gap-3">
<div class="flex max-w-full flex-col grow">
<div class="min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal [.text-message+&amp;]:mt-5" dir="auto" data-message-author-role="assistant" data-message-id="2aeddc95-6885-40fa-9258-eb453be85499" data-message-model-slug="gpt-4o">
<div class="flex w-full flex-col gap-1 empty:hidden first:pt-[3px]">
<div class="markdown prose dark:prose-invert w-full break-words light">
<p data-start="0" data-end="230" data-is-last-node="" data-is-only-node="">and then, for that specific project, directly select within the zones and conduits we had already designed which ones will be compromised and which ones will be impacted in a very simple way, saving time and avoiding input errors.</p>
</div>
</div>
</div>
</div>
<div class="flex min-h-[46px] justify-start"></div>
</div>
<div class="absolute"></div>
</div>
</div>
</div>
</article>
<div class="pointer-events-none h-px w-px" aria-hidden="true" data-edge="true"><img loading="lazy" decoding="async" class="aligncenter wp-image-23698 size-full" src="https://www.cci-es.org/wp-content/uploads/RECIN-4.png" alt="" width="612" height="953" srcset="https://www.cci-es.org/wp-content/uploads/RECIN-4.png 612w, https://www.cci-es.org/wp-content/uploads/RECIN-4-193x300.png 193w" sizes="auto, (max-width: 612px) 100vw, 612px" /></div>
</div>
</div>
<div></div>
<div></div>
<div></div>
<div></div>
<div>
<div style="text-align: left;">
<p data-start="0" data-end="142">After selecting and clicking the &#8220;Import&#8221; button, all the information including the diagram designed in RECIN will appear in our new scenario.</p>
<p style="text-align: center;" data-start="144" data-end="194" data-is-last-node="" data-is-only-node="">We hope this functionality is useful for everyone!</p>
</div>
</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>600 CCI Weekly Newsletter: A History of Commitment to OT Cybersecurity</title>
		<link>https://www.cci-es.org/en/600-cci-weekly-newsletter-ot-cybersecurity/</link>
		
		<dc:creator><![CDATA[Maite Carli]]></dc:creator>
		<pubDate>Sun, 24 Nov 2024 06:00:30 +0000</pubDate>
				<category><![CDATA[English]]></category>
		<guid isPermaLink="false">https://www.cci-es.org/?p=22200</guid>

					<description><![CDATA[Since 2013, the Industrial Cybersecurity Center (CCI) has worked tirelessly to strengthen cybersecurity in the field of Operational Technologies (OT) and facilitate the work of those with responsibility within industrial organizations. In these more than ten years, we have shared this newsletter with our members weekly, a space that has established itself as a key [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>Since 2013, the Industrial Cybersecurity Center (CCI) has worked tirelessly to strengthen cybersecurity in the field of Operational Technologies (OT) and facilitate the work of those with responsibility within industrial organizations. In these more than ten years, we have shared this newsletter with our members weekly, a space that has established itself as a key resource for continuous updating of knowledge, access to a selection of articles, use cases, best practices and events that address industrial cybersecurity.</p>
<p>The newsletter has incorporated valuable information over time, such as the service catalog, job vacancies, podcasts and other resources for the industrial cybersecurity community.</p>
<p>Today, we proudly celebrate the 600th edition of this newsletter, a milestone that reflects the continued commitment of our organization, and the broad support of a growing community, with more than 8,000 members worldwide.</p>
<h2><strong>A Commitment that Started in 2013</strong></h2>
<p>Industrial cybersecurity is a field that has evolved rapidly due to digitalization in all sectors, especially critical ones such as energy, water, transportation, among many others. Given the importance of risks in the field of OT, the CCI was born in 2013, a pioneering initiative in the Spanish-speaking world that set out to improve the state of industrial cybersecurity. Since its inception, the newsletter has been a key communication channel for sharing threat analysis, best practices, regulatory updates, and other content relevant to our members.</p>
<h2><strong>What&#8217;s Behind 600 Newsletters?</strong></h2>
<p>Every week, the CCI team analyzes high-quality content to offer a global vision of the challenges and opportunities in the field of OT security, both nationally and internationally. In these 600 newsletters, we have covered everything from the most technical to the strategic, with articles on new technologies, trend reports and case studies that illustrate how to address cyber threats in complex industrial environments. We strive weekly to offer information that is not only relevant, but also useful for OT professionals, cybersecurity specialists, and all those interested in protecting critical and industrial infrastructure. From CCI&#8217;s own articles, as well as external ones, and those resources in which the CCI works, including the wide range of training in Industrial Cybersecurity offered by the Professional School.</p>
<p><img loading="lazy" decoding="async" class="wp-image-22201 size-full aligncenter" src="https://www.cci-es.org/wp-content/uploads/V.2_ENG_600_CABECERA-BOLETIN.png" alt="" width="700" height="230" srcset="https://www.cci-es.org/wp-content/uploads/V.2_ENG_600_CABECERA-BOLETIN.png 700w, https://www.cci-es.org/wp-content/uploads/V.2_ENG_600_CABECERA-BOLETIN-300x99.png 300w" sizes="auto, (max-width: 700px) 100vw, 700px" /></p>
<h3><strong>Networking Spaces and Knowledge Communities</strong></h3>
<p>One of the pillars of our work is to build spaces where professionals can exchange knowledge and experiences. Throughout these years, we have organized events, exchange panels, specific meetings and webinars in which top-level experts, industry representatives and academics have participated. Our weekly newsletter is also a tool that facilitates connection between community members, allowing them to access these networking opportunities and strengthening ties between professionals and organizations.</p>
<h3><strong>What this milestone means for the Community </strong></h3>
<p>Bulletin number 600 is not only a milestone in terms of longevity, but also a reflection of the commitment of the industrial cybersecurity community to continue learning, innovating and collaborating, and for this reason we want to thank readers for their support on this path, being a pillar fundamental in the construction of this shared knowledge space.</p>
<p>We also want to thank our sponsors, members, collaborators, and the CCI team who have made it possible to reach this milestone. The journey towards continuous improvement of industrial cybersecurity does not end here, our commitment continues to be to provide a knowledge space that keeps the community informed and prepared for the challenges of a constantly changing environment.</p>
<p style="text-align: center;"><em><strong>¡Thank you!</strong></em></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>CCI Events Calendar 2025</title>
		<link>https://www.cci-es.org/en/cci-events-calendar-2025/</link>
		
		<dc:creator><![CDATA[Maite Carli]]></dc:creator>
		<pubDate>Thu, 14 Nov 2024 11:21:28 +0000</pubDate>
				<category><![CDATA[English]]></category>
		<guid isPermaLink="false">https://www.cci-es.org/?p=22130</guid>

					<description><![CDATA[The new year 2025 is full of events, appointments and meetings focused on Industrial Cybersecurity. At CCI we have designed a complete new calendar to work with the ecosystem, generate networking and strengthen synergies in the regions and countries where cybersecurity is already a prevailing priority. Our goal is to continue adding to the environment, generating [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>The new year 2025 is full of events, appointments and meetings focused on<strong> Industrial Cybersecurit</strong>y. At CCI we have designed a complete new calendar to work with the ecosystem, generate networking and strengthen synergies in the regions and countries where cybersecurity is already a prevailing priority. Our goal is to continue adding to the environment, generating synergies and creating meeting points between professionals in the sector.</p>
<p>We will travel through part of the national and international geography with interesting meetings in which we invite you to participate and continue adding to the community. <strong>Join each of the events as a member of the CCI ecosystem</strong> – Discover the available <a href="https://www.cci-es.org/en/join-for-free/">memberships and become a member</a>.</p>
<p><img loading="lazy" decoding="async" class="wp-image-22131 size-full aligncenter" src="https://www.cci-es.org/wp-content/uploads/Info-Events-CCI-2025-ENG.png" alt="" width="662" height="942" srcset="https://www.cci-es.org/wp-content/uploads/Info-Events-CCI-2025-ENG.png 662w, https://www.cci-es.org/wp-content/uploads/Info-Events-CCI-2025-ENG-211x300.png 211w" sizes="auto, (max-width: 662px) 100vw, 662px" /></p>
<p>&nbsp;</p>
<p><a href="https://www.cci-es.org/en/events/"><img loading="lazy" decoding="async" class="alignnone size-medium wp-image-22282 aligncenter" src="https://www.cci-es.org/wp-content/uploads/ING_VENTOS-BOTON-300x59.png" alt="See all CCI 2025 events" width="300" height="59" srcset="https://www.cci-es.org/wp-content/uploads/ING_VENTOS-BOTON-300x59.png 300w, https://www.cci-es.org/wp-content/uploads/ING_VENTOS-BOTON.png 700w" sizes="auto, (max-width: 300px) 100vw, 300px" /></a></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>IACS Responsible &#8211; Cybersecurity Leader</title>
		<link>https://www.cci-es.org/en/iacs-responsible-cybersecurity-leader/</link>
		
		<dc:creator><![CDATA[Maite Carli]]></dc:creator>
		<pubDate>Tue, 05 Nov 2024 11:42:27 +0000</pubDate>
				<category><![CDATA[English]]></category>
		<guid isPermaLink="false">https://www.cci-es.org/?p=22067</guid>

					<description><![CDATA[The IACS manager or cybersecurity leader for industrial environments plays a key role in their protection and subsequently in the prevention and management of cyber incidents that affect them. And there is no doubt about the importance of the cybersecurity manager in industrial environments, and that it is a key role in these times for [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><strong>The IACS manager or cybersecurity leader</strong> for industrial environments plays a key role in their protection and subsequently in the prevention and management of cyber incidents that affect them. And there is no doubt about the importance of the cybersecurity manager in industrial environments, and that it is a key role in these times for their protection as well as in the prevention and management of cyber incidents, but sometimes Doubts do arise about what the person in this position should do or what challenges they will have to face.</p>
<h2>What are the tasks of an IACS manager?</h2>
<p>The cybersecurity leader for industrial automation and control systems is <strong>responsible for safeguarding these systems</strong>. Their job consists of <strong>designing, implementing and maintaining security policies</strong> <strong>and procedures</strong> to ensure protection against cyber threats. Additionally, they are responsible for assessing risks, monitoring systems and networks, responding to incidents and promoting cybersecurity awareness [1].</p>
<p>It is also responsible for <strong>security incident management</strong>, which involves the <strong>identification, analysis and response to security incidents</strong> that may affect control and automation systems. Additionally, you must stay abreast of the latest trends and threats in industrial cybersecurity to ensure that control and automation systems are protected against the latest threats.</p>
<p><img loading="lazy" decoding="async" class="wp-image-22068 size-full aligncenter" src="https://www.cci-es.org/wp-content/uploads/C02-ENG.png" alt="" width="1400" height="425" srcset="https://www.cci-es.org/wp-content/uploads/C02-ENG.png 1400w, https://www.cci-es.org/wp-content/uploads/C02-ENG-300x91.png 300w, https://www.cci-es.org/wp-content/uploads/C02-ENG-1024x311.png 1024w, https://www.cci-es.org/wp-content/uploads/C02-ENG-768x233.png 768w" sizes="auto, (max-width: 1400px) 100vw, 1400px" /></p>
<h2><strong>What are your main challenges?</strong></h2>
<p>The Cybersecurity Manager &#8211; IACS in an industrial environment has a multifaceted role. Within the life cycle of the management system that the Cybersecurity Manager governs, some of the following challenges arise:</p>
<h3>Know and understand the industrial environment:</h3>
<p>In an industrial environment, the complexity with respect to the technology to operate and maintain the production process or service delivery is extremely high. With non-standard communication protocols, legacy technology and modern systems coexisting, the Cybersecurity Manager must understand their operation in detail and maintain an updated inventory of the assets that must be protected. Additionally, you must take into account that cyber attacks can come from both internal and external sources.</p>
<h3>Risk assessment and management:</h3>
<p>A key aspect of the Cybersecurity Manager&#8217;s job is to identify and assess potential cyber risks in the industrial environment. This involves performing vulnerability analysis, penetration testing, and risk assessments to understand existing weaknesses and take appropriate preventive measures. You must also collaborate with other departments to ensure that effective measures are implemented at all levels. And that its selection is hand in hand with the risk appetite that the owner of the process has determined for each asset.</p>
<h3>Implementation of policies and security measures:</h3>
<p>They develop policies and procedures to ensure the security of industrial control systems. They implement firewalls, intrusion detection systems, and access controls to protect the internal network against external threats and monitor activity for abnormal behavior [2].<br />
They also maintain close collaboration with the engineering, operations and maintenance teams, to ensure that security best practices are followed from the beginning.</p>
<h3>Monitoring and incident response:</h3>
<p>Despite preventive measures, security incidents can occur. The Cybersecurity Manager must be prepared to respond quickly to these situations, investigate the root causes and minimize the impact. This involves maintaining a well-trained incident response team, establishing disaster recovery plans, and coordinating with relevant authorities in the event of serious security breaches[3].<br />
Industrial control environments continue to be a target for cybercriminals, and 93% of operational technology (OT) organizations have experienced an intrusion in the last 12 months[4]. This means that cybersecurity leaders in industrial environments must be prepared to deal with continued cyber intrusions and attacks.</p>
<h3>Cybersecurity Awareness:</h3>
<p>Education and awareness are critical to strengthening cybersecurity posture in an industrial environment. The Head of Cybersecurity must carry out training and awareness programs for staff, highlighting risks, best security practices and preventive measures. This will foster a strong security culture and help prevent human error and social engineering attacks[5].</p>
<h3>Cybersecurity Talent Gap:</h3>
<p>The cybersecurity talent gap is another challenge facing industrial environment protection leaders[6]. As demand for cybersecurity professionals increases, organizations may struggle to find and retain talent.</p>
<h3>Integration of OT and IT systems:</h3>
<p>Integrating OT and IT systems is another challenge facing cybersecurity leaders in industrial environments[7]. As OT systems integrate with IT and corporate networks, organizations&#8217; attack surface increases significantly, which can make it difficult to protect control and automation systems from cyber threats.</p>
<h2><strong>Conclusions about the person responsible for IACS</strong></h2>
<p>The role of the Cybersecurity Manager in an industrial environment (IACS manager) is <strong>essential to ensure the protection of critical infrastructure against cyber threats</strong>. Their experience in risk assessment, security policy implementation, system monitoring and incident response is essential to safeguarding industrial processes. As digitalization and interconnection continue to transform industrial environments, the role of the Cybersecurity Manager becomes even more crucial. With <strong>proper measures and a proactive mindset</strong>, we can build an industrial environment that is secure and resilient to the cyber threats of the future.</p>
<p>To know in detail the tasks and obligations of an IACS manager, it is best to complete specific training for this purpose. <a href="https://www.cci-es.org/c02-curso-responsable-ciberseguridad-iacs/">The C02 &#8211; Course responsible for cybersecurity at IACS coordinated by ISA &#8211; Spain &#8211; CCI</a> is totally focused on providing students with all the theoretical and practical knowledge necessary to perform this highly demanded professional role. <strong><a href="https://www.cci-es.org/c02-curso-responsable-ciberseguridad-iacs/">Discover now the next call that we will hold for this course</a></strong>.</p>
<h3><strong>References:</strong></h3>
<p>[1] A. Genge, &#8220;Roles and responsibilities of a Chief Information Security Officer (CISO),&#8221; Conference on Human Factors in Computing Systems &#8211; Extended Abstracts, 2016.<br />
[2] J. Fraser and S. K. Lowe, &#8220;Industrial Network Security: Securing Critical Infrastructure Networks for Smart Grid, SCADA, and Other Industrial Control Systems,&#8221; Syngress, 2014.<br />
[3] NIST Special Publication 800-82, &#8220;Guide to Industrial Control Systems (ICS) Security,&#8221; U.S. Department of Commerce, National Institute of Standards and Technology, 2015.<br />
[4] Security challenges facing your infrastructure&#8230; <a href="https://www.iproup.com/innovacion/33262-desafios-de-seguridad-que-enfrenta-infraestructura-de-tu-empresa" target="_blank" rel="noopener nofollow">https://www.iproup.com/innovacion/33262-desafios-de-seguridad-que-enfrenta-infraestructura-de-tu-empresa</a><br />
[5] K. J. Shin, S. H. Yang and J. H. Park, &#8220;Empirical Study on Factors Affecting Individual Employees&#8217; Information Security Awareness,&#8221; 2008 Fourth International Conference on Networked Computing and Advanced Information Management, Gyeongju, 2008, pp. 32-37.<br />
[6] Main trends in digital agreements and &#8230; <a href="https://www.onespan.com/es/blog/digital-agreement-cybersecurity-trends-2023" target="_blank" rel="noopener nofollow">https://www.onespan.com/es/blog/digital-agreement-cybersecurity-trends-2023</a><br />
[7] Industrial cybersecurity: what is it and how to implement it? <a href="https://www.ikusi.com/mx/blog/ciberseguridad-industrial-que-es-y-como-implementarla/" target="_blank" rel="noopener nofollow">https://www.ikusi.com/mx/blog/ciberseguridad-industrial-que-es-y-como-implementarla/</a></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
