Industry Perspectives

SOC 2 for Cloud Infrastructure Providers

Tyler Carbone
Published Updated 9 min read

If your infrastructure customers keep asking for a SOC 2 report that can survive their own downstream audits, you are not alone — this is the most common challenge we see with cloud infrastructure and hosting companies. Here is how we help infrastructure providers build SOC 2 programs that hold up under the most intense scrutiny in the market.

Key Takeaways

  • •For the next operating decision, compare compliance for technology companies with managed compliance services.
  • •When your customers undergo their own SOC 2 audits, they must address how they rely on third-party infrastructure providers.
  • •Confirm which responsibilities belong to the provider, subservice organizations, and customers.

Your customers — SaaS companies, enterprises, and regulated organizations — depend on your SOC 2 report to support their own compliance programs. When a SaaS company's auditor evaluates their control environment, your SOC 2 report serves as evidence that the underlying infrastructure controls are sound. This downstream dependency means infrastructure provider SOC 2 reports receive more intense review than any other vendor category, and weaknesses in your report directly impact your customers' audit outcomes.

This guide covers SOC 2 compliance specifically for cloud infrastructure and hosting companies, addressing the subservice organization model, the inclusive versus carve-out method, complementary user entity controls (CUECs), Trust Service Criteria selection for infrastructure providers, availability and uptime SLA documentation, and how to build a SOC 2 report that withstands the intense scrutiny of downstream auditors and enterprise security teams.

For the next operating decision, compare compliance for technology companies with managed compliance services. Confirm the work included, the evidence you need, and who will own implementation before committing to a provider.

How do subservice organizations affect the report?

When your customers undergo their own SOC 2 audits, they must address how they rely on third-party infrastructure providers. You are a "subservice organization" in SOC 2 terminology — an organization that provides services to a service organization (your customer), which in turn provides services to its own customers (end users).

Why This Matters

Your customers' SOC 2 auditors must evaluate whether infrastructure-level controls are adequate. They do this by reviewing your SOC 2 report. If your report has significant exceptions, covers an insufficient scope, or uses a limited trust criteria set, your customers face audit complications — potentially exceptions in their own reports.

This downstream accountability creates strong market pressure. In our experience working with infrastructure providers, these dynamics are non-negotiable:

Inclusive vs Carve-Out Method

Your customers choose one of two methods to address your services in their SOC 2 report:

How do subservice organizations affect the report? — comparison
MethodHow It WorksImpact on You
Inclusive methodYour customer's auditor evaluates your controls directly as part of their auditYour controls are tested in detail; high scrutiny on your control environment
Carve-out methodYour customer's report states that they rely on your services and references your SOC 2 reportYour SOC 2 report must be comprehensive enough to satisfy downstream auditor review

The carve-out method is far more common because the inclusive method requires your customer's auditor to have direct access to your systems and evidence. Under the carve-out method, your SOC 2 report becomes the primary evidence of your infrastructure control effectiveness — making report quality critical. We recommend that every infrastructure provider treat their SOC 2 report as a customer-facing product that must meet an exceptionally high quality bar.

Which criteria address the infrastructure service commitments?

Infrastructure providers should include more Trust Service Criteria than the typical SaaS company because downstream customers depend on your service characteristics beyond basic security. We advise our infrastructure clients to think about criteria selection from the perspective of their customers' auditors — not just their own compliance requirements.

Which criteria address the infrastructure service commitments? — comparison
CriterionRecommendationReasoning
Security (Common Criteria)RequiredMandatory for all SOC 2 audits
AvailabilityStrongly recommendedInfrastructure uptime directly affects customer service delivery; most customers expect this
Processing IntegrityRecommendedValidates that infrastructure processing (compute, storage, networking) operates correctly
ConfidentialityRecommendedValidates protection of customer data across shared infrastructure
PrivacySituationalRequired only if you process end-user personal data (uncommon for pure infrastructure)

Why Availability Is Essential

