Snapshot 34652
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Contact Us Login Search Language United States (English) France (Français) Spain (Español) JumpCloud Trust, Disaster Recovery, and Resiliency JumpCloud’s platform is often at the center of an organization’s IT infrastructure. JumpCloud’s cloud-based directory service connects user identities to the systems, applications, and networks that need to be accessed. Resiliency As a cloud-based service, the question of availability is an important one. JumpCloud designs services, products and infrastructure to be secure, available, resilient and reliably scalable in the face of any number of networking, infrastructure, physical, or other challenges. JumpCloud uses many layers of defense, monitoring, and automation to ensure that its infrastructure is highly available and resilient. JumpCloud has built resilience in our service model by building scalable services across availability zones and regions to account for service or platform-level disaster across zones. JumpCloud has built a global network of ‘edge’ nodes that operate autonomously from the JumpCloud central infrastructure. JumpCloud leverages infrastructure located in a variety of different geographies. While this is primarily for resiliency and maximum uptime, it also serves to increase the performance of our platform for our customers around the globe. Disaster Recovery All persisted data is backed up and encrypted on a frequency supporting our disaster recovery point objectives (RPO). These encrypted backups are stored at multiple secure locations to ensure availability in a disaster. If necessary, data would be restored from the encrypted backup data to meet our recovery time objectives (RTO). If for any reason the central JumpCloud infrastructure were to experience an outage, these systems would continue to operate autonomously. Our customers’ systems and applications can continue authenticating against these edge servers via LDAP as normal. The ability to make changes to data would be interrupted while the management infrastructure was being recovered, but existing data would continue to be available at these edge servers. Outside of the Jumpcloud SaaS Platform, our agent-based Windows®, Linux®, and Mac® OS X would not be impacted by a widespread outage of the JumpCloud SaaS platform. Users would continue to access their devices as they normally would with their current credentials. Monitoring JumpCloud leverages multiple monitoring solutions as well as monitoring tools built in-house. These tools are aimed at detecting any issues with availability or performance as quickly as possible. JumpCloud’s monitoring infrastructure alerts the appropriate personnel, who can then investigate any issues and take appropriate action. JumpCloud also leverages an escalation protocol in situations where an issue cannot be resolved or poses a significant issue to the on-going performance of our platform. JumpCloud takes its responsibility to provide a highly available platform very seriously. If you would like to learn more about our disaster recovery or resiliency plans, please contact us at [email protected]. View JumpCloud’s real-time status here. Security Advisories JumpCloud Agent Privilege Escalation via Repair Action CVE Number: CVE-2023-26603 Remediation Date: Apr 4, 2024 CVE Publication Date: Apr 26, 2024 Bug Bounty and Vulnerabilities Reporting To learn more about our bug bounty program or to report a suspected vulnerability please review our Vulnerability Disclosure Policy.