Audit Insights & Preparation

Does SOC 2 Require Encryption? What the Criteria Say

Tyler Carbone
Published Updated 9 min read

SOC 2 is fundamentally principle-based, meaning it defines what you must achieve (data protection) rather than how you must achieve it (specific encryption standards). This contrasts with prescriptive frameworks like PCI DSS, which specify exact encryption algorithms and key management procedures.

Key Takeaways

  • •SOC 2 is fundamentally principle-based, meaning it defines what you must achieve (data protection) rather than how you must achieve it (specific encryption standards).
  • •For the next operating decision, compare SOC 2 compliance for startups with policies needed for SOC 2.
  • •The Trust Service Criteria use language like "appropriate controls" and "suitable design" rather than specifying encryption.

This guide explains what the Trust Service Criteria actually say about encryption, what auditors evaluate in practice, the minimum encryption standards expected, and how to document your encryption approach for SOC 2.

For the next operating decision, compare SOC 2 compliance for startups with policies needed for SOC 2. Confirm the work included, the evidence you need, and who will own implementation before committing to a provider.

What the Trust Service Criteria Say?

Principle-Based vs Prescriptive

What the Trust Service Criteria Say? — comparison
Framework ApproachSOC 2PCI DSS
Encryption requirementProtect data from unauthorized access and disclosureEncrypt cardholder data with strong cryptography (specific algorithms listed)
Algorithm specificationNone — auditor evaluates whether your approach is appropriateAES-128/256, RSA 2048+, specific protocols listed
Key managementControls for managing cryptographic keys (principle-based)Specific key rotation schedules, split knowledge, dual control
Protocol specificationNone — auditor evaluates whether protocols are currentTLS 1.2+ explicitly required; older protocols prohibited

Relevant Trust Service Criteria Points

What the Trust Service Criteria Say? — comparison
Criteria PointWhat It SaysHow Encryption Relates
CC6.1 — Logical access securityThe entity implements logical access security over information assetsEncryption protects data from unauthorized access even if other access controls are bypassed
CC6.7 — Data transmission controlsThe entity restricts the transmission of data to authorized usersEncryption in transit (TLS) ensures data transmitted over networks is protected
C1.1 — Confidentiality of informationConfidential information is identified and protected from unauthorized accessEncryption is a primary control for protecting confidential information at rest and in transit
C1.2 — Disposal of confidential informationConfidential information is disposed of in a manner that protects against unauthorized accessEncryption supports secure disposal (encrypted data is unreadable without keys)
A1.2 — Environmental protectionThe entity protects system components from environmental threatsEncryption at rest protects data if physical media is compromised

The "Appropriate Controls" Standard

The Trust Service Criteria use language like "appropriate controls" and "suitable design" rather than specifying encryption. This means your auditor evaluates whether your data protection approach — which almost always includes encryption — is reasonable and effective given your risk profile. In our experience, an organization that stores customer data without encryption at rest would need an exceptionally strong alternative control to demonstrate appropriate data protection, and in practice, no alternative is as universally accepted as encryption.

What Auditors Actually Evaluate?

Encryption at Rest

Encryption at rest protects stored data from unauthorized access if physical media, backup files, or database snapshots are compromised.

What Auditors Actually Evaluate? — comparison
What Auditors CheckExpected EvidenceCommon Implementation
Database encryptionConfiguration evidence showing encryption is enabled for databases storing customer dataAWS RDS encryption, GCP Cloud SQL encryption, Azure SQL TDE
Storage encryptionEvidence that storage volumes and object storage are encryptedAWS S3 default encryption, EBS encryption, GCP Cloud Storage encryption
Backup encryptionEvidence that backups are encryptedEncrypted backup configurations, KMS-managed backup keys
Encryption algorithmVerification that the algorithm is current and appropriateAES-256 is the standard expectation; AES-128 is acceptable
Key managementEvidence that encryption keys are managed securelyCloud KMS (AWS KMS, GCP Cloud KMS, Azure Key Vault), key rotation policies
Laptop/endpoint encryptionEvidence that employee devices are encryptedFileVault (macOS), BitLocker (Windows), MDM enforcement evidence

Encryption in Transit

Encryption in transit protects data as it moves between systems, from users to your application, and between internal services.

What Auditors Actually Evaluate? — comparison
What Auditors CheckExpected EvidenceCommon Implementation
HTTPS enforcementEvidence that all public-facing endpoints use HTTPSTLS certificate configuration, HTTP-to-HTTPS redirect, HSTS headers
TLS versionVerification that current TLS versions are usedTLS 1.2 minimum; TLS 1.3 preferred; older versions (TLS 1.0, 1.1, SSL) disabled
Internal service communicationEvidence that internal service-to-service communication is encryptedService mesh TLS, internal TLS certificates, VPN for cross-network communication
API encryptionEvidence that API communications are encryptedHTTPS for all API endpoints, mutual TLS for sensitive service-to-service APIs
Database connectionsEvidence that database connections use encryptionSSL/TLS enforcement for database client connections
Email encryptionEvidence that email communication uses encryption where appropriateTLS for email transport (STARTTLS), encrypted email for sensitive communications

Key Management

Key management is where auditors often find deficiencies, even when encryption itself is implemented correctly.

What Auditors Actually Evaluate? — comparison
Key Management ControlWhat Auditors EvaluateBest Practice
Key storageWhere encryption keys are stored and how they are protectedCloud KMS (hardware-backed), never stored alongside encrypted data
Key rotationWhether keys are rotated periodicallyAnnual rotation minimum; automated rotation preferred
Access to keysWho can access encryption keys and how access is controlledRestricted to authorized personnel; IAM policies limit access
Key backup and recoveryWhether keys can be recovered if primary access is lostKey recovery procedures documented; tested periodically
Separation of dutiesWhether the same person who manages data also manages keysSeparate roles for data administration and key management where feasible
Key lifecycleHow keys are created, distributed, stored, rotated, and eventually destroyedDocumented key lifecycle procedures covering all stages

