This page outlines how not following the recommended security policies can expose users to vulnerabilities including 

 statement is intended to explain the tradeoffs between accessibility and security that users of BrightSign players need to consider for various different applications. Generally speaking, more accessible players are less secure and less accessible players are more secure.

When the Local Diagnostic Web Server is turned ON and is NOT password protected, the player is at it's most accessible. While this is the recommended configuration for development and lab applications where accessibility is preferred and often critical for troubleshooting issues and bugs, this accessibility also means that a potential bad actor have full access to storage, the runtime, the networking interface and other aspects of the system.

Consequently, any security testing that does not follow our security recommendations are not cause for action by BrightSign. Please be sure to refer to 

Q4 2022 Security Statement

Advisory ID: ZSL-2020-5595

This is our legacy cloud platform. Our latest cloud platform is BSN.Cloud which consists of the free bsn.Control and the paid bsn.Content tiers. Development of BSN has largely ceased and will eventually be deprecated and replaced with BSN.Cloud.

BrightSign_Network_BSN

BrightSign’s *legacy* app for authoring and managing players. The app's actual name is BrightAuthor but is referred to as BrightAuthor Classic to lessen confusion with BrightAuthor:connected, our latest app.

BrightAuthor_Classic

BrightSign’s latest free, all-in-one app for player setup / management, authoring, and content management.

BrightAuthorconnected

The BSN.Cloud record of a player and its Setup. The Default Setup is assigned to the player unless another Setup has been explicitly set.

Provision_Record

The process where a Setup is delivered and applied to a player by BSN.Cloud.

Provision

A set of files containing player settings (player name, description, time zone, Publishing Mode, network settings, etc.) and an autorun.brs file which instructs the player what to do upon bootup.