Recovery Time and Point Objectives

AegisGate Security Platform recovery time objectives (RTO) and recovery point objectives (RPO). Formal availability and data recovery targets by tier.

Recovery Time and Point Objectives

Version: 1.0 Owner: AegisGate Security, LLC Review Cycle: Annual (next review: Q3 2027) Contact: security@aegisgatesecurity.io

Overview

This document defines AegisGate Security Platform’s Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) for each deployment component. These targets support SOC 2 Availability criteria, HIPAA contingency planning requirements (45 C.F.R. § 164.308(a)(7)), and business continuity planning.

AegisGate is a self-hosted, on-premises security gateway. Infrastructure recovery is the customer’s responsibility. This document covers the Platform software components and the recovery capabilities AegisGate provides.

Architecture Context

ComponentStateDeploymentRecovery Model
AegisGate binary (34.7 MB)StatelessDocker containerPull and recreate
Configuration (YAML)Semi-statefulVolume mountCustomer-managed backup
Audit logs (hash-chained)StatefulVolume mountCustomer-managed backup
License key (ECDSA P-256)StatelessEnvironment variableRe-download from portal
Session state (Redis)EphemeralIn-memoryAuto-reconstructed
Compliance engineStatelessEmbedded in binaryRecreated on startup

Recovery Time Objectives

Platform Software

ComponentRTORationale
AegisGate container15 minutesDocker pull + container start. No initialization dependencies.
Configuration restoration30 minutesRestore from version-controlled YAML backup.
License reactivation5 minutesRe-download from portal or restore environment variable.
Compliance engine warm-up2 minutesFramework registration and pattern compilation on startup.
Full service restoration45 minutesWorst case: container + config + license + warm-up.

Infrastructure (Customer Responsibility)

ComponentTarget RTORationale
Host OS recovery2–4 hoursCustomer-managed. VM restore or re-provisioning.
Docker daemon15 minutesStandard package installation.
Network reconfiguration30 minutesCustomer-managed firewall, DNS, load balancer rules.
Volume restoration1–2 hoursCustomer-managed backup restoration.
Full environment restoration4–8 hoursWorst case: complete environment rebuild.

Tier-Specific Targets

TierOverall RTOSLARationale
Community24 hoursBest effortNo guaranteed response time
Starter8 hoursNext business dayEmail support
Developer4 hoursSame business dayPriority email
Professional2 hours24/7 security supportDedicated security channel
Enterprise1 hour24/7 + dedicated engineerNamed engineer on-call

Recovery Point Objectives

Platform Data

Data TypeRPOMechanism
AegisGate configuration0 (stateless)Declarative YAML, version-controlled by customer
Compliance engine state0 (reconstructed)Derived from configuration on startup
Audit logsConfigurable (default: 0)Hash-chained, append-only. Customer-configurable backup frequency.
License state0 (stateless)Re-validated from portal on startup
Session stateNear-zeroRedis ephemeral; sessions reconstruct on next request

Customer Data (Customer Responsibility)

Data TypeTarget RPOMechanism
Persistent volumesCustomer-definedCustomer backup solution (e.g., Velero, AWS EBS snapshots)
Database backupsCustomer-definedCustomer backup solution
Audit log exportsCustomer-definedCustomer-configurable retention and export schedule

Disaster Recovery Procedures

AegisGate Platform Recovery

  1. Pull latest container image: docker pull ghcr.io/aegisgatesecurity/aegisgate-platform:v4.0.0
  2. Restore configuration: Mount version-controlled YAML from backup
  3. Restore license: Set AEGISGATE_LICENSE environment variable
  4. Start container: docker run -d -p 8080:8080 -p 8443:8443 ...
  5. Verify health: curl https://localhost:8443/health
  6. Validate compliance: curl https://localhost:8443/api/v1/compliance/status

Failover Verification

After recovery, validate:

  • Health endpoint returns 200 OK
  • Compliance engine reports all frameworks registered
  • Audit log chain integrity verified
  • TLS certificates valid
  • RBAC policies loaded
  • Rate limiting active
  • MCP guardrails active

Business Continuity Considerations

ScenarioImpactMitigation
Single container failureService unavailable until restart (15 min RTO)Docker restart policy, health check monitoring
Configuration corruptionService starts with defaultsVersion-controlled YAML, automated backup
License key expiration7-day grace period, then fail-closedLicense auto-renewal, expiration alerts
Audit log volume fullLogs stop writing, compliance riskConfigurable retention, rotation alerts
Host OS failureFull environment rebuild (4-8 hours)Customer-managed DR, infrastructure-as-code
Complete data center lossFull recovery from backup (8+ hours)Customer-managed off-site backup, multi-region

Testing Schedule

TestFrequencyResponsibleLast Completed
Container recreationQuarterlyEngineering2026-07-29
Configuration restorationQuarterlyEngineering2026-07-29
License reactivationAnnuallyEngineering2026-07-29
Full DR testAnnuallyEngineering + Customer2026-07-29
Failover verificationQuarterlyEngineering2026-07-29

Attestation

This document was reviewed and approved by:

RoleNameDate
VP EngineeringAegisGate Security, LLC2026-07-29
Security LeadAegisGate Security, LLC2026-07-29