BrightSign Network (BSN) Security

this page / section pertains to brightsign network (often abbreviated bsn ), our legacy cloud platform our latest cloud platform is bsn cloud which consists of the free bsn control tier and the paid bsn content tier development of bsn has largely ceased and the platform will eventually be deprecated and replaced with bsn cloud for a cloud based content management and distribution network, database security and server reliability are of the highest priority the {{brightsign network bsn}} has been built with these principles in mind this section provides a general overview of security and recovery architecture for bsn note that some specific information may be withheld for security purposes physical security all bsn servers are hosted using amazon web services (aws) amazon strictly controls physical access to its platform infrastructure using military grade perimeter control, as well as state of the art surveillance and intrusion detection systems access to the amazon data centers is limited only to amazon employees with legitimate business needs, and each grant of access is revoked once an individual’s business need expires, even if the individual is still an employee of amazon all physical and electronic access to data centers by employees is logged and routinely audited physical assets used by brightsign employees are managed and classified by the vp of finance relevant asset changes are communicated to appropriate constituents on a regular basis virtual data center security all communication with bsn is mediated by two pairs of gateway servers all calls to bsn domains are directed to these gateways each gateway communicates with a specific set of bsn nodes, and each pair of gateways is assigned traffic from a geographically distinct part of the globe nodes located within the security group (i e behind the gateways) can communicate directly with each other because they have a list of internal ip addresses; however, these addresses are not communicated outside of the security group ddos protection the gateway servers protect internal nodes from being overloaded in case of a distributed denial of service (ddos) attack furthermore, there are backup gateway servers that are running “warm” 24 hours a day and can immediately come online if one or more gateway becomes overloaded with connections each gateway also has process code for the other gateways installed on it, so all gateways can be rotated to different routings or geographical assignments in event of an attack general disaster recovery each bsn server node has a backup server that can take over in case of unscheduled downtime the database server for the bsn has both a mirror and a backup that frequently update to prevent data loss in event the production database goes offline all active server nodes are monitored by scripts that notify brightsign it personnel less than a minute after a problem arises with a node dates, times, and an incident description are emailed to network administrators incidents are managed on a case by case basis the recovery time objective (rto) is 30 minutes or less, while the recovery point objective (rpo) is to prevent loss of any customer data there are different thresholds for communicating impairments and outages to users, depending on whether the downtime is scheduled or unscheduled business continuity and disaster recovery (bcdr) tests are conducted quarterly additionally, a business impact analysis is conducted annually all server instances are turned on and off to test resilience of the system to outages protection against intrusion attacks quarterly scans are carried out to check for hacking and intrusion attempts white hat contractors are also employed to attempt breaching public facing web applications all server operating systems are also protected with industry standard virus detection software all bsn account passwords are hashed and salted once a password is generated, it is impossible for even brightsign it personnel to obtain the password from the bsn database furthermore, only a very limited subset of individuals at brightsign have the credentials for root access to the bsn database the minimum password length for bsn accounts is 5 characters there is no complexity or lockout enforcement logging and records activity logs of the database, gateway, and secondary monitoring servers is audited regularly by the devops team logs are retained for 6 months in an easily accessible form, and up to 2 years in archives a combination of operating system logs and application logs provide a history of successful/failed login attempts, password changes, and account modifications however, there is currently no ui for account administrators to retrieve this information data storage data is stored in both a database and a file system bsn is a multi tenant service client content is segregated, but the database cluster contains the information of all tenants database backups are kept for 6 months in easily accessible form and up to 2 years in archives content is not retained in the backup cycle once it is deleted from the content store (by the client or a bsn administrator) database backups do retain some account and network state information, but not content files or pii data sql queries against the database are used to retrieve/copy data without affecting the metadata administrative security information assets all bsn and bsnee software repositories and related confidential material are managed by relevant subject matter experts within the company there is no broad based access to this information within the company employee policies all newly hired employees at brightsign are required to sign a non disclosure agreement (nda) and anti corruption documents most brightsign employees don't have access to bsn order administrator access is limited to technical support and order administrators; server access is limited to development operations engineers; and application level access (for configuration and code changes) is restricted to the automated release system only data handling the product and technical support groups within brightsign are responsible for privacy in terms of client information access to customer data is restricted to a subset of employees within the company, and these teams are trained to comply with the ndas that they sign when joining the company personally identifiable information (pii) is not required and not recommended with bsn separate systems are in place to handle credit card information, shipping addresses, and other personal information all bsn client data is sent and received electronically physical media is never used operating procedures all operating procedures related to bsn servers and source code are generated and reviewed by management by management policy, server code is never pushed manually a mix of agile and waterfall sdlc processes is used to manage and update code for bsn privacy policy the full brightsign privacy policy can be viewed here management reviews all code and configuration changes to ensure that they are in compliance with the privacy policy third parties all third parties used in conjunction with bsn are audited annually hipaa compliance bsn is not hipaa compliant and should not be used to store or transmit medical information application and communications security the brightsign network interacts with digital signage environments by communicating with brightsign devices, {{brightauthor classic}} software, and the bsn api (i e , the browser based bsn webui) players the brightsign network and brightsign players communicate with each other using https, rather than http bsn requires a player to authenticate itself with a hashed and salted phrase before it can download content because of interference with caching/proxy servers, the file download service uses http, but media files can be optionally encrypted using aes 128 brightauthor classic {{brightauthor classic}} requires bsn account authentication before affecting changes on the bsn servers all communication between brightauthor classic and the brightsign network is carried out using http and https depending on specific function tokens are used in all http communication bsn api every api call requires account authentication before affecting changes on the bsn servers or returning content from the database data center operation block diagrams notes during normal operations, the remote monitoring server only receives updates from the monitoring server within data center 1 if the remote monitoring server is no longer receiving updates from the monitoring server, it will switch to receiving information directly from each gateway, application, and database node the database servers in data center 2 constantly mirror the database servers in data center 1 the monitoring server in data center 2 reports to the monitoring server in data center 1