Hosting locations and disaster recovery

How EPM Cloud for Linux stores data

Customer data in EPM Cloud for Linux is securely stored on Amazon Web Services (AWS). EPM Cloud for Linux uses a microservice architecture with multiple purpose-built data stores. Data is kept isolated by tenant IDs at the row level in shared databases. Tenants operate independently in each AWS region, ensuring data remains secure and separated.

You can choose your primary instance deployment location based on your geographic location and preference.

For non-US based customers, a list of sub-processors used to deliver the services can be referenced in Schedule 3 of BeyondTrust’s Data Processing Agreement (DPA).

Amazon Web Services (AWS) regions

EPM Cloud for Linux is deployed in two AWS regions:

• US-East-1 (Northern Virginia)
• EU-Central-1 (Frankfurt)

These regions ensure optimal performance and compliance with regional data protection regulations. Each tenant's data is stored and managed in its designated region for compliance. While data may transfer between regions for user access, storage, and processing remains in the tenant’s primary region to uphold data residency commitments.

ℹ️

Note

View the BeyondTrust Cloud Region Availability page for our current list of hosting regions.
For more information on Data Processing Addendum, see BeyondTrust's Data Processing Agreement.

AWS regions and Availability Zones

Each AWS region consists of multiple Availability Zones (AZs), which are isolated locations in a region. EPM Cloud for Linux uses these AZs to enhance data redundancy and support robust disaster recovery strategies. AZs are geographically dispersed but connected through low-latency networks. This mitigates risks from environmental events that could impact service availability and ensures high levels of fault tolerance.

ℹ️

Note

For more information, see AWS Regions.

Disaster recovery testing and procedures

Formal Business Continuity Plans (BCP) and Disaster Recovery Plans (DRP) are in place for the corporate and cloud environment, as well as other categories related to personnel shortages and environmental disasters. These plans align with ISO 22301, are certified and audited under ISO 27001 and SOC 2 Type II, reviewed by management, tested annually and approved by BeyondTrust's GRC Committee.

Disaster recovery processes are critical to EPM Cloud for Linux's operational strategy. We conduct tests to ensure recovery time objectives (RTO) and recovery point objectives (RPO) are met. These tests validate the system's ability to quickly recover from potential failures, minimizing service disruptions and maintaining operational continuity.

• Regular recovery drills: Simulated recovery scenarios ensure systems and personnel are prepared for actual disaster events.
• Monitoring and alerts: Continuous monitoring of system performance and automated alerts allow rapid response to any issues.

BeyondTrust only acts on disaster recovery plans in the event of a true failure. Our organization does not perform these procedures to recover data from accidental customer deletions or errors.

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.