Software Bills of Materials for AV Procurement: A Buyer Guide

A connected AV product is rarely just one piece of hardware. A meeting-room endpoint, digital signage player, control processor, UC gateway or management platform may contain an operating system, web services, voice components, codecs, databases, remote-support agents and open-source libraries.

That matters because a security advisory may name a software component rather than the brand printed on the device. On 9 November, the US Cybersecurity and Infrastructure Security Agency added CVE-2026-116779 in SignalWire FreeSWITCH to its Known Exploited Vulnerabilities catalogue after evidence of active exploitation. The vendor advisory says affected versions can expose configuration and credentials, provide call control and allow command execution.

Not every AV or unified communications system uses FreeSWITCH. The wider buyer lesson is that a model-and-serial-number asset list may not reveal whether a vulnerable component is present. A software bill of materials, or SBOM, can help close that gap.

Why a traditional AV asset register can miss the risk

Most AV asset registers identify the manufacturer, model, serial number, location and support status of each device. This is essential, but it describes the visible product rather than all the software that makes it work.

A vulnerable library may appear in several branded products, cloud services or appliances. The equipment manufacturer may not have written that component, yet the client still depends on the manufacturer or service provider to identify exposure, provide a fix and explain any operational consequences. Without component visibility, an organisation can know exactly where a device is installed while still being unable to answer a basic question: does this vulnerability affect us?

What an SBOM can and cannot tell you

An SBOM is a structured inventory of the software components within a product or service. It can identify component names, suppliers, versions and relationships. The ENISA technical advisory on SBOMs sets out practical lifecycle, data-flow and risk considerations for organisations adopting them.

An SBOM is evidence, not a security certificate. It does not prove that a product is securely configured, that every component is exploitable, or that the manufacturer will provide a timely update. It becomes useful when it is current, mapped to the exact product build and combined with a credible vulnerability and support process.

Ten questions to add to an AV tender

  1. Which product and build does the evidence cover? Require the exact model, firmware, software release and cloud-service version where relevant.
  2. Will the supplier provide an SBOM or equivalent component inventory? Ask for a machine-readable format where available, plus a readable summary for the operational team.
  3. How often is it updated? The component record should change when firmware, software, dependencies or hosted services change.
  4. How are components mapped to products? A list of libraries is not enough if the client cannot tell which room, endpoint or service uses each one.
  5. Who monitors new vulnerabilities? Define responsibility across the manufacturer, distributor, integrator, managed-service provider and client.
  6. How will affected status be communicated? The supplier should explain whether a component is present, reachable and exploitable, including any compensating controls.
  7. What is the notification timescale? Set a clear requirement for critical and actively exploited vulnerabilities, with named escalation contacts.
  8. How are updates tested and rolled back? AV patches can affect audio, video, control, interoperability and room availability. Require a controlled test, maintenance and recovery process.
  9. How long will security support continue? Record the support period, end-of-life notice and route for replacing a product that can no longer be secured.
  10. What happens when the software supply chain changes? Require notice of material component substitutions, new cloud dependencies, acquisitions and changes to the responsible support entity.

How to use SBOM evidence in an AV audit

An AV infrastructure audit should connect software evidence to the live estate rather than collecting documents that are never used. A practical review can follow six steps:

  1. Build a verified inventory of products, firmware, software, hosted services and management platforms.
  2. Request current component evidence from manufacturers and service providers, starting with the highest-consequence systems.
  3. Compare identified components with vendor advisories, recognised vulnerability records and CISA’s Known Exploited Vulnerabilities catalogue.
  4. Assess exposure, privileges, network position and business impact rather than treating every finding as equal.
  5. Confirm the named owner, approved remediation, test plan, backup and rollback route.
  6. Record residual risk and the evidence needed to close it, including supplier statements, updated versions and post-change functional tests.

Where a supplier cannot provide an SBOM, the answer should not automatically be rejection. Ask for an equivalent component disclosure, a documented vulnerability process and a contractual commitment to investigate and notify the client. The level of evidence should reflect the consequence of failure and the expected service life.

Prioritise systems by consequence

Start with systems that are externally reachable, process sensitive conversations, hold privileged credentials, control other equipment or support business-critical operations. Typical priorities include:

  • UC, SIP and voice gateways
  • AV-over-IP controllers and management servers
  • Digital signage players with internet or content-management access
  • Remote-support appliances and cloud management agents
  • Control-room, broadcast and recording platforms
  • Endpoints shared across multiple rooms, sites or customer tenants

This risk-based approach keeps the work proportionate. It also helps procurement teams distinguish a useful security requirement from a generic request that suppliers cannot interpret or price consistently.

Make software visibility part of lifecycle planning

Software-component visibility should not end at tender award. Include it in handover, support reviews, major updates, incident response and end-of-life planning. A product that cannot be patched, supported or investigated may need network isolation, a compensating control or planned replacement even if its audio and video performance still appears acceptable.

For related controls, use the AV network switch security checklist and the AI incident response playbook. Venture AV can also help clients turn these requirements into an independent specification, audit or supplier review through its corporate AV consultancy. Contact Venture AV to discuss a specific estate or procurement exercise.