Secure Access

Secure access to screens and company data.

An administrator updates content across dozens of screens. An employee opens a payslip on a shared kiosk. Both need convenient access — with different permissions.

An employee uses a laptop and phone while a colleague presents a card to a shared kiosk reader.
Access from a personal computer or shared kiosk should be tied to an individual identity. Illustrative visualisation.

A valid account can be in the wrong hands.

Login credentials open the way to content and data. If someone else obtains them, they may be able to use the permissions the account already has. In digital signage, the consequences go beyond what a screen looks like: unauthorised access could alter operational messages or expose company information.

Security research39%of the breaches analysed involved credential abuse at some point in the attack.Verizon · Data Breach Investigations Report 2026

Verizon DBIR 2026 counts credential abuse at any stage, not just initial access. The analysis on page 16 (Figure 11) covers 19,905 breaches, excluding the Error and Misuse categories.

The report covers cases from November 2024 to October 2025. These are contributed cases, not a representative sample of all organisations.

Open the Verizon DBIR 2026 report (PDF, page 16) Opens in a new tab

Secure access brings three tasks together: verify the person, define their permissions and end access when it is no longer needed. They apply to managing screens as well as using internal applications.

Explore security features in Docs

Sign-in that fits your organisation.

Ki-Wi Signage CMS is the web application for managing content and devices. Users can sign in with their Google or Microsoft Entra ID identity. With single sign-on (SSO), they do not need a separate CMS password.

Company identity

With single sign-on (SSO), Google or Microsoft Entra ID handles authentication. The email address must match an existing CMS account; SSO does not create a new account on its own.

Email and password

Users can enable two-factor authentication (2FA) for this sign-in method. After entering their password, they also provide a time-limited code from an authenticator app.

The choice should follow how the organisation manages identities. If centralised sign-in is already in place, the CMS can use it too. For accounts with their own password, 2FA adds another verification step: knowing the password alone is not enough.

Explore CMS sign-in options in Docs

Permissions should follow a person's work.

Signing in verifies identity. Permissions determine what that person can do. Someone preparing content does not necessarily need to decide what appears on every screen. In the CMS, for example, the User role can prepare content but cannot send it to playback.

Accounts also need to reflect who still needs access. When someone joins, changes responsibilities or leaves, their access should change accordingly. Ki-Wi Signage supports SCIM, an interface that lets Microsoft Entra ID automatically create, update and deactivate CMS accounts.

This automation requires provisioning to be configured. New accounts receive the default role configured for provisioning. Roles and groups from the company directory are not imported into the CMS. The activity view helps identify who made recorded changes and when, including content deployments.

Connect account management with SCIM in Docs

A shared device. Personal access.

In a factory or warehouse, not everyone has their own computer. Employees still need to open an HR portal, check attendance or view a personal document. Ki-Wi InfoHub makes internal applications available from a shared Windows kiosk, with personal content accessible after sign-in.

In a compatible company environment, employees can sign in with a SmartCard and PIN. Windows SSO then provides access to connected applications without repeated password entry. The setup depends on the cards, applications and company configuration in use.

For applications with their own login form, InfoHub offers Password Autofill: its password manager fills in credentials saved for that user. This works differently from SSO — sign-in still uses the username and password for that application.

Access on a shared device also needs a clear ending. InfoHub supports signing out with a button or after inactivity, clearing temporary browsing data when the session ends. Verify the configuration on the actual kiosk: after sign-out, the next person must not be able to access the previous open session.

Explore Ki-Wi InfoHub

Start with three practical decisions.

How will people sign in? Choose a company identity or a password account with 2FA. For shared kiosks, also consider the cards in use and how the connected applications authenticate users.

Who can prepare, publish and administer? Assign roles around actual responsibilities. Decide who owns account changes and whether automated provisioning can handle them.

How will you check that access ends? Test both an employee leaving the company and people taking turns at a kiosk. Deactivating an account and ending a session are different scenarios — verify both.

How Ki-Wi Signage works

Last updated: .

How should secure access work for you?

We can review your sign-in, account management and shared kiosk access, then plan how they connect to your company systems.