Cross-Sector

SOC 2: Availability

Controls focused on uptime commitments, fault tolerance, incident response, and recovery objectives.

Back to SOC 2 categories

Controls and Detailed Requirements

9 of 9 controls
A1.1Availability Objectives and Service Commitments

Document service availability commitments, recovery objectives, and critical dependencies so operations teams can align architecture and support procedures to contractual uptime expectations.

A1.2Capacity and Performance Planning

Forecast system demand, monitor performance thresholds, and execute capacity planning actions before bottlenecks affect customer-facing services.

A1.3Environmental and Infrastructure Resilience

Design infrastructure with redundancy, fault tolerance, and environmental safeguards so single points of failure do not compromise service continuity.

A1.4Operational Monitoring for Availability

Continuously monitor service health, latency, and availability indicators, and trigger alerts with actionable runbooks when thresholds are exceeded.

A1.5Business Continuity and Disaster Recovery

Maintain tested continuity and disaster recovery plans that define backup strategy, failover processes, and recovery responsibilities across critical systems.

A1.6Backup Integrity and Restoration

Execute and monitor backup jobs, validate backup integrity, and perform periodic restore tests to demonstrate recoverability within defined objectives.

A1.7Incident Response for Availability Events

Operate documented incident response workflows for outages, including escalation, communication, root-cause analysis, and corrective action tracking.

A1.8Availability Change and Release Controls

Assess operational impact of changes before release and schedule high-risk deployments with rollback and communication plans to minimize outage risk.

A1.9Resilience Testing

Conduct scheduled exercises such as backup restores and failover drills, capture lessons learned, and update procedures to improve recovery performance.