Reference, security
Hardening a display
A signage panel is not a laptop, and most of the endpoint controls on a security reviewer’s checklist cannot exist on one. This is which controls do not apply and what stands in for each of them.
Each panel runs one signed application and only ever connects outward, so it can sit on a segmented VLAN with no inbound rules. The sections below go control by control, then list what to write into your assessment.

The problem with the checklist
Your standard controls were written for computers people use.
An endpoint checklist assumes a device with a general-purpose operating system, a logged-in user, an agent that can be installed, and a directory to join. A commercial display has none of those. It runs a fixed application on a manufacturer’s embedded platform, with no user session and usually no way to install anything at all.
The reason a signage estate is normally the least governed device class on a corporate network is that people try to apply the laptop checklist, fail, and then apply nothing. What follows is what actually applies.
Control by control
What replaces each thing you cannot do.
| Endpoint agent, EDRNot possible | Nothing outside the signed Adverro application can run on the panel. There is no shell and no route to install arbitrary software, so the surface an agent would watch does not exist. The application initiates outbound connections to the platform only. Unexpected behaviour shows up centrally as an unexpected application version rather than through on-device monitoring. |
| Full disk encryptionNot available | Content is stored encrypted on the device, so it is not readable by someone with physical possession of the panel. This is application-level encryption rather than volume-level. |
| Domain join, Active DirectoryNot applicable | There is no user session on a panel to authenticate, so there is nothing to join. The trust boundary is the network: the device needs outbound connections only, to the destinations in the network requirements, and nothing inbound. Administrator identity is handled in the platform, where multi-factor authentication and role-based access apply to the people, not the screens. |
| Operating system patchingManufacturer or you | Adverro does not control panel firmware or the embedded operating system. Depending on the panel and its settings, firmware updates automatically, through the manufacturer’s channel or under your own control, and we recommend taking it through the manufacturer’s channel. This is worth raising with your AV supplier at procurement, because it determines who controls when a panel’s behaviour changes. |
| Application patchingAdverro | The Adverro application is updated server-side and pulled by the device on restart, through its update check. Combined with the daily restart we recommend as operating practice, an estate converges on the current version without anyone touching a screen. A faulty release is corrected by republishing the last stable version, which panels install the same way, and a panel can be held on a specific version. |
| Licence checkSame service | There is no separate licence server. Each panel’s licence is validated continuously by the same service it takes content from, using the panel’s own authentication token. If the panel cannot reach the service, it keeps playing until that token expires. |
| Physical accessSite responsibility | Panels live in public and semi-public space, so physical control is a site design question rather than a software one: mounting, enclosures and where the panel’s own connectors sit relative to the public. Worth deciding at installation rather than after. |
What a reviewer should take from this
Three things worth writing into your assessment.
The device is single purpose
It runs one signed application and cannot run another. That is a stronger position than a general-purpose endpoint with an agent watching it, which is why several controls on your list do not apply.
The network boundary is outbound only
Panels initiate every connection outward: to the Adverro service, the package server, media storage and, for the live view, a relay. Nothing needs to reach them, so they can sit on a segmented VLAN with no inbound rules at all. The full list is in the network requirements.
The people are governed, not the panels
Multi-factor authentication, role-based access and audit logging apply in the platform, where the decisions are made. Screens hold content, not credentials or user sessions.
Bring your security reviewer to the call.
Bring the questions procurement will ask. A completed vendor security questionnaire is available on request.