In partnership with

Disclaimer: All views presented here, in this newsletter, are my own.

Author or the newsletter are not liable for any actions taken by any individual or any organization / business / entity. The information provided is for education and awareness purposes only and is not specific to any business and or situation.

M. Yousuf Faisal

Hey there,

Hope you are doing well.

This is Part 4 of “The Digital Factory” series.

In case you’ve missed first three parts, check them out below:

  • Part 1 - The Digital Factory (4.0) - Hub & Spoke - we covered what is industry 3.0, industry 4.0, digital factory and UNS concepts. Concluded that these new approaches, challenges the status quo for industry 3.0 and generates a debate around the “questionable” use of Purdue model for network segmentation - whether its dead or alive, reference network architectures and why Security folks are in a fist fight most of the time with solution architects and or automation professionals.

  • Part 2 - The Digital Factory (4.0) - Data Flow - we covered industrial DataOps, industry 4.0 data flow lifecycle, DataOps and security considerations. <data flow * and tie it together add comments>.

  • Part 3 - The Digital Factory (4.0) - Architecture - we covered different reference models, IT/OT event driven architecture, UNS and more.

In this Part 4 - The Digital Factory (4.0) - Industry Debates, we’ll be covering some famous industry debates that we all should be familiar with (Cyber leaders, CISOs/CTOs, practitioners and most importantly newbies):

  • 🧑‍🎓 IT & OT Convergence - is it converging or not? Yes or No?

  • 🧑‍🎓 Purdue Model - is it dead or alive? Yes or No?

  • ↪️ on a decade old position by Gartner - The Death of Purdue Model.

  • 📲 Digital Transformation - Project or Strategy? (& failures).

  • ↪️ MQTT vs. OPC UA - Industry 4.0 protocol winner?

  • ✍️ And many more…

Am excited, are you Ready?

If so, let’s dig in.

Happy Holidays and Seasons greetings.

Hope you had or having good holidays with family and friends.

Yours truly.

— Yousuf.

Together with:

The Tech newsletter for Engineers who want to stay ahead

Tech moves fast, but you're still playing catch-up?

That's exactly why 100K+ engineers working at Google, Meta, and Apple read The Code twice a week.

Here's what you get:

  • Curated tech news that shapes your career - Filtered from thousands of sources so you know what's coming 6 months early.

  • Practical resources you can use immediately - Real tutorials and tools that solve actual engineering problems.

  • Research papers and insights decoded - We break down complex tech so you understand what matters.

All delivered twice a week in just 2 short emails.

But before we begin, do me a favour and make sure you hit the “Subscribe” button to let me know that you care or liked and keep me motivated to publish more. Thanks!

Drop in your best email address to subscribe and continue reading the rest of the newsletter edition for free.

Industry Debate and Updates

Here’s a list of few classical debates in the world of OT or ICS security.

🧑🎓 The Great IT/OT Convergence Debate: Is It Really Happening?

The burning questions every industrial cybersecurity professional comes across and debates - IT and OT Convergence!

Some definitions first:

Convergence Definition - refers to the act or condition of coming together or moving toward a common point. It can apply to various contexts, including:

General Meaning Coming Together: The merging of two or more things, ideas, or interests into a similar state or point.

Technological Convergence: The integration of different technologies, such as combining data processing and telecommunications into a single system.

Integration Definition - refers to the process of combining two or more elements to create a unified whole. This concept can be applied in various contexts, including social, mathematical, and business environments.

Business Integration Definition: The process of combining different systems, applications, or technologies to work together seamlessly.

Now what we have is:

Some experts despise the term IT/OT convergence.

Some experts call it - IT & OT can never converge! (naysayers on convergence)

Some experts call it - IT & OT is converging!

Some experts call it - IT & OT have converged already!

Some experts are calling it - IT & OT integration (naysayers on convergence)

For many and for most, I call it - its confusing ;-p

I am not an expert 😉 - so no pun intended.

But what I believe is; all this mean different things for people from different backgrounds and perspectives.

For marketing → its just a buzz word - just say IT/OT convergence - SEO ranking etc.

For OT folks (in some context of a - cave man) → no it can never be.

For IT folks (in most context) → convergence / integration means the same things.

If we look at it from historical perspective we find:

In around 1990s for industrial control systems - TCP/IP won the protocols war after a lot of industry resistance.

Ethernet and windows were introduced in ICS and benefits outweighed the resistance and concerns, leading to industry wide adaption.

So in that essence → IT technology penetrated into ICS systems, so convergence already started almost two decades ago.