For infrastructure providers, Availability is not optional in practice — even though it is technically optional in the SOC 2 framework. What we tell clients is: if you provide infrastructure, your customers' services live or die on your uptime. Enterprise buyers purchasing infrastructure for mission-critical applications will not consider providers whose SOC 2 reports lack Availability criteria. Including Availability requires:

  • Documented uptime commitments and SLA targets
  • Capacity monitoring and planning procedures
  • Redundancy and failover mechanisms
  • Backup and recovery procedures with documented RTO and RPO
  • Incident communication procedures for availability events
  • Historical uptime data and incident response records

Why Processing Integrity Matters

Infrastructure providers that handle compute, storage, or networking must ensure these services operate correctly. Processing Integrity validates that your infrastructure does not introduce errors, data corruption, or processing failures. In our experience, this criterion is increasingly expected by enterprise buyers. For infrastructure providers, this means:

  • Storage services maintain data integrity (no silent corruption)
  • Compute services execute workloads as specified
  • Networking services route traffic correctly and securely
  • Database services maintain transactional integrity
  • API services process requests accurately

Complementary User Entity Controls (CUECs)

CUECs are controls that your customers must implement on their end for the overall control environment to function as intended. For infrastructure providers, CUECs are particularly important because you provide the platform but your customers configure and operate their applications on top of it.

Common CUECs for Infrastructure Providers

Complementary User Entity Controls (CUECs) — comparison
CUECWhat It Requires of Your CustomerWhy It Is Necessary
Access managementCustomers must manage their own user access to resources on your platformYou provide the access control tools; customers must use them appropriately
Encryption configurationCustomers must enable encryption for their data stored on your platformYou offer encryption capabilities; customers must activate them
Network security configurationCustomers must configure security groups, firewall rules, and network ACLsYou provide networking controls; customers must configure them for their workloads
Backup configurationCustomers must configure backup schedules and test recovery procedures for their dataYou provide backup tools; customers must set them up
Monitoring configurationCustomers must set up monitoring and alerting for their applications and resourcesYou provide monitoring capabilities; customers must implement them
Patch managementCustomers must patch their own operating systems and application softwareYou manage infrastructure; customers manage their software stack
Security incident reportingCustomers must report suspected security incidents to your security teamEffective incident response requires customer cooperation

Documenting CUECs Effectively

CUECs must be documented clearly in your SOC 2 report's system description. In our experience, ambiguous CUECs are one of the most common weaknesses we see in infrastructure provider reports — they create problems for your customers because their auditors cannot determine what their responsibilities are. For each CUEC, we recommend:

  • State the specific control the customer must implement
  • Explain why the control is necessary (what risk it addresses)
  • Describe how the customer can verify they have implemented it
  • Reference any platform tools or documentation that support implementation

Well-documented CUECs demonstrate compliance maturity and make your report more valuable to downstream auditors.



Infrastructure-Specific Controls

Beyond standard SOC 2 controls, infrastructure providers must address controls specific to their service delivery model. We walk our infrastructure clients through each of these areas during scoping to ensure nothing is missed.

Multi-Tenancy Controls

Infrastructure-Specific Controls — comparison
Control AreaWhat Auditors Evaluate
Tenant isolationLogical separation between customer environments ensuring one tenant cannot access another's data or resources
Resource allocationFair resource distribution preventing one tenant from degrading another's performance
Data segregationCustomer data stored and processed in isolated contexts with no cross-tenant data leakage
Configuration isolationCustomer configurations cannot affect other tenants' environments
Noisy neighbor mitigationControls preventing resource contention between tenants

Physical and Environmental Controls

Infrastructure providers with data center operations face additional physical security requirements:

  • Physical access controls (biometric, badge, multi-factor physical authentication)
  • Environmental monitoring (temperature, humidity, water detection)
  • Power redundancy (UPS, generator, dual power feeds)
  • Fire suppression systems
  • Visitor management procedures
  • Equipment disposal and media destruction

