At Carousel, we do our absolute best to be good stewards of the data that you entrust with us. To that end, we have implemented technology, policies, and procedures to secure your data.
URLS, Firewalls, and Ports
TCP Port 443 is used between user workstations and your Cloud URL to access the Carousel user interface over the internet.
TCP Port 443 is used between your Media players and the Cloud URL.
Web Sockets are used between your Media players and the Cloud URL.
This allows the players to be able to get on-demand content, alert content and channel change notifications from the Cloud. If web requests are blocked, changes may be delayed.
mail.carouselsignage.net is used to invite new users to join your Cloud Account
Your Media players will access:
The URL(s) of streaming network video you wish to display (port can be specified in URL)
The URL(s) of websites used for interactive bulletins
The following URL’s are used by Brightsign players/BSN Cloud:
http://fileservices.brightsignnetwork.com - on ports 9990, 9991, 9992, 9993 and 9994
Here is a link to a BSN Connectivity utility which can confirm a network locations ability to connect to BSN specific addresses:
These are specific to Brightsign/BSN cloud and any questions about network setup should be directed to firstname.lastname@example.org
Carousel Cloud is hosted in Amazon Web Services, which is compliant with many security standards including:
SOC 1/ISAE 3402, SOC 2, SOC 3
FISMA, DIACAP, and FedRAMP
PCI DSS Level 1
ISO 9001, ISO 27001, ISO 27017, ISO 27018
For a complete list of data center controls in place by AWS, including Business Continuity & Disaster Recovery, Physical Access Controls, Monitoring and Logging, and more, please visit https://aws.amazon.com/compliance/data-center/controls/
Carousel Cloud is hosted within the
us-east-1 region of Amazon Web Services.
Data in transit is encrypted using HTTPS/SSL and TLS 1.0-1.2 protocols.
Data At Rest
Data at rest is encrypted using an XTS-AES-256 block cipher.
Encryption keys are managed by AWS Key Management services
Carousel Cloud uses several services to automatically monitor uptime and site availability. Key employees receive automatic email and SMS notifications in the case of downtime or emergencies.
You can also check for outages and incident status on our Cloud Status Page.
Carousel cloud contains many security features designed to protect access to your data from unauthorized users.
Carousel Cloud Authentication
Password requirements and controls
Passwords are never stored in plain text, and are prevented from being added from log files.
Passwords are stored using the following encryption algorithm standard:
PBKDF2 with HMAC-SHA1, 128-bit salt, 256-bit subkey, 1000 iterations.
* (See also: SDL crypto guidelines v5.1, Part III)
Carousel can communicate using SAML (Security Assertion Markup Language) with an external IdP (Identity Provider) as the source of truth for who is allowed access to the Carousel system. Setting up this communication requires the exchange of several security settings between Carousel and the IdP.
Carousel officially supports the following IdP’s.
Role Based Access Control
Site Admins have the ability to create custom access rights for users in order to limit access to their relevant areas within Carousel.
Carousel Cloud includes the ability for signage content to require admin approval before it can be published live.
All media players must securely register with Carousel Cloud before displaying signage content. In order to register a player, users must be able to log into Carousel Cloud with the appropriate user rights.
Players registration can also be revoked should it ever be necessary to do so.
Software Engineering Security
Ongoing Dependency Vulnerability Monitoring
We monitor all of our software dependencies closely for security advisories using automated tooling, and we update dependencies promptly when new security releases are issued.
Security-focused Code Review
Every change to the software, big or small, undergoes a critical code review process where engineers review the suggested change for accuracy, reliability, and security impact. A change cannot be merged in unless at least two engineers have approved it.
OWASP Top 10 Training
Our engineering team does regular research and training into the OWASP Top 10 list, and uses this training in both code creation and review.
Data entered into a Carousel Cloud input field is checked relevance and sanitized to prevent any malicious code or script execution.
All changes must be promoted from development, into a staging environment where testing is performed, before being promoted to production systems. All production deployments follow a strict release checklist, are always performed by no fewer than two engineers, and detailed logs are kept.
Access to production systems is strictly controlled, and all connections to production systems are logged. Access logs are stored on separate infrastructure using AWS Cloud Trail.
Ongoing Penetration Tests
We have partnered with a third party penetration test company to perform regular penetration tests of Carousel Cloud. During the most recent test (performed Nov 2019), the pen-test team identified 4 critical and 8 medium/low findings. All findings have since been resolved by our team and confirmed as such by the original pen-test team.
We require 2FA to be in place on all critical systems.
We have enacted an Asset Management policy which includes requirements around clean desk, screen locking, and device encryption, with enforcement via MDM software like Jamf. Access to our physical office is controlled and monitored using uniquely issued id cards. 24 hour security patrols are onsite.
Access to production systems is restricted to a limited scope of roles within the company.
All sensitive credentials are stored in encrypted vaults, with limited access.
Onboarding/off-boarding procedures are in place to ensure access to internal systems is granted/revoked appropriately.
All staff are subject to background checks.
If you have a security vulnerability to report, we ask that you send us a message directly at the following address:
All vulnerability report submissions are read within hours of receipt, and we aim to respond to all submissions within 48 business hours.