[searchandfilter class="search" fields="search,post_types" types=",checkbox" search_placeholder="Suchbegriff..." post_types="page,post,glossar,product"]

Bluebeam Studio: Security and Disaster Recovery FAQ

Wichtiger Hinweis

Innerhalb von Bluebeam Revu gibt es einen Echtzeit-Zusammensarbeitsraum, welcher mit einer AWS-Cloudtechnologie arbeitet und wahlweise verwendet oder blockiert werden kann. Das Bluebeam Studio kann nur √ľber die Client Applikation Bluebeam Revu erreicht und verwendet werden. Mit der Installation Bluebeam Revu wird der Button “Bluebeam Studio” in der Anwendung eingeblendet und der Anwender kann sich √ľber einen Registierungsmechanismus anmelden. F√ľr die Anmeldung m√ľssen seitens der IT die unten aufgef√ľhrten Domains freigegeben werden; diese sind in der Regel nicht freigegeben.

Dementsprechend gibt es eine “Online-Nutzung” und eine “Offline-Nutzung” von Bluebeam Revu. Nur bei der Online Nutung, also der Nutzung inkl. Bluebeam Studio, m√ľssen Sie das folgende Dokument beachten. Bei einer Offline-Nutzung ohne Bluebeam Studio entf√§llt die Beachtung der folgenden Ausf√ľhrung. Als einfachtes Vorgehen zur offline Nutzung sollte die IT die Bluebeam Studio Domains f√ľr Nutzer blockieren, wenn es nicht standardm√§√üig schon der Fall ist.


This document provides clarification of questions we receive from Bluebeam Studio‚ĄĘ users regarding document and system security, access control, as well as the consequences of an infrastructure failure.

See the Studio Prime Help Manual and Studio Enterprise Support page for more information.

Accessing Bluebeam Studio

In order to participate in Studio Sessions and Projects, users must enter a username and password.

Customers using Bluebeam¬ģ¬†Revu¬ģ¬†in¬†View Mode¬†may also access Studio, but they must be invited to a Studio Session or Project by a licensed Revu¬ģ¬†user first. This is also the case for customers who might still be using Bluebeam Vu, however available functions and features may differ from those available to users of Revu 2018 and above.

Studio server connections are initiated by Revu clients, but the system does not send inbound connection requests back to the client. Primary communication and transmission of files, markups and other rich data uses the HTTPS protocol, while encryption and authentication uses the Transport Layer Security (TLS) protocol.

Revu client to Studio server diagramFirewall Requirements

Revu 12.5 and above need access to the following domains in order to communicate with the Studio Server:




Revu 12.1 and below also communicate with Studio via TCP/UDP protocols. studio.bluebeam.com:7398 should be open for these clients.

We use the following domains to communicate with end-users for support, licensing and Studio-related information. Please make sure they are white-listed to ensure successful email transmission:





These emails are sent on our behalf by amazonses.com. If your users aren’t receiving them, please ask your Email Server Administrators to check the Sender Policy Framework (SPF) record, and make sure that amazonses.com is also whitelisted as a trusted domain.

End-User Authentication & Access Control

The following protocols have been implemented for secure end-user authentication and access control:

Certificate Requirements

Connections to the Studio server (studio.bluebeam.com) are encrypted using a Public Key Infrastructure-based (PKI) SSL certificate, issued by Amazon Web Services Certificate Authority (AWS CA).

The certificate may be viewed by going to https://studio.bluebeam.com and clicking the padlock icon, located near the beginning of the URL in the address bar.

Password Requirements & Storage

All passwords must be between 8 and 32 characters, with at least one uppercase letter, one lowercase letter, one number and one special character, such as !@#$%^&*.

Password are hashed prior to storage, using a one-way strong hash algorithm with salt.

Along with this, an ‚Äėexponential back-off‚Äô algorithm locks accounts for progressively longer periods of time with each failed login attempt using an incorrect password. Login failures are logged, and our Operations Team is alerted if the quantity rises above a preset level.

The system does not store any Personally Identifiable Information (PII) besides user e-mail addresses for authentication purposes.

Data and System Security

The measures described below have been implemented to address data and system security concerns.

Infrastructure and Data Storage

Studio infrastructure diagram

Bluebeam Studio is hosted on Amazon Elastic Compute Cloud (EC2) managed by Amazon Web Services (AWS).

The Studio infrastructure is comprised of application servers which serve Revu clients on Windows¬ģ, macOS¬ģ, and iOS, as well as a backend processing system and a data tier.

User data, Project and Session metadata, and Session markups are stored on SQL servers. Actual Project and Session documents reside on Amazon Simple Storage Service (Amazon S3) servers.