For providers using hyperscale cloud (AWS, Azure, GCP) as their underlying infrastructure, we recommend referencing the cloud provider's own SOC 2 report for physical and environmental controls and focusing your report on the controls you operate on top of that infrastructure.

Change Management for Infrastructure

Infrastructure change management is more complex than application change management because changes can affect all customers simultaneously. What we tell clients is that this is one of the areas where infrastructure SOC 2 reports diverge most significantly from application-level reports:

  • Infrastructure changes must include impact assessment across the customer base
  • Maintenance windows must be communicated to affected customers in advance
  • Rollback procedures must be tested and documented
  • Emergency change procedures must balance speed with safety
  • Configuration management databases (CMDBs) must accurately reflect infrastructure state

Capacity Management

Infrastructure-Specific Controls — comparison
ControlEvidence
Capacity monitoringDashboards and reports showing resource utilization across infrastructure
Capacity planningDocumented capacity planning process with growth projections
Auto-scaling configurationArchitecture documentation showing auto-scaling capabilities and thresholds
Threshold alertingAlert configurations that trigger before capacity limits are reached

How do you build a Report That Withstands Scrutiny?

Report Quality Indicators

Downstream auditors and enterprise security teams look for specific indicators of a strong infrastructure provider SOC 2 report. Based on what we see reviewing reports across the industry, these are the markers of a credible infrastructure SOC 2:

  • Complete Trust Service Criteria coverage: Security, Availability, and Processing Integrity at minimum
  • Twelve-month observation period: Demonstrates sustained operational control effectiveness
  • Detailed system description: Clearly documents service architecture, boundaries, tenant isolation, and data flows
  • Comprehensive CUECs: Well-defined customer responsibilities that demonstrate mature shared responsibility understanding
  • Minimal exceptions: Zero exceptions is ideal; any exceptions must include clear remediation plans
  • Recognized CPA firm: Reports from established audit firms carry more credibility

Common Report Weaknesses

How do you build a Report That Withstands Scrutiny? — comparison
WeaknessImpact on CustomersHow to Avoid
Missing Availability criterionCustomers cannot reference your report for availability-related controlsInclude Availability from your first Type II audit
Vague CUECsCustomer auditors cannot determine responsibility boundariesWrite specific, actionable CUECs with implementation guidance
Depends on scope and readinessDownstream auditors may question control sustainabilityUse six-month minimum; twelve-month preferred
Significant exceptions in access managementRaises concerns about multi-tenant isolationPrioritize access management controls and quarterly access reviews
Depends on scope and readinessCustomers cannot use an expired report for their current auditMaintain annual audit cycle without gaps

AICPA & CIMA’s SOC overview describes CPA assurance services. It defines the assurance context; it does not establish vendor rankings, market prices, or a particular company’s readiness.

Frequently Asked Questions

What is Subservice Organization Model?
When your customers undergo their own SOC 2 audits, they must address how they rely on third-party infrastructure providers. You are a "subservice organization" in SOC 2 terminology — an organization that provides services to a service organization (your customer), which in turn provides services to its own customers (end users).
Which Trust Service Criteria should an infrastructure provider include?
More than a typical SaaS company. Security is mandatory and Availability is effectively expected given uptime commitments. Confidentiality and Processing Integrity are commonly added because downstream auditors rely on your report for their own engagements.
What are complementary user entity controls?
Controls your customers must implement on their side for the overall control objective to be met. They belong in your report because they define the boundary of your responsibility, and downstream auditors read them closely.
Tyler Carbone

Tyler Carbone

Managing Director and Cofounder

Tyler Carbone is a Managing Director and Cofounder of Agency and one of the industry's leading voices on governance, risk, and compliance. He holds degrees from Harvard and a JD/MBA from the University of Virginia, and previously worked in cybersecurity at Deloitte. Tyler has helped hundreds of companies operate SOC 2, ISO 27001, HIPAA, and GDPR programs.

LinkedIn

Related Reading

Stay ahead of compliance

Expert insights on cybersecurity compliance delivered to your inbox.

We respect your privacy. Unsubscribe anytime.