SOC 2 Compliance
SOC 2 (Service Organization Control 2) is a framework for managing customer data based on five Trust Services Criteria. Cloudgeni helps you achieve and maintain SOC 2 compliance across your cloud infrastructure.SOC 2 Coverage
- 200+ automated checks across AWS, Azure, and GCP
- All 5 Trust Services Criteria covered
- Continuous monitoring with real-time alerts
- Audit-ready reports for Type I and Type II audits
Trust Services Criteria
Security (Common Criteria)
The security principle addresses protection against unauthorized access.| Control Area | Cloudgeni Checks |
|---|---|
| Access Control | IAM policies, MFA enforcement, least privilege |
| Network Security | Security groups, NACLs, firewall rules |
| Encryption | Data at rest, data in transit, key management |
| Logging | Audit trails, CloudTrail, activity logs |
| Vulnerability Management | Security scanning, patch management |
soc2_cc6_1- Logical access controls implementedsoc2_cc6_2- Authentication mechanisms enforcedsoc2_cc6_3- Access removal upon terminationsoc2_cc6_6- System boundaries protected
Availability
The availability principle ensures systems are operational and accessible.| Control Area | Cloudgeni Checks |
|---|---|
| Redundancy | Multi-AZ deployments, load balancing |
| Backup | Automated backups, retention policies |
| Disaster Recovery | Cross-region replication, failover |
| Monitoring | Health checks, uptime monitoring |
| Capacity | Auto-scaling, resource planning |
soc2_a1_1- Capacity management implementedsoc2_a1_2- Environmental protections in placesoc2_a1_3- Recovery procedures documented
Processing Integrity
The processing integrity principle ensures system processing is complete, accurate, and authorized.| Control Area | Cloudgeni Checks |
|---|---|
| Data Validation | Input validation, data integrity checks |
| Error Handling | Exception handling, error logging |
| Processing Controls | Transaction logging, reconciliation |
| Quality Assurance | Testing procedures, change validation |
soc2_pi1_1- Processing integrity policies definedsoc2_pi1_2- System inputs validatedsoc2_pi1_3- Processing monitored for completeness
Confidentiality
The confidentiality principle protects information designated as confidential.| Control Area | Cloudgeni Checks |
|---|---|
| Data Classification | Tagging, labeling requirements |
| Encryption | Encryption at rest and in transit |
| Access Restrictions | Role-based access, data isolation |
| Data Retention | Retention policies, secure deletion |
soc2_c1_1- Confidential information identifiedsoc2_c1_2- Confidential information protectedsoc2_c1_3- Disposal procedures implemented
Privacy
The privacy principle addresses collection, use, and disposal of personal information.| Control Area | Cloudgeni Checks |
|---|---|
| Data Collection | Consent management, purpose limitation |
| Data Use | Access controls, use restrictions |
| Data Retention | Retention schedules, deletion |
| Data Disclosure | Third-party sharing controls |
soc2_p1_1- Privacy notice providedsoc2_p2_1- Personal information collected with consentsoc2_p3_1- Personal information used as disclosed
Control Mapping
CC1 - Control Environment
| Control | Description | AWS Check | Azure Check |
|---|---|---|---|
| CC1.1 | COSO principles | Organizational policies | Resource tagging |
| CC1.2 | Board oversight | IAM governance | Azure AD governance |
| CC1.3 | Management philosophy | Security policies | Compliance policies |
CC2 - Communication and Information
| Control | Description | AWS Check | Azure Check |
|---|---|---|---|
| CC2.1 | Internal communication | SNS topics | Service Bus |
| CC2.2 | External communication | API Gateway | API Management |
| CC2.3 | Security awareness | Training records | Training records |
CC3 - Risk Assessment
| Control | Description | AWS Check | Azure Check |
|---|---|---|---|
| CC3.1 | Risk objectives | Security Hub | Defender for Cloud |
| CC3.2 | Risk identification | GuardDuty | Sentinel |
| CC3.3 | Fraud consideration | CloudTrail | Activity Log |
CC4 - Monitoring Activities
| Control | Description | AWS Check | Azure Check |
|---|---|---|---|
| CC4.1 | Ongoing evaluation | Config Rules | Azure Policy |
| CC4.2 | Internal assessments | Inspector | Defender scans |
| CC4.3 | Deficiency evaluation | Security findings | Security alerts |
CC5 - Control Activities
| Control | Description | AWS Check | Azure Check |
|---|---|---|---|
| CC5.1 | Control selection | Security groups | NSGs |
| CC5.2 | Technology controls | WAF, Shield | Application Gateway |
| CC5.3 | Policy deployment | SCPs | Management Groups |
CC6 - Logical and Physical Access
| Control | Description | AWS Check | Azure Check |
|---|---|---|---|
| CC6.1 | Logical access | IAM policies | Azure RBAC |
| CC6.2 | Authentication | MFA enabled | Conditional Access |
| CC6.3 | Access removal | IAM audit | Access reviews |
| CC6.6 | System boundaries | VPC isolation | VNet isolation |
| CC6.7 | Data transmission | TLS/SSL | TLS/SSL |
| CC6.8 | Malicious software | GuardDuty | Defender |
CC7 - System Operations
| Control | Description | AWS Check | Azure Check |
|---|---|---|---|
| CC7.1 | Vulnerability detection | Inspector | Defender |
| CC7.2 | Anomaly detection | GuardDuty | Sentinel |
| CC7.3 | Security evaluation | Security Hub | Security Center |
| CC7.4 | Incident response | CloudWatch Alarms | Azure Monitor |
CC8 - Change Management
| Control | Description | AWS Check | Azure Check |
|---|---|---|---|
| CC8.1 | Infrastructure changes | CloudTrail | Activity Log |
| CC8.2 | Software changes | CodePipeline | DevOps |
| CC8.3 | Emergency changes | Change tracking | Change tracking |
CC9 - Risk Mitigation
| Control | Description | AWS Check | Azure Check |
|---|---|---|---|
| CC9.1 | Risk mitigation | Security Hub | Defender |
| CC9.2 | Vendor management | Third-party audit | Third-party audit |
Getting Compliant
Step 1: Run SOC 2 Assessment
- Go to Compliance in Cloudgeni dashboard
- Select SOC 2 framework
- Click Run Assessment
- Review findings by control
Step 2: Prioritize Remediation
Focus on high-impact controls first:| Priority | Control Area | Impact |
|---|---|---|
| 1 | Access Control (CC6) | Critical - protects all data |
| 2 | Logging (CC7) | Critical - audit trail |
| 3 | Encryption (CC6.7) | High - data protection |
| 4 | Change Management (CC8) | Medium - operational |
Step 3: Remediate Findings
For each finding:- Click Remediate to generate fix
- Review generated IaC code
- Create pull request
- Merge and verify with re-scan
Step 4: Generate Audit Report
- Go to Compliance → SOC 2
- Click Generate Report
- Select date range and filters
- Download PDF for auditors
Continuous Compliance
Automated Monitoring
Cloudgeni continuously monitors your infrastructure:- Real-time detection of configuration changes
- Automatic re-assessment on resource changes
- Drift alerts when compliance degrades
- Trend tracking over time
Compliance Score
Track your SOC 2 compliance score:| Score | Status | Action |
|---|---|---|
| 95-100% | Audit Ready | Maintain controls |
| 85-94% | Good | Address gaps before audit |
| 70-84% | Needs Work | Prioritize remediation |
| Below 70% | At Risk | Immediate attention |
Audit Preparation
Type I Audit
Point-in-time assessment of control design:- Run comprehensive SOC 2 scan
- Document control implementations
- Generate evidence report
- Prepare control narratives
Type II Audit
Assessment of control effectiveness over time:- Enable continuous monitoring
- Maintain evidence over audit period (typically 6-12 months)
- Track remediation timelines
- Document exceptions and compensating controls
Evidence Collection
Cloudgeni automatically collects:- Configuration snapshots
- Change history
- Access logs
- Security scan results
- Remediation records