Post-Quantum AV Procurement: A Crypto-Agility Checklist

Most AV systems bought today will still be operating when security requirements have changed. Meeting-room endpoints, AV-over-IP devices, control processors, signage players, cameras, network switches and cloud-management platforms all depend on encryption, certificates, digital signatures or secure update mechanisms.

That makes post-quantum cryptography a lifecycle and procurement issue, not just a future research topic. The goal is not to replace working AV equipment immediately. It is to avoid buying systems that cannot change when the cryptography they rely on is phased out.

Why post-quantum planning belongs in AV

NIST’s post-quantum transition roadmap identifies the widely used public-key algorithms that will need to be replaced and the standards intended to succeed them. For US federal systems, the highest-value and highest-impact assets are expected to move first, with key-establishment migration targeted by 2030, digital signatures by 2031 and broader migration by 2035.

Those milestones matter beyond government. An AV system specified now may have an expected life of seven to ten years. Some components will be replaced earlier, while infrastructure, control code, management platforms and specialist devices may remain much longer. A product that cannot accept new cryptographic methods, certificates or trusted firmware could become difficult to support before its physical hardware has failed.

What crypto agility means for an AV estate

Crypto agility is the ability to identify where cryptography is used and change algorithms, keys, certificates or supporting components without rebuilding the entire system. NIST’s guidance on achieving crypto agility treats this as an organisational capability rather than a single product feature.

For AV teams, that means knowing how devices authenticate to management portals, how control interfaces and APIs are protected, how firmware is signed, how certificates are renewed and what happens when a legacy endpoint cannot support a required change. The answer often spans the manufacturer, integrator, client IT team and cloud provider.

A practical procurement and audit checklist

  1. Map the cryptographic dependencies. Record which AV devices and services use TLS, VPNs, device certificates, signed firmware, secure boot, wireless security, API tokens or other trust mechanisms. Include cloud portals, mobile apps, remote support and integrations, not only equipment in the room.
  2. Identify the data that needs long-term protection. A room-control command and a confidential meeting recording do not carry the same consequence. Prioritise systems that handle sensitive content, identities, credentials, operational data or information that must remain confidential for many years.
  3. Ask for the vendor’s migration roadmap. Require a clear statement on post-quantum support, affected product families, planned firmware or platform changes and any hardware limitations. “PQC ready” is not useful unless the supplier explains which standards, protocols and versions are supported.
  4. Test the update path and support period. Confirm how cryptographic libraries, firmware and trusted certificates are updated, who approves the change and how rollback works. Compare the security-support commitment with the intended service life. A ten-year design based on a product with three years of updates creates avoidable risk.
  5. Plan for a mixed estate. Migration will not happen across every room and platform at once. Ask how new and legacy devices will interoperate during the transition, whether gateways or hybrid cryptographic approaches are supported and what performance or licensing effects may result.
  6. Control keys and certificates. Document ownership of certificate issuance, renewal and revocation. Test expiry and rollover before a live change is required. Avoid static credentials and certificates that cannot be replaced without factory intervention or a paid service visit.
  7. Define the fallback for unsupported equipment. Where an endpoint cannot migrate, decide whether it will be segmented, restricted, fronted by another control, replaced or retired. Make the decision according to operational consequence and exposure, not simply the age of the device.
  8. Retain evidence and review triggers. Keep the product version, cryptographic capabilities, support commitment, certificate owner and migration decision in the asset record. Reassess when NIST guidance changes, a supplier ends support, a cloud dependency changes or a major firmware release alters the security architecture.

Prioritise by consequence, not by novelty

Post-quantum planning should not become a blanket replacement programme. A disconnected display with no sensitive data may be a low priority. A control room, executive collaboration space, broadcast workflow or remotely managed AV estate may justify earlier analysis because loss of trust, confidentiality or availability has a greater impact.

Start with systems that have a long remaining life, process sensitive information, rely heavily on public-key cryptography or serve business-critical operations. An AV infrastructure audit can place these dependencies alongside firmware, network, support and end-of-life risks so the organisation can make one coordinated lifecycle plan.

Questions to add to an AV tender

Ask bidders to identify the cryptographic functions used by every networked product and service, the party responsible for each dependency and the supported method for changing it. Require a published security-support period, vulnerability-disclosure route, certificate-management process and notification if the proposed product cannot meet the client’s future cryptographic policy.

Evaluation should consider the whole system. A compliant endpoint can still depend on an unsupported management server, proprietary gateway or cloud service. The same principle applies to network switches, as explained in our AV network switch security checklist.

Build the migration path into the lifecycle

The best time to ask about crypto agility is before equipment is selected. The next best time is during an audit, before a certificate expiry, security policy change or supplier withdrawal creates an urgent project.

Venture AV’s independent corporate AV consultancy helps clients turn security, lifecycle and operational requirements into vendor-neutral specifications and practical upgrade plans. Contact Venture AV if you need to understand the cryptographic dependencies and support risks across a proposed or existing AV estate.