Security

Secure by default, from the cloud to the screen

Screens sit in public spaces and editors work from their phones. We designed for both.

Accounts

Passwords hashed with Argon2id; minimum length 10 characters
HttpOnly, Secure session cookies; sessions can be ended at any time
Sign-in attempts rate limited per address and per account
Changing your password signs out every other session

Tenant isolation

Every request is checked against your role in that company or client
Content, media, screens and people are separated per client
Inaccessible resources return “not found”, so other organisations can't be discovered
Media links are signed and expire

Screens

Single-use pairing codes that expire after 15 minutes
Each screen has its own token, handed over exactly once and revocable instantly
A screen can only read its own content and report its own status
Only outgoing HTTPS — no open ports on the screen's network

Info Display OS

root account locked; SSH keys only, and no keys shipped in images
Player and agent run as an unprivileged user with a short list of allowed system actions
Recovery page only while offline, protected by an on-screen PIN with lockout
Automatic security updates from Debian

Content safety

HTML slides run in a sandboxed frame with no access to the player or other slides
State-changing API requests require JSON, which blocks cross-site form attacks
Uploads are type- and size-checked and re-encoded before reaching screens

Accountability

Pairing, unpairing, publishing, uploads, invites, role and password changes are recorded in an audit log
Commands that affect a screen's system (reboot, update) need admin rights

Found a vulnerability?

Please email display@8w.fi with the details. We'll confirm receipt within two working days and keep you updated until it's fixed. Please don't test against other customers' data.