Hosting locations and disaster recovery

BeyondTrust and your customer data

All customer data is confined to a dedicated instance of BeyondTrust allocated to their organization. The data resides in a siloed BeyondTrust instance and is not shared between customers.

Customers can choose their instance deployment location based on their geographic location and preference. Atlas in the Cloud customers may also choose the deployment locations for each of their traffic node instances.

Amazon Web Services regions

From a hosting perspective within AWS, Remote Support Cloud and Privileged Remote Access Cloud (collectively SRA Cloud) can be deployed to the AWS regions listed on the BeyondTrust Cloud Region Availability page.

📘

For more information on Data Processing Addendum, see BeyondTrust's Data Processing Agreement.

AWS regions and availability zones

Each AWS region has multiple, isolated locations known as Availability Zones to provide customers with data redundancy within the cloud and to support disaster recovery functions. An Availability Zone (AZ) is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region. AZs give customers the ability to operate production applications and databases that are more highly available, fault tolerant, and scalable than would be possible from a single data center. All AZs in an AWS Region are interconnected with high-bandwidth, low-latency networking, over fully redundant, dedicated metro fiber providing high-throughput, low-latency networking between AZs. All traffic between AZs is encrypted. The network performance is sufficient to accomplish synchronous replication between AZs. AZs are physically separated by a meaningful distance, many kilometers, from any other AZ, although all are within 100 km (60 miles) of each other.

📘

For more information, see Amazon’s Global Infrastructure and Regions and Zones.

Data redundancy within AWS

SRA Cloud uses AWS EC2 Data Lifecycle Manager to take snapshots of all customer EBS Volumes and replicates those snapshots to all AZs within the instance’s AWS Region. Snapshots are taken every 4 hours and retained for 24 hours. A daily snapshot for each instance is retained for 72 hours.

In the event of a disaster, BeyondTrust Cloud Operations can restore services into a different AZ from one of the replicated snapshots.

📘

For more information, see Amazon’s EC2 Data Lifecycle Manager.

BeyondTrust disaster recovery testing & procedures

Formal Business Continuity (BC) and Disaster Recovery (DR) plans have been implemented for the corporate and cloud environment as well as other defined categories related to personnel shortages and environmental disasters. This plan is aligned to ISO 22301, certified, and audited under ISO 27001 and SOC 2 Type II, reviewed by management, tested annually, and approved by BeyondTrust's GRC Committee.

Scenarios have been developed to ensure that our teams have considered various threats and situations when attempting to restore services within the cloud. Such scenarios include the team creating a single tenant instance and intentionally rendering the service inoperable. This allows for various methodologies to be tested, such as redeploying an instance and/or implementing the last known good backup within the service. All DR testing performed by BeyondTrust is conducted through virtualization to avoid impacting our customer's daily operations and the service.

It is important to note that BeyondTrust cloud operations only carries out the DR functionality in the event of a true failure. Our organization does not perform DR procedures to recover data from accidental customer deletions or errors.

📘

For more information regarding Amazon's DR capabilities and testing, see Amazon’s Compliance Program.

Recovery time, recovery point objectives, and cloud uptime

BeyondTrust's Security Requirements states in Section 12.1.2 of Business Continuity Management that our organization is required to update and test the BCP annually at a minimum and is also required to mitigate significant changes to information security risk. With that, recovery time and recovery point objectives are situation specific and will vary depending on the nature of the incident.

The Cloud Service Guide states in Section 4. Availability Service Level, subsection (4) that BeyondTrust's

availability SLA for the service shall be 99.9% during a calendar month. From an historical standpoint (Q1 2022 to present), BeyondTrust has exceeded this SLA uptime averaging (99.997%) but is unable to commit to anything higher to due to these values reflecting the contractual commitments between BeyondTrust and AWS.