There was a time when AV sat comfortably on the edge of the network. More isolated. Quieter. Mostly someone else's problem.

That world is gone.

Today, displays, microphones, control panels, cameras, DSPs, room booking panels, wireless presentation systems, and digital signage players are all sitting on the network. And once they are on the network, they stop being just room devices. They become part of the school's wider technology environment.

AV and IT have fully merged

The convergence has been coming for years. AV-over-IP platforms, cloud-managed control systems, digital signage players, room scheduling panels — they all sit on the same infrastructure as business-critical applications. That brings real advantages. Systems can be easier to monitor, easier to manage, and more flexible to deploy across a campus.

It also means every connected AV device becomes another endpoint that needs to be considered properly.

From an IT or security team's perspective, an AV device is no different from any other network-connected system. It has firmware. It has ports. It communicates with external services. Which means it can be exploited.

The question has changed

It used to be enough to ask: does the room work? That question still matters. But it's no longer the only one.

The questions IT managers and their security teams are now asking — and should be asking — sound more like this:

• Where does this device sit on the network?
• What risk does it introduce?
• Was security considered from the start, or bolted on later?
• Who's responsible for firmware updates and patching?
• What happens when something goes wrong?

What secure-by-design AV actually looks like

This isn't about adding a security checklist at the end of a project. It's about building security into the design from day one.

What this means for schools

In a private independent school environment, the stakes are real and the exposure points are multiplying.

Think about what's on the network: interactive flat panels in every classroom. Room booking systems in the corridors. PA and bell infrastructure the whole campus depends on. CCTV. Video conferencing systems used for board meetings and parent communications. Digital signage updated from a central server.

Most school IT teams are already stretched. They are carrying infrastructure, support, cybersecurity, procurement pressure, and day-to-day operations. If AV is added to that mix without proper design thinking, it becomes one more source of avoidable risk — and one more category they are expected to manage after the fact.

That is also why the AV partner conversation has changed. The question is no longer just: "can they install it?" The real question is: do they understand the environment this system needs to operate in?

The AV partner's role has changed

For a long time, network security was someone else's problem. AV installers focused on the room. Firewalls and authentication policies were the IT team's domain. AV just needed to connect.

That's not a sustainable position anymore.

When an AV device touches the network, it becomes part of the organisation's security posture. That means integrators need to understand how their systems interact with enterprise security frameworks — NIST, Zero Trust, 802.1X authentication, VLAN segmentation. Not to replace the IT team, but to work alongside them without creating unnecessary risk.

It also means asking better questions during the design phase, not just the sales phase. What compliance standards does this network need to meet? How is the IT team structured? Who owns firmware updates after handover? Is security designed in, or is someone expected to fix it later?

How The Big Picture Group approaches this

At TBP, we have always believed that complexity is the enemy of reliability. A room that's over-engineered is harder to operate, harder to support, and harder to defend. That philosophy applies just as directly to cybersecurity.