A service level agreement (SLA) is a contract term that defines the level of service a provider commits to deliver, such as uptime, response time, or support hours, and what happens if the commitment is missed.
An SLA is a commercial commitment, not a compliance framework. In SOC 2, it connects most closely to the availability criterion, because a company that promises uptime to customers usually needs controls that support the promise.
In simple terms, an SLA answers:
- What service level are we promising?
- How is it measured?
- What remedy applies if we fall short?
Why an SLA Matters
- It sets customer expectations in writing
- It gives engineering and support clear targets
- It can drive investment in monitoring and resilience
- It affects how a company evaluates its own vendors
Common SLA Elements
| Element | Example |
|---|---|
| Uptime commitment | A target percentage of availability per month |
| Measurement method | How and where uptime is measured |
| Support response | Target response times by severity |
| Exclusions | Scheduled maintenance or customer-caused issues |
| Remedy | Service credits or termination rights |
Specific numbers are set by each company and agreed in its contracts. There is no universal standard value.
SLA vs SLO vs SLI
| Term | Meaning |
|---|---|
| SLI | A measured indicator, such as request success rate |
| SLO | An internal target for an SLI |
| SLA | A contractual commitment, often looser than the internal SLO |
Example Evidence
| Activity | Example evidence |
|---|---|
| Commitment | Customer contract or terms of service with the SLA |
| Measurement | Uptime reports or status page history |
| Monitoring | Monitoring alerts and on-call records |
| Recovery | Business continuity and disaster recovery test records |
How Auditors Typically See It
Auditors do not test whether you met a customer SLA. In a SOC 2 examination that includes availability, they test the controls you describe in your system description. If you state commitments there, auditors may check that related controls operate as described.
Common Mistakes
- Promising a service level that monitoring cannot measure
- Using different uptime definitions in contracts and internal reports
- Not keeping records that show how uptime was calculated
- Treating the SLA as proof of a control
How AuditFlo.co Helps
AuditFlo.co helps teams retain audit-period evidence collection records from connected systems. It does not measure your uptime, does not enforce SLAs, does not issue SOC 2 reports, does not certify compliance, and does not replace auditors.