Enterprise communications require precise control over who can change content, which displays receive it and what information is available to users. SignagePlus provides defined capabilities for access management, organizational separation and recording administrative operations. The deployment model and infrastructure configuration also form part of each project’s security design.
Enterprise access and communications
Access aligned with individual responsibilities
Users, roles and platform permissions are managed within organizations and workspaces. Responsibility for content, displays and other resources can be divided among users, with each role receiving permissions suited to its duties. Platform services also enforce these permissions.
Separation of organizations and workspaces
Resources such as content and data sources are associated with an organization and workspace. Requests are evaluated against permissions within that scope. Role design and periodic access reviews should be part of the organization’s operating process.
Secure communications and enterprise sign-in
Web access and platform communications are configured over HTTPS in a secure deployment. Valid certificates, TLS settings and network rules should be configured and reviewed for the cloud or on-premises environment.
SignagePlus can connect to an enterprise directory service through LDAP. The connection method, certificate validation and access policies should align with the organization’s infrastructure and security requirements.
Scoped authorization for enterprise content display
For monitoring dashboards, display authorization is bound to a specific dashboard and organizational scope and has a limited validity period. This authorization does not give the display administrative access to the management panel.
Protecting displays and VMS boards
Displays are registered and authenticated to receive the relevant content. In the VMS workflow, playlist signing and validation help verify the authenticity of received content. Behavior during connectivity loss and use of the last valid content depend on the player type and project settings and should be tested on the destination hardware.
Data protection and deployment model
Protecting sensitive connection information
Data-source connection settings can contain sensitive information. The platform stores these settings in encrypted form within its data-source layer so they are not retained as plain text in the database.
Protection of keys, server disks, file storage and backups should also be defined in the deployment design. The encryption status of each layer is evaluated according to the actual configuration of that environment.
Operation logging and change tracking
The platform records events and change history for the administrative operations it covers. This information helps the responsible team track significant changes and investigate operational incidents. Report access, retention periods and review processes should be set according to organizational policy.
Choosing cloud or on-premises deployment
SignagePlus is available for cloud and on-premises deployment. In an on-premises deployment, server location, network access and data-retention policies are aligned with the organization’s infrastructure. Responsibility for updates, backups, certificate maintenance and service recovery should be assigned between project parties from the outset and recorded in project documentation.
Discuss your organization’s security requirements · Explore on-premises deployment
No. The product architecture has no general requirement to use AWS. Storage infrastructure and deployment location are defined by each project’s technical design.
No. Protection of sensitive data-source settings is implemented in the product; protection of files, disks, backups and keys also depends on the relevant layer and deployment configuration. The exact encryption scope should be evaluated for the specific environment.
Retention periods for content, events and backups should be based on organizational policy and the deployment design. Before launch, the team reviews responsibility for backups, access to backup copies and the recovery scenario, then records them in project documentation.