> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/security/business-continuity-and-disaster-recovery-at-glesys.md).

# Business continuity & disaster recovery at Glesys

*A public statement of how Glesys protects and recovers its services.*

### Our approach

Glesys keeps no single standalone continuity plan. Continuity and recovery requirements sit inside the policies, processes, and roles that govern the work, so the teams that run a service also prepare its recovery.

This statement describes how Glesys prepares for, responds to, and recovers from disruption. It gives customers and partners assurance without exposing the operational detail behind it.

### Governed by a certified management system

The Glesys integrated management system governs continuity and recovery. Independent auditors certify it against ISO 9001 (quality), ISO 14001 (environmental management), and ISO 27001 (information security). Glesys is extending the same system to ISO 22301 (business continuity).

The Security Policy sets the continuity commitments, and Glesys publishes it. The Security Manager owns continuity operationally, and the IMS Coordinator coordinates it across the organization. Each business area owner is accountable for the continuity of the activities their teams perform.

### How we prepare

Glesys analyzes continuity activity by activity. An activity is a capability that Glesys performs to deliver products such as cloud, dedicated servers, colocation, storage, and connectivity. For each one, Glesys analyzes the impact of a disruption over time, maps the systems, data, suppliers, facilities, and people it depends on, and sets three objectives: how long it can be disrupted before the consequences become unacceptable, how quickly it must be restored, and how much data loss is acceptable.

The activities Glesys can least afford to be without are prioritized. Each has a continuity strategy and a recovery plan, maintained by its own business area owner and produced through the same method company-wide. Every system a prioritized activity depends on has a current recovery runbook. Glesys does not test runbooks in isolation. Glesys proves them by exercising the recovery plan of the activity that depends on them.

Glesys prepares for power outages, fire, connectivity loss, platform failures, cyber attacks, sabotage, supplier disruption, and events that affect its people. UPS systems and generators provide backup power, redundant network paths carry connectivity, and redundant systems fail over on test. High-availability platforms keep critical applications running. Automated fire detection protects the facilities, and Glesys tests those systems and runs fire drills. Glesys tests backups quarterly, including a full restoration.

Daily operations protect continuity too. Glesys controls changes so that improvements do not introduce instability. Glesys classifies every system by criticality and links each critical system to the activities that depend on it. Glesys manages its suppliers to limit the risk they pass on.

### How we respond

Glesys handles disruption at three levels.

**Incidents.** Glesys reports, contains, investigates, and resolves incidents against targets set by their urgency and impact. Containment comes before diagnosis.

**Major incidents.** Glesys declares a major incident when resolving the disruption needs more than one team, or when a prioritized activity may be disrupted beyond the period it has judged tolerable. A major incident manager coordinates the teams involved, invokes the recovery plans of the affected activities, and tracks progress against their recovery objectives.

**Crises.** Glesys declares a crisis when the situation calls for decisions, resources, or external communication beyond the mandate of major incident management. A threat to life, health, or safety, a disruption affecting several sites or a significant share of customers, and a duty to notify an authority each trigger one as well. A crisis does not require an underlying incident.

The CEO leads a crisis by default, and another member of Executive Management takes the role when the CEO is unavailable. The crisis leader and the roles around them decide, set priorities across competing activities, and communicate. They do not run the technical recovery. Where a crisis follows a major incident, the two run in parallel: the major incident manager drives recovery, and the crisis leader drives decisions and communication. When there is a threat to life, health, or safety, staff call the emergency services first, without waiting for any declaration.

Glesys gives one consistent account during a crisis. The crisis leader approves external communication before release, and a communications lead prepares and sends it. Every update states when the next one is due, and Glesys sends an incomplete update on time rather than a complete one late. At least one route for reaching customers does not depend on Glesys infrastructure.

### How we recover and improve

Business area owners run the recovery plans for their activities, validate the restored systems and dependencies, and report progress and deviations. The crisis leader sets priorities across affected activities and resolves conflicts between plans competing for the same resources. Before returning to normal operations, the responsible owners confirm that each affected activity and its dependencies are stable, and they document any workaround and residual risk.

Glesys reviews every incident in proportion to its severity, and gives major incidents, the highest priority incidents, and every crisis a dedicated review. The reviews test whether Glesys detected and escalated the event in time, whether roles and communication worked, and whether recovery met the objectives for each affected activity. Findings update the impact analysis, continuity strategy, and recovery plan of the activity concerned. Glesys escalates continuity gaps through enterprise risk management and feeds findings into future exercises.

An exercise program validates the plans before they are needed rather than during a real event. Exercises test the recovery plans of prioritized activities and the runbooks of the systems they depend on. They also build and demonstrate the competence of the roles that respond, and Glesys records who took part.

### In summary

Glesys delivers business continuity and disaster recovery through a certified management system, resilient and redundant infrastructure, a defined crisis response capability, and a continual cycle of exercises and improvement. Continuity is part of how Glesys works every day, so customers can rely on their services being protected and recoverable.

***

*Glesys, 1.0.0, 2026-09-18. Owner: IMS Coordinator.*