What encryption standards should your risk assessment consider?

Industry-Standard Encryption Expectations

While SOC 2 does not mandate specific standards, the following represent what auditors and enterprise customers expect as baseline encryption implementation.

What encryption standards should your risk assessment consider? — comparison
Encryption AreaMinimum ExpectedPreferredUnacceptable
Data at rest algorithmAES-128AES-256DES, 3DES, RC4, no encryption
Data in transit protocolTLS 1.2TLS 1.3TLS 1.0, TLS 1.1, SSL 3.0, no encryption
Key managementCloud-managed KMSHSM-backed KMS with automatic rotationKeys stored in application code, shared keys, no key management
Endpoint encryptionFull disk encryption (FileVault/BitLocker)Full disk encryption enforced via MDM with compliance monitoringNo endpoint encryption, self-managed without enforcement
Database encryptionCloud-native encryption at rest enabledCloud KMS with customer-managed keys (CMK)No database encryption, deprecated algorithms
Backup encryptionEncrypted backups using same or stronger encryption as sourceEncrypted backups with separate key managementUnencrypted backups, backups accessible without encryption

What "AES-256" Means for SOC 2

AES-256 (Advanced Encryption Standard with 256-bit key length) has become the de facto standard for data at rest encryption in SOC 2 environments. While AES-128 is technically sufficient and not considered weak by current cryptographic standards, AES-256 is what enterprise customers expect and what most cloud provider default encryption uses. Implementing AES-256 is straightforward when using cloud provider encryption services, as it is typically the default configuration.

What "TLS 1.2+" Means for SOC 2

TLS 1.2 is the minimum acceptable protocol version for data in transit. TLS 1.3, released in 2018, offers improved security and performance and is increasingly expected. Older versions (TLS 1.0, TLS 1.1) are considered insecure and should be disabled. Auditors will check your TLS configuration and may flag systems that support older protocol versions even if newer versions are also supported.

Documenting Your Encryption Approach

What to Include in Your System Description

Your SOC 2 report's system description should clearly document your encryption approach.

Documenting Your Encryption Approach — comparison
Documentation ElementContentExample
Encryption at rest overviewGeneral description of encryption for stored data"All customer data at rest is encrypted using AES-256 encryption managed through AWS KMS"
Encryption in transit overviewGeneral description of encryption for data transmission"All data in transit is encrypted using TLS 1.2 or higher; TLS 1.0 and 1.1 are disabled"
Key management approachHow encryption keys are managed"Encryption keys are managed through AWS KMS with automatic annual rotation"
Scope of encryptionWhat data is encrypted and where"Encryption applies to all production databases, object storage, backups, and inter-service communication"
Endpoint encryptionHow employee devices are encrypted"All company-managed devices are encrypted using FileVault (macOS) or BitLocker (Windows), enforced through MDM"

Policies to Create or Update

Documenting Your Encryption Approach — comparison
PolicyEncryption-Related Content
Information Security PolicyHigh-level statement on data protection including encryption requirements
Data Classification PolicyClassification levels with corresponding encryption requirements per level
Encryption Policy (dedicated)Detailed encryption standards, algorithms, protocols, key management procedures
Key Management ProceduresSpecific procedures for key creation, rotation, storage, access, and destruction
Acceptable Use PolicyRequirements for endpoint encryption and secure data handling

Evidence to Maintain

Documenting Your Encryption Approach — comparison
Evidence TypeSourceCollection Frequency
Database encryption configurationCloud provider console or APIContinuous via GRC platform integration
Storage encryption configurationCloud provider console or APIContinuous via GRC platform integration
TLS configurationSSL Labs scan, load balancer configurationMonthly or continuous via monitoring tool
Key rotation recordsKMS audit logs showing key rotation eventsAnnual or per rotation schedule
MDM encryption complianceEndpoint management platformContinuous via GRC platform integration
Disabled protocol evidenceLoad balancer or web server configuration showing old TLS versions disabledAfter configuration changes; periodic verification

Common Encryption Findings in SOC 2 Audits

What Auditors Commonly Flag

Common Encryption Findings in SOC 2 Audits — comparison
FindingRoot CausePrevention
TLS 1.0/1.1 still enabledLegacy compatibility not removed; default configurations not hardenedDisable legacy TLS versions proactively; test for compatibility impact
Unencrypted database connectionsDatabase SSL enforcement not configured; applications connecting without encryptionEnable SSL enforcement on database servers; require encrypted connections
No key rotation evidenceKey rotation not configured or not documentedConfigure automatic key rotation in KMS; document rotation schedule
Unencrypted backupsBackup encryption not enabled by default; overlooked during configurationEnable encryption for all backup services; verify backup encryption status
Endpoint encryption gapsSome devices not enrolled in MDM; BYOD devices without encryption requirementsEnforce MDM enrollment; require encryption for all devices accessing company data
Missing encryption for internal trafficService-to-service communication within VPC not encryptedImplement service mesh TLS or internal certificate management

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

Does SOC 2 mandate a specific encryption standard?
No. SOC 2 is principle-based: it defines what you must achieve rather than how. The Trust Service Criteria never name an algorithm or key length, which is why two companies can both pass with materially different encryption implementations.
Is encryption effectively required for SOC 2 in practice?
Yes. Although no criterion prescribes it, meeting the confidentiality and logical access criteria without encryption at rest and in transit is not realistic, so auditors expect it and treat its absence as a finding.
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.