Security by design for your screens
With Disign, digital signage security is built in, not bolted on: servers hosted in Europe, encrypted connections, SSO and two-factor authentication, isolated teams, versioned publishing, signed firmware and a hardened operating system for your players.

Hosting & data
Your media, playlists, screen data and user accounts stay on servers located in Europe. Every exchange between the platform, your browsers and your players is encrypted in transit.
The Disign platform and your data are hosted in European data centers, a natural fit for organizations working under the GDPR.
The back office, the API and media downloads are only served over HTTPS (TLS). Nothing travels in clear text between Disign and your network.
Real-time commands and screen status updates go through encrypted WebSocket connections (WSS), never through unencrypted channels.
Architecture & network
Disign players initiate every connection themselves. Screens reach the platform over HTTPS and WSS, and the platform never needs to connect into your network. Your firewall keeps all inbound ports closed.
Disign players and screens
Servers in Europe
Players open the connection; no port forwarding, no public IP, no inbound rule.
HTTPS for the API and media, WSS for real-time: protocols your proxies and firewalls already know.
With no listening service exposed to the internet, a screen cannot be reached from outside your network.
We share the detailed flow matrix so your security team can validate the deployment quickly.
Access & users
Most digital signage incidents start with a stolen or shared password. Disign secures every account from sign-in to the most sensitive actions, so only the right people can change what your screens display.

Connect Disign to your identity provider: users sign in with their corporate account, your password policies apply, and onboarding or offboarding follows your directory automatically.
A second verification factor is required at sign-in, so a leaked password alone is never enough.
2FA recovery is limited to 10 recovery codes: a lost phone does not lock anyone out, and recovery never becomes an open door.
Sensitive requests carry a CSRF token, and session cookies are flagged HttpOnly so that scripts cannot read them.
Sign-in attempts and other critical actions are rate limited to stop brute-force attacks and automated abuse.
Even inside an active session, the most sensitive operations ask users to confirm their identity again. An unlocked computer is not enough to take control of your screens.
Team isolation
Create as many projects and spaces as you need: per site, department, brand or agency. Each space is a sealed environment with its own screens, media and users, so one team can never see or change another team's content.
Publishing governance
Campaigns, scenarios, playlists and data channels are edited in draft mode without touching what is on screen. When the work is ready, a version is created and goes through validation before it reaches your displays.
Edit freely: changes stay in draft mode and never affect the screens.
Submitting the draft creates a version: a frozen snapshot of what will be broadcast.
Users with the right permission accept or refuse the version.
Only the accepted version is published to the screens.
A refused version never reaches the screens: the team goes back to the draft.
When a user holds every permission, creating, accepting and publishing the version happen in a single click. Governance without slowing down small teams.
Franchises & large groups
Manage several organizations from one account, each with its own permission groups and very fine-grained permissions. Head offices publish approved content to a shared library, and franchisees or subsidiaries use it without ever accessing each other's data.
Shared library, curated by the content creator
Uses the head office scenes as references: every update is applied automatically.
Always broadcasts the latest approved playlists and scenarios, with no manual copy.
Copied a template and customized it freely for local promotions.
The content creator decides which modes are allowed for each shared item: scenes (designs, mini applications, templates), playlists or scenarios.
Integrity from cloud to screen
Security does not stop at the login page. Disign protects what is delivered to the player, what is installed on it and what runs on it.
Media and files are only served through signed URLs. Without a valid signature issued by the platform, a file cannot be downloaded.
Assets travel over HTTPS, and commands over WSS, from the platform to every player.
Disign OS firmware updates are signed: a player only installs an update whose signature has been verified.
The Disign player application is signed, guaranteeing it comes from Disign and has not been tampered with.
Scenes and mini applications run in separate iframes and exchange data through a secured inter-iframe channel, using the Disign SDK rather than direct access to the player.
Third-party scripts are executed in an isolated sandbox, with no access to the rest of the player or to other applications.

Lockdown enabled
Local access and maintenance closed
Disign OS
A screen running a general-purpose desktop is an unmanaged computer in a public place. Disign OS is built the other way around: a minimal system that only does digital signage.
No Windows, no macOS: Disign OS is a purpose-built embedded system that only ships what signage needs, which drastically reduces the attack surface.
The system is mostly read-only: malicious changes cannot persist, and the player always comes back to a known, clean state.
When lockdown is enabled, the player is completely locked: no local access, and even the maintenance mode is disabled.
Files stored on the player are encrypted, so your content stays protected even if a device is removed or stolen.
Maintenance relies on Disign's own system, developed in-house, and is only opened when it is actually needed.
Firewalls, proxies, VLANs, VPNs, existing hardware, internal security policies or a security questionnaire to fill in: our team goes through your deployment conditions with your IT and security teams.
Talk to our team about securityHosting, network flows, authentication, permissions and player hardening: the answers IT and security teams ask us most often.
Digital signage security covers everything that prevents unauthorized people from changing what your screens display or accessing your data: hosting, encrypted connections, user authentication, permissions, publishing control and the protection of the players themselves.
The Disign platform and your data are hosted on servers located in Europe.
No. Disign players only make outbound HTTPS and WSS connections to the platform. No inbound port, port forwarding or public IP address is required, and we can share the detailed flow matrix with your IT team.
Yes. Disign supports SSO with SAML and OpenID Connect, so your users sign in with their corporate account and your identity provider remains the source of truth.
Users can protect their account with two-factor authentication (2FA). If they lose their second factor, they can use one of their recovery codes, which are limited to 10 to keep recovery from becoming a weakness.
Create separate projects and spaces. Each space has its own screens, media and users, governed by permission groups and detailed permissions. Playlists, scenarios, campaigns and scenes can be shared with other spaces without opening the rest of the space.
Yes. Campaigns, scenarios, playlists and data channels are edited in draft mode, then submitted as a version that authorized users accept or refuse before publication. Users with all the rights can publish in one click.
Disign manages several organizations with their own permission groups and fine-grained permissions. The head office shares scenes, playlists or scenarios through a shared library, used either as a reference that updates automatically or as a copy that local teams can customize, depending on what the creator allows.
The Disign application and Disign OS firmware updates are signed. A player only installs an update whose signature has been verified, and media files are delivered through signed URLs.
Yes. Third-party scripts run in a sandbox, and scenes and mini applications communicate through a secured inter-iframe channel using the Disign SDK, without direct access to the player.
Disign OS is built like an embedded system: it only contains what digital signage needs, its system is mainly read-only, files are encrypted, and a lockdown mode can disable all local access, including maintenance.
Disign only needs outbound encrypted connections, which fits most corporate networks. Contact our team to review your specific firewall, proxy, VLAN or security policy requirements.

Servers in Europe, SSO and 2FA, isolated spaces, versioned publishing, signed firmware and the hardened Disign OS: Disign gives your security team the guarantees it expects, and your communication teams a platform that stays simple to use.