AWS and Microsoft Azure each hold their own SOC 2 reports covering the infrastructure they operate. Those reports do not extend to what you build on top. In your SOC 2 report, the cloud provider is a subservice organization, normally carved out, and you remain responsible for configuration, access, data, change management and monitoring.
Key takeaways
- “We run on AWS” answers the physical security question and little else.
- The provider’s report is evidence for your vendor monitoring, not a substitute for your controls.
- Most cloud-related findings are configuration and access issues on the customer side.
- Evidence can be pulled directly from cloud consoles and APIs, which auditors prefer to screenshots.
Who is responsible for what
| Area | Cloud provider | You |
|---|---|---|
| Data center physical security | Yes | No |
| Hardware, hypervisor, core network | Yes | No |
| Identity and access configuration | Provides the service | Who has access, MFA, least privilege, key rotation |
| Network configuration | Provides the service | Security groups, exposure, segmentation |
| Encryption | Provides the capability | Turning it on, key management choices |
| Logging and monitoring | Provides the services | Enabling, retaining, alerting, reviewing |
| Backups and recovery | Provides the capability | Configuring, testing restores |
| Application code and change management | No | Yes |
| Customer data handling | No | Yes |
How the provider appears in your report
Your system description names the provider and the services used, states that it is carved out, and lists the complementary subservice organization controls you assume, such as physical access and environmental protection. See subservice organizations and CUECs and CSOCs explained.
Monitoring the provider
At least annually, obtain the provider’s current SOC 2 report (AWS Artifact, or the Microsoft Service Trust Portal), read the opinion and exceptions, and check that the user controls it lists are in place in your account. Record the review. See vendor management for SOC 2.
Evidence auditors commonly request
- Identity configuration: users, roles, MFA status, root or global administrator protections.
- Audit logging enabled and retained across accounts or subscriptions.
- Encryption settings for storage and databases.
- Network exposure: public endpoints and firewall rules.
- Infrastructure-as-code change history tied to approvals.
- Backup configuration and a restoration test.
Frequently asked questions
Does using only managed services reduce my scope?
It shifts some operational controls to the provider, but configuration and access remain yours.
Is Google Cloud treated differently?
No. The same model applies.
Do we need the provider’s SOC 1?
Only if your own report is a SOC 1.
Sources & further reading
AWS and Microsoft shared responsibility documentation; AICPA SOC 2 Guide.
Related: How to scope systems for SOC 2, SOC 2 for SaaS, Audit evidence management.
Work with a licensed CPA firm
Auditsuisse Assurance NA PC is a licensed US CPA firm enrolled in the AICPA Peer Review Program. See our published SOC 2 fees or book a scoping call.