SOC 2 Database Controls and Evidence Generation
Meet SOC 2 CC6 and CC7 requirements. Generate continuous evidence. Pass your Type II assessment.
Enterprise software buyers increasingly require SOC 2 Type II reports as a condition of procurement. Meeting the Trust Service Criteria for database environments — access controls, change management, monitoring, and incident response — requires both technical implementation and continuous evidence collection. DBsafe automates the database-specific controls that SOC 2 assessors focus on most heavily.
SOC 2 requires continuous evidence that most teams collect manually
SOC 2 Type II requires demonstrating that controls were in place and operating effectively throughout a 12-month audit period. This is fundamentally different from Type I, which only requires that controls were in place at a point in time. Meeting the Type II standard requires continuous evidence: access logs from every day of the period, configuration records showing no unauthorised changes, and incident response documentation.
Most organisations gather this evidence manually in the weeks before their audit, pulling records from multiple systems, reformatting them, and assembling them into evidence packages. This process is expensive, incomplete, and produces evidence that looks retrospectively assembled rather than continuously maintained.
The cost of inaction
Lost enterprise contracts requiring SOC 2 Type II: typically £500K-£5M per lost contract
SOC 2 Type I report not accepted by enterprise buyers who require Type II evidence
Manual evidence gathering: £100,000-£300,000 per year in engineering and compliance time
Qualified SOC 2 opinion: can trigger contract review clauses and enterprise churn
How DBsafe supports SOC 2 database controls
Implement CC6 access controls
DBsafe enforces and evidences the logical and physical access controls required by SOC 2 CC6: role-based access, least-privilege enforcement, access reviews, and privileged account monitoring.
Collect CC7 operational evidence
Every database operation, configuration change, and access event is logged and retained. CC7's system operations requirements are met through continuous monitoring, anomaly detection, and incident response documentation.
Generate audit-ready evidence packages
SOC 2 evidence packages — formatted for your auditors with the specific controls they test and the evidence periods they require — are generated on demand from continuously collected data.
SOC 2 CC6: Logical and physical access controls
Common Criteria 6 covers logical and physical access to prevent unauthorized access. For databases, the relevant controls include restricting access to authorised users (CC6.1), assigning access based on job responsibilities (CC6.2), revoking access when no longer needed (CC6.3), and preventing and detecting unauthorized access (CC6.6 through CC6.8).
DBsafe addresses all of these: role-based access control implements CC6.1 and CC6.2. Automated access reviews support CC6.3 by identifying accounts with excessive or unused access. Monitoring and anomaly detection support CC6.6-CC6.8.
SOC 2 CC7: System operations and monitoring
Common Criteria 7 requires that systems be monitored for anomalies and deviations from expected performance. For databases, this includes detecting, analysing, and responding to security events (CC7.2), identifying and responding to threats (CC7.3), and implementing business continuity and recovery (CC7.5).
DBsafe's real-time query monitoring and anomaly detection directly satisfy CC7.2 and CC7.3. Incident response documentation capabilities support CC7.5 by providing the investigation tools needed for structured incident handling.
Access reviews and evidence for SOC 2 assessors
SOC 2 assessors look for evidence that access reviews are conducted regularly and that access is removed promptly when no longer needed. DBsafe schedules automated access reviews, captures the results, and generates review completion records. When access is removed, the removal is logged with timestamp and authorisation.
This creates a continuous record of access management activity that satisfies assessors' expectations for CC6 controls without requiring manual spreadsheet-based reviews.
Change management and configuration monitoring
SOC 2 CC8 covers change management: changes to infrastructure and software must be authorised, tested, and documented. For databases, this includes schema changes, access control modifications, and configuration updates.
DBsafe monitors database configurations and alerts on unauthorised changes. Schema change events are logged with the identity of the initiating connection and the SQL statement executed. This change log provides the evidence assessors need to verify that change management controls are operating as described in the control narrative.
Continuous evidence versus point-in-time collection
The key difference between Type I and Type II assessments is the requirement for continuous evidence. Type I assessors ask: were controls in place on this date? Type II assessors ask: were controls in place and operating effectively throughout this 12-month period?
DBsafe's continuous collection model — logging every database operation, access event, and configuration change from the day you connect — creates the evidence base that Type II assessors need. Evidence is not reconstructed before the audit; it has been accumulating throughout the period.
Preparing for a SOC 2 assessment with DBsafe
SOC 2 audit preparation traditionally takes 4-6 weeks of engineering and compliance time. With DBsafe, the process is compressed significantly. The compliance dashboard shows which controls are in place and which gaps exist. Evidence packages are generated in minutes. Specific evidence items — access logs for a date range, configuration records for a control period, access review completion records — are available on demand.
This compression of audit preparation work is a direct cost saving and frees engineering teams from reactive compliance work to focus on product development.
Platform Capabilities
Everything you need to address SOC 2 compliance — in one integrated platform.
CC6 Access Controls
Role-based access, least-privilege enforcement, and automated access reviews with evidence capture.
CC7 Monitoring
Real-time query monitoring, anomaly detection, and incident response documentation.
Continuous Evidence Collection
Every access event, configuration change, and operational action logged automatically throughout the audit period.
Audit-Ready Evidence Packages
SOC 2-formatted evidence exports generated on demand for assessors.
Configuration Change Logging
Schema changes and configuration modifications logged with identity and authorisation context.
Access Review Automation
Scheduled access reviews with automated capture of completion evidence.
Frequently Asked Questions
Answers to the most common questions about SOC 2 compliance.
What SOC 2 Trust Service Criteria apply to databases?
The most relevant criteria for database environments are CC6 (Logical and Physical Access Controls) and CC7 (System Operations). CC6 requires access controls, access reviews, and anomaly detection. CC7 requires operational monitoring, incident response, and change management. DBsafe addresses all of these directly.
What is the difference between SOC 2 Type I and Type II?
SOC 2 Type I provides an opinion on whether controls are suitably designed at a point in time. Type II provides an opinion on whether controls are suitably designed and operating effectively over a defined period (typically 12 months). Type II requires continuous evidence that controls were in place and working throughout the period.
Can DBsafe generate evidence retrospectively for an audit?
DBsafe generates evidence from the point at which a database is connected. Evidence cannot be created retroactively for periods before connection. For this reason, connecting databases as early as possible — ideally well before the intended audit period — maximises the evidence available for a Type II assessment.
How does DBsafe help with SOC 2 access reviews?
DBsafe schedules periodic access reviews, identifies accounts with excessive or unused privileges, and captures completion evidence when reviews are conducted. Access removals are logged with the identity of the person who authorised the change. This creates the continuous access management evidence that SOC 2 CC6 assessors look for.
Does DBsafe integrate with GRC platforms used for SOC 2 management?
Yes. DBsafe integrates with GRC platforms including Vanta, Drata, Secureframe, and Tugboat Logic via REST API and webhook integrations. Evidence collected by DBsafe can be automatically synced to your GRC platform, reducing the manual evidence management burden during audit preparation.
Related Solutions
Database Compliance Across Every Framework
One platform. Every framework. Continuous evidence.
Learn moreComprehensive Database Audit Logging
Know who accessed what, when, from where, and why. Always.
Learn moreISO 27001 Data Controls for Database Environments
Implement Annex A controls for information classification, access management and operations security.
Learn more