If we look at it from ICS experts perspective we find opinions like - it could and should never converge - linguistically - meaning controls required for physical process.

If we look at it from industry standards perspective we find set of standards like - ISA 95 / IEC/ISA 62264-x that is specifically trying to address the need for integration between business processes (i.e. IT) to manufacturing processes (i.e. OT).

In the early 90s, there was significant interest in integrating business and manufacturing systems.

The goal was to use real-time manufacturing data to improve business decision-making.

However, integrating these systems proved challenging due to their fundamental differences, including varying terminologies, cultures, and timeframes, such as the millisecond response times required by control systems.

IT focuses on data—storage, integrity, business systems. IT prioritizes security and rapid updates.

— while OT demands uptime and stability. OT deals with real-time control, uptime, and physical processes. Their priorities and protocols couldn’t be more different.

These conflicting priorities create organizational friction that technology alone can't solve.

All we’ve been seeing now is more and more adaption of IT type technology solutions into ICS / OT environment (e.g. virtualization, cloud adaption, MQTT, IIOT, PKI / certificates etc.).

Bottom Line: Convergence is happening rapidly, but success requires addressing the people problem first, not just the technology integration.

It’s driven by digital transformation, remote operations, and efficiency demands.

McKinsey calls IT/OT convergence a key enabler of scaling digital factory operations.

Legacy companies worry and for good reasons — and with good reason — but many see this as a push toward modernization, not a retreat.

The Verdict: YES - But It's Messier Than Expected

The convergence is definitely happening, but it's not the smooth integration many predicted.

Why It's Still Struggling:
The biggest barrier isn't technical—it's cultural.

Ask your team: Are we mindfully converging IT and OT — with security baked in —or stumbling toward it by chance?

Here’s an interesting set of conversations on IT/OT Convergence at S4 conference:

So what position you’ll take?

📲Digital Transformation - a Project or a Strategy?

“Digital transformation isn’t a project / an app. It’s a strategy—and often, a trap.”

When Digital Transformation becomes “just a project,” momentum falters.

Most failures are rooted in poor alignment and approach — not the tech.

The $2.3 Trillion Failure Epidemic - The Shocking Statistics

  • 70-90% of digital transformation projects fail

  • Only 30-35% achieve their intended goals

  • $2.3 trillion wasted globally on unsuccessful programs

  • Manufacturing success rates: 26% (high-tech) to 4-11% (traditional industries)

Digital transformation often gets boiled down to flashy tools—IoT dashboards, cloud, AI.

But real transformation is organizational. Clear strategy, culture change, leadership buy-in—those are the hard parts.

Why it Fails (The Truth):

  1. No Clear Strategy - Adopting technology for technology's sake

  2. Assuming it's an IT task - Missing the organizational change component

  3. Employee Resistance - Forcing change without buy-in or training

  4. Unrealistic Expectations - Believing benefits appear within months

  5. Wrong architecture - choosing a solutions driven architecture, instead of technology driven. Vendor lock ins and interoperability issues. More on this below in event driven architecture section.

The Success Formula:

  • Start with business outcomes, not technology

  • Invest heavily in change management (7x more likely to succeed)

  • Create cross-functional teams, not IT-only initiatives

  • Focus on people, process, then platform.

  • Choose an open and technology driven architecture that is future ready.

Email your executive team:

Digital transformation is a strategy - not a project.

“Let’s shift from Digital Transformation as a tech project to a business-holistic initiative.” Propose forming a cross-functional committee.

Here’s a 20 mins Masterclass on IT/OT Digital Transformation and Cybersecurity Strategy.

So what position you’ll take?

🧑🎓Purdue Model – Dead or Alive? for Security?

Over the years, there’s been a great amount of debates and discussions around this topic.

Is The Purdue Model Dead? - Joel Langill and Brad Hegrat join Dale Peterson to answer this question at an S4 event back in 2019.

Brad Hegrat declared it “essentially dead—convergence killed it.”

Opponents like Joel Langill defended its value, saying it still helps us see architectural layers—and why they exist.

Mr. Langill acknowledged that while “the architecture, from a network perspective, is probably dead,” the model was among the first to show “how these pieces are supposed to be layered and interoperate,” and “if we lose sight of that, we’re going to lose sight of why we created hierarchy in the first place.”

Langill contended that while the model was never conceived as a security reference architecture, it nonetheless incorporates some risk ideas that help security practitioners understand how information flows organizationally and thereby helps identify and address potential attack vectors.

The "Dead" Camp Says:

  • IIoT devices bypass traditional hierarchies (Level 0 sensors connect directly to cloud)

  • Rigid layers can't handle modern dynamic architectures

  • Cloud integration breaks traditional segmentation

