Course contentsShow
← Security
Lesson 2593 of 3,05249. Compliance and RegulatoryFree lesson

Availability Criterion

Understanding availability commitments, system uptime, disaster recovery, and incident management requirements.

Availability Criterion

What you'll learn: How the SOC 2 Availability criterion ensures systems remain accessible and operational when users need them.

After covering the Security criterion, the Availability Trust Services Criterion focuses on whether your system is accessible and usable as committed. This isn't just about uptime percentages—it's about demonstrating structured commitments around system availability, disaster recovery capabilities, and how you handle disruptions.

Core Commitments

The Availability criterion evaluates whether your organization:

  • Defines availability commitments explicitly (e.g., "99.9% uptime during business hours")
  • Monitors system performance against those commitments continuously
  • Plans for and tests disaster recovery to restore service after major incidents
  • Manages capacity to prevent overload and degradation
  • Responds to incidents systematically to minimize downtime

Think of availability like an airline's on-time performance promise. They don't just say "we fly planes"—they commit to specific schedules, have backup aircraft ready, monitor weather constantly, and follow protocols when delays happen.

Key Components Auditors Examine

System Uptime Tracking: Do you measure actual availability? Are metrics aligned with your SLA commitments?

Disaster Recovery Plans: Can you restore operations after catastrophic failure? Have you tested these plans recently?

Incident Management: When outages occur, do you follow documented procedures? How quickly do you detect, respond, and communicate?

Capacity Planning: Do you monitor resource utilization and scale proactively before performance degrades?

Redundancy and Resilience: Are single points of failure eliminated through backup systems, load balancing, and geographic distribution?

Unlike the Security criterion (which asks "are you protecting the system?"), Availability asks "is the system actually working when promised?"

Key Takeaway: The Availability criterion requires documented commitments, continuous monitoring, tested recovery procedures, and evidence that your system delivers on its uptime promises—not just that it's theoretically available.