SOC 2
Evidence that your cloud controls work, not just that they exist.
Updated
SOC 2 is an attestation report defined by the AICPA. An independent auditor examines your controls against the Trust Services Criteria: Security, which every report must cover, plus Availability, Processing Integrity, Confidentiality and Privacy as you choose to include them.
A Type I report says the controls were designed properly at a point in time. A Type II report, the one most customers ask for, says they operated effectively over a period of three to twelve months. That is where cloud configuration gets hard: you have to show the state of your infrastructure throughout the window, not just on audit day.
Who needs it
SaaS and infrastructure companies selling to other businesses, especially in the United States, and any team whose customers send security questionnaires. It is usually the first formal attestation a growing company obtains.
What the auditor wants from your cloud
The Security criteria ask for logical access controls, network boundaries, encryption of data in transit and at rest, detection of changes and vulnerabilities, and a change-management process. Auditors expect configuration evidence for each: exports or reports that show the control in place and, for Type II, that it stayed in place.
Point-in-time versus continuous
The usual approach is a scramble before the audit window closes. A review that runs on a schedule, flags drift and keeps an audit trail turns that into a by-product of normal operations: every review is dated evidence, and every fix is a recorded change.
What SOC 2 asks of your cloud
The control areas that map onto infrastructure configuration in AWS, Google Cloud and Azure.
CC6 · Logical and physical access
Who and what can reach your systems and data: identity, authentication, authorisation, network boundaries, and encryption in transit and at rest.
CC7 · System operations
Detecting configuration changes, vulnerabilities and anomalies; monitoring; responding to and recovering from incidents.
CC8 · Change management
Infrastructure changes are authorised, tested, documented and traceable, including the changes made to fix findings.
A1 · Availability
When in scope: backups, recovery objectives and capacity, for example database snapshots and multi-zone deployment.
C1 · Confidentiality
When in scope: confidential data is identified, protected and disposed of, which in the cloud mostly comes down to storage access, encryption and retention settings.
How AKRIBOS checks SOC 2
Mapped to your resources
Every SOC 2 control is evaluated against the actual accounts, roles, networks and storage in your estate, with the setting behind each result.
Findings come with the fix
A failing control is shown with the exact change as CLI commands or Terraform. You review and approve; nothing is applied on its own.
Evidence over time
Scheduled reviews and a full audit trail give you a dated record of each control for the whole audit period, not just the day of the audit.
Common issues under SOC 2
Misconfigurations that fail SOC 2 controls, with the control reference for each.
Storage bucket open to the internet
CriticalObject storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.CC6.1 (logical access to data) and CC6.6 (boundaries against external threats).
Read moreRoot or owner account without MFA
CriticalThe most privileged identity in the account protected by a password alone.CC6.1 (authentication of users) and CC6.3 (privileged access).
Read moreDatabase reachable from the internet
CriticalA managed database with a public address and a firewall that lets the world in.CC6.1 (access to data) and CC6.6 (network boundaries).
Read moreSnapshots or machine images shared publicly
CriticalDisk snapshots, database snapshots or machine images that anyone with a cloud account can copy.CC6.1 (logical access to data) and CC6.6 (external boundaries).
Read moreOver-permissive IAM policies
HighIdentities, often service accounts, that can do anything in the account because a wildcard or a basic role was easier than a scoped policy.CC6.1 (authorisation), CC6.3 (least privilege and role changes).
Read moreSSH or RDP open to 0.0.0.0/0
HighManagement ports reachable from any address on the internet.CC6.6 (network boundaries and external threats).
Read moreAudit logging incomplete
HighGaps in the record of who did what: missing regions, missing data-access events, or logs that can be altered.CC7.2 (monitoring for anomalies) and CC7.3 (evaluating security events).
Read moreLong-lived or unused credentials
HighAccess keys, service account keys and client secrets that never rotate and are no longer needed.CC6.1 (credential management) and CC6.2 (removal of access).
Read moreInstance metadata without session tokens
HighCompute instances that answer metadata requests, including their temporary credentials, to any process that can reach the local metadata address.CC6.1 (protection of credentials) and CC7.1 (vulnerability management).
Read moreTrust policies open to any account
HighRoles or bindings that let identities outside your organisation assume access, often for a vendor integration that was set up too generously.CC6.1 (authorisation) and CC6.3 (access by third parties), CC9.2 (vendor risk).
Read moreData at rest without the encryption you intended
MediumVolumes, snapshots or databases created without encryption, or without the customer-managed keys your policy requires.CC6.1 (protection of data at rest) and C1.1 (confidential information) when Confidentiality is in scope.
Read moreTransport encryption not enforced
MediumEndpoints that still accept plaintext or outdated TLS, even though an encrypted path exists.CC6.7 (transmission of data).
Read moreNetwork flow logs off
MediumNo record of which addresses talked to which, so traffic to and from a compromised host cannot be reconstructed.CC7.2 (monitoring for anomalies).
Read moreDefault network with permissive rules
MediumWorkloads running in the cloud-created default network, which ships with rules nobody would write deliberately.CC6.6 (network boundaries).
Read moreSOC 2 questions
Does using AKRIBOS make us SOC 2 compliant?
No tool does. SOC 2 covers people, policies and vendors as well as technology. AKRIBOS covers the cloud configuration part of the Security criteria and gives you dated evidence for it; the rest of the programme is still yours.
Type I or Type II?
Type I is quicker and proves design. Most enterprise customers ask for Type II, which proves operation over time, so plan for continuous evidence from the start.
Which Trust Services Criteria apply to cloud infrastructure?
Mainly the Security common criteria, in particular CC6 (access), CC7 (operations) and CC8 (change management). Availability and Confidentiality add backup, recovery and data-protection controls when they are in scope.
How do we show evidence for a whole audit period?
Run reviews on a schedule and keep the results. Each review is a timestamped record of the state of your controls, and the audit trail shows who changed what in between.
Other frameworks
CIS Benchmarks
The baseline configuration standard for AWS, Google Cloud and Azure.
Read moreISO/IEC 27001
The international standard for an information security management system, applied to your cloud.
Read moreDORA
The EU Digital Operational Resilience Act, applied to the cloud behind your financial services.
Read moreNIS2
EU-wide cyber risk-management obligations for essential and important entities.
Read morePCI DSS v4
Requirements for every environment that stores, processes or transmits cardholder data.
Read moreNIST CSF 2.0
The US framework of outcomes: Govern, Identify, Protect, Detect, Respond, Recover.
Read moreBSI C5
Germany's cloud computing compliance criteria catalogue.
Read moreDNB Good Practice Information Security
What De Nederlandsche Bank expects of the financial institutions it supervises.
Read moreAttackers don't wait for your next audit. Neither does AKRIBOS.
Connect AWS, Google Cloud or Azure and get your first review today.
