In the beginning, there was no IT department, no architecture, and no security model. There were just machines doing a job — computers running locally, controlling equipment, completely isolated because they had to be.

Then came networks, then came the internet, hen manufacturing, facilities, and operations were digitized step by step.

Over time, systems were connected for convenience, visibility, and remote access. What had once been isolated environments slowly turned into one large, flat network, where office IT, production systems, building automation, sensors, and embedded devices all lived side by side.

It worked — until it didn’t.

The Dangerous State Many Organizations Are in Today

This historical evolution explains why many organizations now find themselves in a risky position:

• Legacy OT systems connected directly to corporate networks 
• IoT devices sharing infrastructure with critical systems 
• Minimal segmentation and unclear trust boundaries 
• Little separation between users, systems, and operations 

This was rarely the result of bad decisions. It was the result of incremental change without an overarching architecture.

Now, security teams are asked to “secure IT/OT/IoT”, but what they are really facing is the task of re‑architecting something that grew organically for decades.

Why the Journey Feels Overwhelming

Moving from a flat, historically grown environment to a structured IT/OT/IoT architecture can feel overwhelming — especially when:

• Production cannot be stopped 
• Legacy systems cannot be replaced 
• Documentation is incomplete or outdated 
• Ownership is spread across multiple teams and vendors 

This is not about flipping a switch or deploying a product. It’s about introducing structure, segmentation, and trust boundaries into an environment that was never designed for it. 

That is why architecture, pragmatism, and an understanding of operational reality are so critical when securing these environments. 

A Changed Threat Landscape 

Traditional IT security models were built around systems where confidentiality was the primary concern. In OT and IoT environments, availability and safety are often even more critical. Downtime can stop production, disrupt logistics, or in some cases, put people at risk.

At the same time, many OT and IoT systems were never designed to be exposed:

• Legacy devices with long lifecycles remain in use
• Proprietary or outdated protocols lack basic security controls
• Patching and scanning are often limited or impossible
• Ownership is spread across IT, operations, facilities, and external vendors

Attackers are well aware of this. OT and IoT environments are increasingly targeted — not only to disrupt operations, but also as entry points into broader enterprise networks.

Why “Just Apply IT Security” Doesn’t Work

A common mistake is assuming that IT security controls can simply be copied into OT and IoT environments. In reality, this often leads to operational issues, blocked processes, or a false sense of security.

Securing these environments requires a different mindset:

• Architecture before tools — design trust boundaries and communication paths first
• Segmentation by design, not flat networks with exceptions
• Controlled access for both users and systems
• Visibility and monitoring that does not interfere with operations
• Compensating controls where modern security features are not available

Most importantly, security must be adapted to how the environment actually works — not how we wish it worked.

From Frameworks to Real-World Design

Standards and frameworks provide valuable guidance, but they do not automatically translate into working solutions. Every environment has constraints: legacy systems, business requirements, vendor dependencies, and operational realities.

In practice, successful IT/OT/IoT security is about:

• Reducing risk step by step
• Accepting that not everything can be fixed immediately
• Designing security that can evolve over time
• Ensuring close collaboration between IT, security, and operations

This pragmatic approach is often the difference between a secure design that works — and one that looks good on paper but fails in production.

Learn More — Online and in Person

These topics are explored in depth in a longer, hands-on article that walks through real-world architecture patterns, common pitfalls, and practical design principles for securing converged environments.

For the full deep dive, read: Building a Secure IT/OT/IoT Infrastructure in the Real World (Deploymentbunny.com)

If you prefer an interactive format, these challenges and solutions will also be discussed during an upcoming conference session focused on IT/OT security in practice, where real-world experiences and lessons learned will be shared:

Event information: OT Security Day (Scanautomatic.se)