The "Alive" Camp Argues:

  • Forbes 2022: "The Purdue Model is dead. Long live the Purdue Model"

  • SANS Institute maintains it's still essential for network segmentation

  • YouTube debates show practitioners adapting, not abandoning it.

Death of Purdue Model  - Gartner position (2023)

But what you might not be aware of that, back in 2023 Gartner changed its more than a decades old position on the Purdue as the reference Model and called it Death of Purdue Model.

Paul DeBeasi published a paper on 31st July 2023 – Reference Architecture for Integrating OT and Modern IT.

Where he declared that Purdue is obsolete (a significant change in Gartner’s decades old position) and this represents the next step in the evolution from the hierarchical Purdue Model toward a distributed, interconnected model.

Note that this was beside the fact that Purdue was never published as a reference architecture to be used for security.

Security was not mentioned in any where of the said publication.

The Majority Verdict: ALIVE - But on Life Support Requiring Major Surgery

Despite Gartner's earlier pronouncements, the Purdue Model isn't dead — it's evolving rapidly.

The Reality: It's not about killing the Purdue Model—it's about layering Zero Trust principles on top of its segmentation framework. The model provides structure; modern security adds intelligence.

Stop debating death. Start planning evolution.

“'The Death of the Purdue Model'—or is it just evolving into something better?”

Today, many cybersecurity leaders echo a balanced view: the model’s pure hierarchical structure may not fit modern, flat, cloud-integrated networks—but its segmentation principles still matter. SANS calls it a useful conceptual tool. See SANS position - here.

Claroty agrees: it's a solid foundation for newcomers or flat networks—but needs adaptation in modern architectures here → Beyond the Purdue Model: ICS Security in Modern, Complex Network Architectures.

Zscalar also points some views → What Is the Purdue Model for ICS Security?

Challenge your planners: Are we clinging to an outdated hierarchy — or reimagining the Purdue Model to fit our digital reality?

The Claim - Purdue Model for Segmentation/Security - Really?

Here are few must watch videos that breaks it down:

Which view you are inclined to and why? post in comments below.

✍️IT & OT Event Driven Network Architecture vs. Solutions driven 

📘Many solution architects / System Integrators and other stakeholders that design and implement OT/ICS solutions

Gartner's Stance: EDA is Fundamental for Digital Business

Gartner has been bullish on Event-Driven Architecture since 2018:

  • EDA underpins hyper automation and multi experience trends

  • 82% of IT leaders plan EDA adoption for 2-3 new use cases within 24 months

  • Four core technologies needed: Event broker, Event portal, Event store, Stream Analytics

The Expert Reality Check:

  • Limited tools and skills remain major barriers

  • Manufacturing leads adoption due to real-time operational needs

  • Success requires moving beyond RESTful thinking to event-native approaches

For IT/OT: EDA becomes critical as operational events (machine failures, production changes) need real-time propagation across enterprise systems.

“Event-driven? More than a buzzword — it’s how real-time IT and OT talk.”

Event-driven architectures enable seamless, responsive communication across IT and OT layers.

Experts advocate them for real-time insights, predictive maintenance, and responsive automation — but they add new cybersecurity demands.

Think sensors triggering operations automatically, dashboards updating live, analytics acting instantly. That’s the power—but also a complex attack surface.

Call to action:
Plan an “event-driven proof of concept.”

Map real events—say a sensor threshold—and track the full event chain end-to-end. Highlight security gaps.

Let’s show stakeholders both promise and risk in action.

Based on Gartner’s 2023 paper Reference Architecture for Integrating OT and Modern IT (31st July 2023 by Paul DeBeasi) here are some:

Key Findings:

  • A new industrial IT-OT architecture is emerging to improve data accessibility and reduce asset vulnerability.

  • It will be build upon event-centric integration pattern that will use MQTT brokers, the Sparkplug B standard and a Unified Namespace (UNS) design strategy.

  • It will also use OT asset discovery and protection platforms.

and Recommendations:

  • Modernize industrial edge architecture by transitioning from a Purdue Model toward an event centric integration pattern.

  • Use cyber-physical security protection platform (CPS-PP) to discover OT assets before defining your namespace data hierarchy.

  • Use the same CPS-PP to protect your OT assets and to integrate with IT security tools such as SIEM.

So what position you’ll take?

MQTT vs OPC UA - Leader for Industry 4.0?

There are many debates on social you may have encounter around which of these two leading protocols for broker services is a better choice when it comes to digitally transformation your manufacturing environment to an industry 4.0 or above.

