AV Network Switch Security: A Practical Audit Checklist

A managed network switch can sit quietly at the centre of an AV estate. It may carry meeting-room traffic, AV-over-IP signals, control data, digital signage, monitoring and power to connected devices. When that switch is poorly inventoried, exposed or out of support, several room services can inherit the same risk.

A recent security development makes the issue unusually concrete. The US Cybersecurity and Infrastructure Security Agency has added CVE-2026-7273 to its Known Exploited Vulnerabilities catalogue after finding evidence of active exploitation. Zyxel’s advisory says the flaw affects specified firmware versions on several GS1900 switch models. A LAN-based attacker who is not authenticated could potentially execute operating-system commands through a crafted request. Patches are available for supported affected models.

This is not a reason to single out one manufacturer. It is a useful reminder that AV security depends on the network infrastructure beneath the endpoints, and on the process used to maintain it.

What this means for AV owners

Known Exploited Vulnerabilities deserve priority because they are not merely theoretical. In this case, an attacker needs network reachability to the management interface, but the interface does not need to be exposed to the public internet. An unmanaged contractor device, an overly broad local network or compromised credentials elsewhere in the environment can all change the risk picture.

The operational problem is often ownership. The AV integrator may have selected and configured the switch, internal IT may control the network, a managed service provider may hold the credentials, and facilities may own the maintenance budget. If no one is explicitly accountable for monitoring advisories and approving firmware changes, a supported product can remain vulnerable long after a fix exists.

Immediate checks for potentially affected switches

  1. Identify the exact switch model, hardware revision, firmware version and physical location. A family name alone is not enough.
  2. Compare that information with the manufacturer’s advisory. Do not assume every model in a product family is affected, or that every available patch applies to every hardware revision.
  3. Follow the vendor’s mitigation and update guidance through normal change control. Back up the configuration, define a rollback route and plan a functional AV test after the change.
  4. Review available logs and management history for unexpected access or configuration changes, particularly if the interface was reachable from general user networks.
  5. Restrict switch management to authorised administrators and appropriate management networks. Remove obsolete accounts and avoid shared credentials where the platform supports individual access.
  6. Record the decision and evidence. An audit trail should show what was checked, what changed, who approved it and how successful operation was verified.

Seven controls an AV network audit should cover

1. A usable asset and firmware inventory

The inventory should identify make, model, hardware revision, firmware, management address, location, function, support status and responsible owner. It must be detailed enough to compare directly with a security advisory. A spreadsheet listing “48-port AV switch” will not support a reliable response.

2. A protected management plane

Document which networks and administrator devices can reach the management interface. Confirm that management is not available from guest, general user or other unnecessary networks. Review remote-access routes, unused services and any dependency on a supplier-hosted portal.

3. Clear identity and access rules

Replace default accounts, remove former supplier or employee access and use named administrator identities where possible. Privileges should match the task. Credentials need an accountable owner, secure storage and a controlled handover process rather than being buried in an installation document.

4. Defined patch ownership

Write down who monitors advisories, assesses relevance, approves downtime, obtains firmware, tests the change and verifies AV operation. Set a risk-based response target for actively exploited vulnerabilities. NIST’s patch-management guidance treats patching as preventive maintenance, which is a useful model for long-lived AV infrastructure.

5. Configuration backup and recovery

Keep a current, protected configuration backup and prove that it can be restored. Record VLANs, multicast settings, quality-of-service rules, port configuration and power requirements. A patch plan without a tested recovery route can turn a security fix into a service outage.

6. Monitoring and time synchronisation

Send useful security and configuration events to an appropriate monitoring service where practical. Accurate time, retained logs and clear alert ownership make investigation possible. Monitoring should distinguish a genuine AV fault from a network or access-control event.

7. Support, end-of-life and replacement planning

Confirm the manufacturer’s security-support period and the organisation’s planned replacement date. Unsupported switches can remain operational for years, but the absence of fixes changes the risk and business-continuity case. Include compatible spares, configuration portability and migration effort in the lifecycle plan.

Questions to put into the next AV tender

  • How long will the proposed switch receive security and firmware updates?
  • Where are vulnerability advisories published, and how will the client be notified?
  • Can configurations, logs and asset data be exported in usable formats?
  • Which secure management, authentication and logging functions are supported without extra licences?
  • Who owns patching during delivery, warranty, managed service and eventual handover?
  • What is the tested rollback and recovery procedure if an update affects AV performance?

Make the switch part of the AV health check

A dependable review connects cybersecurity with operational reality. It checks the switch and firmware, but also tests the rooms, signal paths, documentation, support arrangements and recovery process that depend on them. The goal is not a long list of theoretical findings. It is a prioritised plan that protects service continuity and gives each action a clear owner.

Venture AV’s AV audits and legacy upgrades identify technical, lifecycle and ownership gaps across existing estates. For environments where availability is critical, see our approach to business-critical AV infrastructure. If you need an independent view of an existing system or an upcoming procurement, contact Venture AV.