Broadcast and IT Converged. What Happened to the Wall Between Them?

In 2012, the question was how much separation broadcast systems needed from corporate IT. Fourteen years later, broadcast itself runs increasingly on IT infrastructure.

Originally published October 2012. Updated October 2026 to reflect the evolution of broadcast and enterprise IT infrastructure.

When I first wrote about this in 2012, there was a very real tension between broadcast engineering and corporate IT.

I had experienced it firsthand.

Broadcast equipment was becoming increasingly networked, while corporate IT departments were responsible for protecting and standardizing the technology environment across the organization.

Those objectives didn’t always align.

From the broadcast side, the concern was straightforward: systems responsible for getting a program on the air couldn’t be treated like ordinary corporate computers.

Corporate antivirus software, administrative policies, network changes or security measures that were perfectly reasonable elsewhere in the organization could potentially interfere with a broadcast operation.

From the IT side, allowing another technology environment to operate beyond normal corporate controls created its own legitimate concerns.

Security was becoming more important. Content creators needed internet access. Files moved between systems. Portable storage devices crossed boundaries.

The debate wasn’t really about whether security mattered.

It was about how to protect the enterprise without creating another risk inside the broadcast operation.

We Kept the Networks Apart for a Reason

One answer at the time was separation.

Broadcast infrastructure could operate on networks designed specifically around the reliability and performance requirements of production, while the corporate network handled conventional business applications.

That isolation helped protect critical broadcast systems from problems originating elsewhere in the enterprise.

But even in 2012, it was obvious that complete separation wasn’t going to be a permanent answer.

Video was moving across networks. Broadcast equipment was becoming increasingly dependent on IT technology. The two groups needed access to some of the same systems and information.

I ended the original article with a fairly simple conclusion:

“Convergence is here to stay.”

Fourteen years later, convergence isn’t the prediction anymore.

It’s the operating environment.

Broadcast Became an IP Business

The technological change since then has been substantial.

Modern professional media infrastructure increasingly uses IP networks to transport video, audio and data. Standards such as SMPTE ST 2110 were specifically developed to support real-time professional media over managed IP networks.

That changes the old broadcast-versus-IT discussion.

A modern broadcast facility can use common IP infrastructure rather than requiring entirely separate switching technologies for traditional broadcast signals and conventional data. Software-based production, virtualization and cloud workflows push that convergence even further.

The wall between broadcast engineering and information technology hasn’t simply gotten lower.

In many areas, the distinction itself has become difficult to draw.

But that doesn’t mean everything should be connected indiscriminately.

Convergence Didn’t Eliminate the Risk

This may be the most interesting part of looking back at the original discussion.

The technology changed.
The underlying operational concern didn’t.

Today’s IP-based broadcast environments can still require segmentation, traffic prioritization, controlled access and security measures specifically designed around real-time production.

The reason is familiar.

A security control that protects the corporate environment but introduces unacceptable latency or interferes with a live media stream hasn’t solved the entire problem.

At the same time, putting critical production systems onto IP infrastructure creates cybersecurity exposures that traditional broadcast systems didn’t face in quite the same way.

So the old question—

Should broadcast and corporate IT be separate?

—has evolved into a more useful one:

How should a converged technology environment be designed and governed so that one part of the organization doesn’t compromise another?

The Organizational Line Moved Too

In 2012, Broadcast Engineering and Corporate IT could still be treated as distinct technology organizations with an interface between them.

That distinction is much harder to make today.

When production systems run on IP networks and increasingly depend on software, storage, cybersecurity and enterprise infrastructure, responsibility can cross traditional departmental lines.

The important question isn’t whether Broadcast and IT collaborate.

It’s who has authority—and accountability—when their requirements conflict.

A cybersecurity standard may be entirely appropriate for the enterprise but have unintended consequences for a real-time production environment. A production requirement may protect availability but introduce a security exposure elsewhere.

Someone still has to determine what absolutely cannot fail, where isolation or segmentation is necessary, what redundancy is justified and who has authority to make a change that could affect production.

Convergence may have solved the technology boundary faster than organizations solved the accountability boundary.

The Technology Changed. The Management Problem Didn’t.

Looking back at the original article, some of the technology now sounds distinctly like 2012.

The concern behind it doesn’t.

We were trying to determine how two increasingly interconnected technology environments could coexist without one creating unacceptable risk for the other.

Today those environments are far more integrated.

The objective isn’t to rebuild the old wall between them.

Nor is it to assume that because everything uses IP, everything should be treated the same way.

The objective is to understand what absolutely has to work, what can cause it to fail, and then design the technology and governance around protecting the operation.

Fourteen years ago, I wrote that convergence was here to stay.

It did.

The harder question was always going to be what we did after it arrived.