There are die hard fans for both out there. That’ll convince you to choose one over other.

MQTT - its open architecture, light weight, supports report by exception updates, and push/pull or publish or subscribe model and requires less poking holes in the firewall policies.

OPC UA - on the other hand, is protocol, but its not light weight, does not support report by exception updates, is client/server architecture, requires specific firewall policies.

For a slightly more specific comparison checkout - OPC UA vs. MQTT (a comparison of the most important features) by i-flow.

“Stop fighting the MQTT vs OPC UA war. It’s a trap.

Real architecture demands both. OPC UA for machines and MQTT for IIOT/ cloud.

You need both to build a scalable IIOT/Unified Namespace architecture.

In summary, we should know that they both have their specific advantageous places in digital transformation to an event based / UNS / IIOT / 4.0 architecture for specific implementation.

So what position you’ll take?

Together with:

Turn AI Into Your Income Stream

The AI economy is booming, and smart entrepreneurs are already profiting. Subscribe to Mindstream and get instant access to 200+ proven strategies to monetize AI tools like ChatGPT, Midjourney, and more. From content creation to automation services, discover actionable ways to build your AI-powered income. No coding required, just practical strategies that work.

What other debates you often hear about in OT?

Here are some topics in OT, that are often discussed, debated and you find contradictory opinions between professionals / experts.

  • Is it ICS, IACS, OT or CPS? How do you define correct terms?

  • Firewall vs data diode - which one is better?

  • Active vs passive scanning in OT?

  • Common or independent SOC for IT and OT?

  • Common or Separate Active Directory for IT and OT?

  • Secure-by-Design vs Secure-by-Default

  • Integrated SIS and BPCS or isolated ?

  • Should DCS be able to write to SIS?

  • Encrypt ICS traffic (level 0/1) or not?

  • Self-signed or CA certs for OT?

  • SBOM or CSAF?

  • SBOM responsibility - product manufacturer or asset owner?

  • Which is true: 100s of ICS Security incidents vs handful?

Let me know by hitting reply if you’d like me to cover some of these in future Digital factory editions.

Conclusion

The goal and or idea behind this edition is to not to convince you to make a specific opinion but rather to understand arguments from both camps, consult with experts, explore and understand the concepts behind and draw your own conclusions.

The fact that these debates exits and for a good reason.

CISO’s role in OT Cybersecurity

More and or more IT CISO’s in industrial environments are also given the task to do something about OT Security or these environments appoints dedicated OT CISOs or OT security leads.

- both needs to be on top of these differing opinions and reasoning.

Overall in 2025, CISOs / CXOs have taken on a more strategic role in OT cybersecurity decision-making.

I’d love to know what opinion / positions you’d take based on:

  • your Industrial environment → if working as an asset owner.

  • OR your Industrial customers environments→ If you are consultant / vendor / solutions provider.

If you’d like to learn more on this head to:

IT-OT CySEAT Training & join the wait-list soon, before its too late.

My Recent Most Viewed Social Posts:

In case you’ve missed - here are some of my recent most viewed social posts.

Ways in which I can help?

Whenever you are ready - I can help you with:

A - IT & OT Cybersecurity Advisory / Consulting services - for securing your business and or its digital transformation journey.

B - Security Awareness Training & Phishing Awareness Portal - Train your staff and build a Security awareness program through our subscription based service.

C - Securing Things Academy (STA) - Security trainings for IT & OT practitioners.

Visit the newsletter website for Links to above services and or reach out at info[at]securingthings[dot]com or DM me via LinkedIn.

D - Securing Things Newsletter - Sponsor this newsletter to showcase your brand globally, or subscribe to simply Get Smarter at Securing Things.

Reach out at newsletter[at]securingthings[dot]com or DM me via LinkedIn.

✉️ Wrapping Up

Have questions, comments, or feedback? Just reply directly, I’d love to hear from you.

Also, if you find this or previous newsletter edition(s) useful and know other people who would too, I'd really appreciate if you'd forward it to them. Thanks a ton.

Thanks for reading - until the next edition!

It’s a Great Day to Start Securing Things for a Smart & Safer Society.

Take care and Best Regards,

Follow Securing Things on LinkedIn | X/Twitter & YouTube.

Rate the newsletter content

Did you find the content valuable?

Login or Subscribe to participate

If you are reading this online don’t forget to register; validate your email, and request a login link to submit the poll.

Your feedback and input is invaluable to me as we work together to strengthen our cybersecurity defenses and create a safer and smarter digital society. Thank you for your trust and continued support.

Reply

Avatar

or to participate

Keep Reading