Bluebeam Studio has two separate insulated instances for data residency concerns, located in the United States and the United Kingdom. The SQL and S3 buckets containing customer data are not shared between the two instances. Both instances are accessible from anywhere in the world.

SLA’s for Amazon EC2 and Amazon S3 can be found in following locations:

Data Protection

In addition to encryption of all SQL server backups and developer hard drives, all documents are automatically encrypted when uploaded to a Studio Session or Project using Revu 2015 and above, as described below.


Encryption is done by AWS using a combination of an Amazon Resource Name (ARN) and an AWS Key Management Service (KMS) key ID.

All data is encrypted at-rest (AES-256 encryption) and in-transit. Data transfer is encrypted in transit via TLS1.2* between the Revu client and Amazon S3. In the server environment, files are encrypted in Amazon’s S3 service. SQL database backups are stored on encrypted volumes.

Files uploaded using versions of Bluebeam Revu 12.1 and below are not encrypted.

System security

We‚Äôve ensured that all server instances perform in the same manner and are subjected to the same network policies and restrictions by building them with a validated and tested ‚Äútemplate.‚ÄĚ Once deployed, the following steps and policies are in place to provide additional security and consistency across the infrastructure:

Controlled Administrator Access

Only a select group of engineers have administrative rights within the Bluebeam Studio infrastructure, and management console access is controlled via Multi-Factor Authentication (MFA).

Change Control

All system changes and enhancements are documented and must undergo testing and approval by our DevOps and Security teams, before implementation in the production environment.


Audit logging of system and application-level changes and processes are centralized in our log management system.

Application and system security logs are retained for a minimum of 30 days. Only DevOps engineers have access to these logs. Developer access to logs for troubleshooting must be approved by security personnel.

Vulnerability Assessment and Remediation

We’ve implemented a comprehensive vulnerability assessment and remediation process to address any security issues that may arise. These measures include antivirus protection on all servers, proactive system patching policy, and file integrity monitoring (which detects unauthorized changes to the systems).

Applications with a web component are scanned prior to and after deployment to the production environment.

All production systems are scanned for infrastructure vulnerabilities on a recurring basis and are patched accordingly.

Inventory of Authorized Assets

All production asset additions and modifications are restricted to the DevOps team and follows Change Control procedures.  The DevOps team leverages AWS tools to maintain asset inventory.

Infrastructure & System Monitoring

To ensure a steady state of operations, a comprehensive monitoring and alert system is in place for the following:

  • Server infrastructure: CPU, memory, disk space, and uptime.
  • Applications: errors, performance degradation, and uptime.
  • Network Performance: usage and bandwidth, server response time, throughput, and web requests.

System Maintenance

Regular maintenance tasks and emergency maintenance is performed in accordance with our established Change Control process.

Disaster Recovery (DR)

In case of emergency, Bluebeam Studio includes proactive infrastructure monitoring, which provides information and alerts on system availability as well as performance and error conditions. Additionally, the Bluebeam Studio team regularly tests their disaster recovery procedures.

To handle the unfortunate event of an infrastructure failure, we’ve also put the following contingencies in place:

Backup Protocol

Full backups of the SQL Databases and Files Stores are performed on a daily basis. The backup files are stored away from production servers, and their integrity is checked regularly.


SQL Database Backups

  • Transaction log backups are taken every 15 minutes. Stored for 30 days.
  • Full backups are taken once a day. Stored for 30 days.
  • Monthly full backups. Stored for 10 years.

PDF File Backups

PDF file changes uploaded to Amazon S3 servers are copied to an isolated S3 bucket every night. These backup files are stored away from production servers, and their integrity is checked periodically.

All backups are replicated to a different AWS region.*

Infrastructure Redundancy

There is full redundancy for all Studio application servers. If a primary server fails, all traffic will automatically be switched to a secondary server.

Application servers run in a cluster behind a load balancer. Studio SQL use ‚ÄúAlwaysOn‚ÄĚ to provide HA. DNS redundancy is provided by¬†AWS Route53.

Regional Failure

In the event of a failure in our primary AWS region all data is replicated to a secondary region. Automation is in place to build all studio infrastructure so we can restore the backups and provide service from the secondary region.

*Regional failure scenario does not apply to bluebeamstudio.co.uk.

Change Log

Date Changes
11/20/2018 Updated security controls with new tools
12/14/2018 Updated DR, Redundancy an Region Failure sections.
12/18/2018 Started tracking changes, removed year, minor tweaks in wording, and added change log
02/04/2019 Updated Logo on cover page

Added details regarding NA vs UK instances

02/19/2019 Corrected some formatting issues
zur√ľck zum Glossar