Trust Principles
SOC2 rules are organized into five trust service criteria:Security
Protection against unauthorized access, disclosure, or damage (Common Criteria)
Availability
Systems are available for operation and use as committed
Confidentiality
Information designated as confidential is protected as committed
Processing Integrity
System processing is complete, valid, accurate, and authorized
Privacy
Personal information is collected, used, retained, disclosed, and disposed of appropriately
Detailed Rule Reference
Security (Common Criteria)
SOC2-CC6.1-001 - Logical Access Control (MFA)
SOC2-CC6.1-001 - Logical Access Control (MFA)
Severity: CRITICAL
Control: CC6.1 — Logical Access SecurityWhat it detects:Identifies accounts with access to PII or sensitive data that do not have multi-factor authentication enabled.Conditions:Policy Excerpt:
Control: CC6.1 — Logical Access SecurityWhat it detects:Identifies accounts with access to PII or sensitive data that do not have multi-factor authentication enabled.Conditions:
Access to sensitive data must be protected by multi-factor authentication.Historical Context:
- Average Fine: $4.88M (Average cost of credential-based breach)
- Breach Example: Uber 2022 — Contractor account without MFA allowed internal network pivot
SOC2-CC6.2-001 - Credential Leakage Detection
SOC2-CC6.2-001 - Credential Leakage Detection
Severity: CRITICAL
Control: CC6.2 — User Access ManagementWhat it detects:Detects API keys, passwords, or secret tokens stored in non-secure database columns or code repositories.Conditions:Policy Excerpt:
Control: CC6.2 — User Access ManagementWhat it detects:Detects API keys, passwords, or secret tokens stored in non-secure database columns or code repositories.Conditions:
Controls should prevent unauthorized use of credentials.Historical Context:
- Average Fine: $2M (Average cost of secret key exposure in public repositories/DBs)
- Breach Example: Twitter 2023 — Private keys leaked in source code allowed API takeover
SOC2-CC6.3-001 - Termination of Access
SOC2-CC6.3-001 - Termination of Access
Severity: MEDIUM
Control: CC6.3 — User Access ModificationWhat it detects:Identifies records where an “inactive” or “terminated” user still has active write permissions.Conditions:Policy Excerpt:
Control: CC6.3 — User Access ModificationWhat it detects:Identifies records where an “inactive” or “terminated” user still has active write permissions.Conditions:
Access is modified or terminated in a timely manner.Historical Context:
- Average Fine: $150k (Common administrative fine for failed access reviews)
- Breach Example: Terminated employee used valid credentials to delete production databases
SOC2-CC7.1-001 - Audit Trail & Logging
SOC2-CC7.1-001 - Audit Trail & Logging
Severity: HIGH
Control: CC7.1 — System MonitoringWhat it detects:Identifies administrative actions or data access events not captured in audit logs.Conditions:Policy Excerpt:
Control: CC7.1 — System MonitoringWhat it detects:Identifies administrative actions or data access events not captured in audit logs.Conditions:
Monitoring activities must be performed to identify anomalies.Historical Context:
- Average Fine: $1.2M (Cost increase when detection/containment exceeds 200 days)
- Breach Example: Company unable to determine extent of breach due to disabled database logs
Availability
SOC2-CC9.1-001 - Business Continuity (Backups)
SOC2-CC9.1-001 - Business Continuity (Backups)
Severity: HIGH
Control: CC9.1 — Business ContinuityWhat it detects:Alerts when critical data has not been backed up in the last 24 hours.Conditions:Policy Excerpt:
Control: CC9.1 — Business ContinuityWhat it detects:Alerts when critical data has not been backed up in the last 24 hours.Conditions:
The entity protects the system against environmental risks.Historical Context:
- Average Fine: $5.1M (Average cost of ransomware data loss)
- Breach Example: Cloud service provider lost 2 weeks of customer data during cluster failure
Confidentiality
SOC2-CC6.7-001 - Encryption of Data at Rest
SOC2-CC6.7-001 - Encryption of Data at Rest
Severity: HIGH
Control: CC6.7 — Protection of InformationWhat it detects:Identifies databases or tables containing PII stored in plaintext (not encrypted at rest).Conditions:Policy Excerpt:
Control: CC6.7 — Protection of InformationWhat it detects:Identifies databases or tables containing PII stored in plaintext (not encrypted at rest).Conditions:
The entity protects confidential information during its processing lifecycle.Historical Context:
- Average Fine: $18M (British Airways breach — lack of security measures)
- Breach Example: Unencrypted S3 buckets exposed 100M+ user records in plain text
SOC2-CC5.2-001 - Data Residency Compliance
SOC2-CC5.2-001 - Data Residency Compliance
Severity: MEDIUM
Control: CC5.2 — Communication and InformationWhat it detects:Verifies that EU customer data is not being processed or stored in unauthorized regions (e.g., outside EEA).Conditions:Policy Excerpt:
Control: CC5.2 — Communication and InformationWhat it detects:Verifies that EU customer data is not being processed or stored in unauthorized regions (e.g., outside EEA).Conditions:
Entity communicates privacy objectives to internal and external parties.Historical Context:
- Average Fine: €1.2B (Meta — transferring data to US without valid basis)
- Breach Example: French health data host fined for using non-EU cloud providers without consent
Processing Integrity
SOC2-CC6.1-002 - Tenant Data Isolation
SOC2-CC6.1-002 - Tenant Data Isolation
Severity: CRITICAL
Control: CC6.1 — Logical Access SecurityWhat it detects:Checks for rows in a customer export that contain data from other tenants (cross-tenant data leak).Conditions:Policy Excerpt:
Control: CC6.1 — Logical Access SecurityWhat it detects:Checks for rows in a customer export that contain data from other tenants (cross-tenant data leak).Conditions:
Customer data must be logically isolated from other customers.Historical Context:
- Average Fine: $3.5M (Average fine for cross-tenant data leak)
- Breach Example: SaaS provider leaked private reports to competitors due to query logic error
Privacy
SOC2-P1.1-001 - Data Retention Policy
SOC2-P1.1-001 - Data Retention Policy
Severity: MEDIUM
Control: P1.1 — Privacy CriteriaWhat it detects:Identifies data that has exceeded the standard 7-year legal retention period.Conditions:Policy Excerpt:
Control: P1.1 — Privacy CriteriaWhat it detects:Identifies data that has exceeded the standard 7-year legal retention period.Conditions:
Personal information is retained for only as long as necessary.Historical Context:
- Average Fine: $1M (Sears — retaining customer tracking data post-consent withdrawal)
- Breach Example: Startup failing audit because “Deleted Users” table still contained full PII from 2016
Rule Summary Table
| Rule ID | Name | Severity | Control | Trust Principle |
|---|---|---|---|---|
| SOC2-CC6.1-001 | Logical Access Control (MFA) | CRITICAL | CC6.1 | Security |
| SOC2-CC6.1-002 | Tenant Data Isolation | CRITICAL | CC6.1 | Processing Integrity |
| SOC2-CC6.7-001 | Encryption of Data at Rest | HIGH | CC6.7 | Confidentiality |
| SOC2-CC7.1-001 | Audit Trail & Logging | HIGH | CC7.1 | Security |
| SOC2-CC9.1-001 | Business Continuity (Backups) | HIGH | CC9.1 | Availability |
| SOC2-CC6.2-001 | Credential Leakage Detection | CRITICAL | CC6.2 | Security |
| SOC2-CC6.3-001 | Termination of Access | MEDIUM | CC6.3 | Security |
| SOC2-CC5.2-001 | Data Residency Compliance | MEDIUM | CC5.2 | Confidentiality |
| SOC2-P1.1-001 | Data Retention Policy | MEDIUM | P1.1 | Privacy |
Trust Principle Coverage
Security (Common Criteria)
Security (Common Criteria)
4 Rules — MFA enforcement, credential leakage detection, access termination, audit loggingSecurity is the foundational trust principle required for all SOC2 audits. These rules ensure:
- Multi-factor authentication for sensitive data access
- No hardcoded credentials or leaked API keys
- Timely revocation of access for terminated users
- Comprehensive audit trails for all administrative actions
Availability
Availability
1 Rule — Business continuity (backup validation)Ensures systems are available for operation and use as committed:
- Critical data backed up within 24 hours
- Protection against data loss from ransomware or system failures
Confidentiality
Confidentiality
2 Rules — Encryption at rest, data residency complianceProtects confidential information designated as sensitive:
- PII encrypted at rest in all databases
- Data stored only in authorized geographic regions
Processing Integrity
Processing Integrity
1 Rule — Tenant data isolationEnsures system processing is complete, valid, accurate, and authorized:
- Multi-tenant SaaS applications prevent cross-tenant data leaks
- Data exports contain only records belonging to the requesting customer
Privacy
Privacy
1 Rule — Data retention policyEnsures personal information is appropriately managed throughout its lifecycle:
- Data not retained beyond legal or business requirements (7-year default)
- Automated purge for records exceeding retention period
Using the SOC2 Pack
- Select SOC2 Framework — Choose “SOC2” when creating a new audit
- Choose Trust Principles — All 9 rules are loaded; toggle rules based on your SOC2 scope (Type I vs Type II)
- Upload Data — Upload your system access logs, user database, or configuration exports
- Confirm Mapping — Map your columns to fields like
mfa_enabled,is_encrypted,tenant_id, etc. - Run Scan — Execute the compliance scan
- Review Violations — Violations include Common Criteria references and breach cost estimates
SOC2 audits typically focus on controls rather than raw data scans. Use Yggdrasil’s SOC2 pack to validate that your data layer adheres to the Common Criteria controls before your formal audit.
SOC2 Type I vs Type II
| Audit Type | Scope | Yggdrasil Use Case |
|---|---|---|
| Type I | Design effectiveness at a point in time | Run a one-time scan to validate controls are in place |
| Type II | Operating effectiveness over 6-12 months | Run periodic scans and track score history to demonstrate continuous compliance |
Next Steps
AML Compliance Pack
Explore the 11 AML/FinCEN rules for financial transaction monitoring
GDPR Compliance Pack
Explore the 15 GDPR rules for data protection compliance
Custom PDF Upload
Upload your own regulatory documents
Confidence Scoring
Learn how violations are scored and ranked