Home›Journal›11 September 2026: cyber rules reach the AV rack
REGULATION · 28 August 2026 · 5 min read

11 September 2026: cyber rules reach the AV rack.

Under the EU Cyber Resilience Act, reporting obligations for connected products begin on 11 September 2026, with full obligations following in December 2027. Networked AV equipment is in scope — and procurement will start asking. Here is what to ask, and what to write into the specification.

JOURNAL / 013
THE COMPLIANCE TIMELINEAUG 2025RADIO-EQUIPMENT CYBERSECURITYREQUIREMENTS APPLY IN THE EU11 SEP 2026CRA REPORTING BEGINS24 H EARLY WARNING · 72 H NOTIFICATIONDEC 2027FULL CRA OBLIGATIONSSECURE BY DESIGN, DOCUMENTEDEVERY NETWORKED AV DEVICE IS IN SCOPEREGULATION (EU) 2024/2847 — WHAT PROCUREMENT WILL ASK, THE SPECIFICATION SHOULD ALREADY ANSWER
Regulation (EU) 2024/2847 — the dates every connected-product manufacturer now works to.

For years, the security of AV equipment was a conversation between the integrator and the IT department. In the European Union it is now also a matter of law. The Cyber Resilience Act — Regulation (EU) 2024/2847 — covers products with digital elements, which includes networked AV equipment: encoders and decoders, control processors, matrices with management interfaces, anything with a firmware image and a network port.

The dates

Radio-equipment cybersecurity requirements have applied in the EU since August 2025. From 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe security incidents — an early warning within 24 hours of becoming aware, a fuller notification within 72 hours. The regulation's full obligations — security by design, vulnerability handling, documented support — apply from December 2027. These duties sit with manufacturers; but their effects reach everyone who specifies, supplies, and supports connected equipment, because procurement questionnaires are already growing a cybersecurity section.

What a specifier should ask of any AV manufacturer

Four questions translate the regulation into tender language. Where do firmware updates publish, and how is a new release announced? Is there a stated route for reporting a suspected vulnerability, and who answers it? For how long will a product receive security updates? And can the manufacturer's answers be verified in public, rather than taken on trust?

Our posture

TELECIS builds for exactly this direction of travel. A suspected vulnerability can be reported directly via the technical contact and is acknowledged within one business day; firmware is supplied on request, per model; and released documentation is revision-controlled. The compliance statement, and how to request compliance documentation for a model, is on the compliance page, and our regulatory work tracks the CRA timeline alongside CE.

Write it into the specification

The clause library at Specify TCE — TELECIS Certified Engineer — now includes a cybersecurity clause: a published firmware register, a stated vulnerability-disclosure route, and conformity with Regulation (EU) 2024/2847 as its obligations come into application. A room being tendered today will still be in service in 2030 — specifying the manufacturer's security posture now is simply specifying for the room's whole life.

Published by TELECIS · 28 August 2026 · Filed under Regulation
Specifying?

Send the room.

We return the architecture, the bill of materials, and the route to supply.