Skip to content

SOC 2 Type II Readiness Guide

Overview

This document maps HeliosDB-Lite’s security controls to SOC 2 Trust Services Criteria, demonstrating readiness for SOC 2 Type II certification.

Trust Services Criteria Mapping

CC1: Control Environment

CriteriaControlHeliosDB ImplementationEvidence
CC1.1Commitment to integrity and ethical valuesCode of Conduct, Contribution GuidelinesCode of conduct and contribution guidelines
CC1.2Board oversightGovernance documentationGovernance documentation (internal)
CC1.3Management establishes structuresOrganizational structureGovernance documentation (internal)
CC1.4Commitment to competenceHiring and training policiesHR documentation
CC1.5Accountability enforcementPerformance managementHR documentation

CC2: Communication and Information

CriteriaControlHeliosDB ImplementationEvidence
CC2.1Internal communicationInternal documentationInternal documentation set
CC2.2External communicationPublic documentation, API docsPublic documentation, REST API reference
CC2.3Security policies communicatedSecurity documentationSecurity policy, compliance documents

CC3: Risk Assessment

CriteriaControlHeliosDB ImplementationEvidence
CC3.1Risk identificationThreat modeling, risk registerRisk register (internal)
CC3.2Risk analysisSecurity assessmentsSecurity audit reports
CC3.3Fraud risk considerationSecurity controlsSecurity policy
CC3.4Change impact assessmentChange management processChange management policy

CC4: Monitoring Activities

CriteriaControlHeliosDB ImplementationEvidence
CC4.1Ongoing monitoringLogging, metrics, alertingBuilt-in tracing, metrics
CC4.2Deficiency evaluationIncident managementIncident response plan (internal)

CC5: Control Activities

CriteriaControlHeliosDB ImplementationEvidence
CC5.1Selection of controlsRisk-based control selectionSecurity architecture docs
CC5.2Technology controlsTechnical implementationSource code, configurations
CC5.3Policies and proceduresDocumented proceduresCompliance and enterprise documentation

CC6: Logical and Physical Access Controls

CriteriaControlHeliosDB ImplementationEvidence
CC6.1Access to infrastructureRole-based accessAccess control policy
CC6.2System access registrationUser provisioningAuthentication system
CC6.3Access removalDeprovisioning processAccess control procedures
CC6.4Access reviewPeriodic access reviewsAudit logs
CC6.5Access authenticationStrong authenticationTLS, JWT, password policies
CC6.6Access protectionEncryption in transit/at restTDE, TLS 1.3 (ZKE planned)
CC6.7Transmission encryptionTLS implementationrustls configuration
CC6.8Destruction of dataSecure deletionZeroize library

CC7: System Operations

CriteriaControlHeliosDB ImplementationEvidence
CC7.1Vulnerability detectionSecurity scanningCI/CD pipeline
CC7.2Incident monitoringLogging and alertingTracing infrastructure
CC7.3Security analysisLog analysisOperational runbooks (internal)
CC7.4Incident responseIR proceduresIncident response plan (internal)
CC7.5Recovery from incidentsRecovery proceduresDisaster recovery plan

CC8: Change Management

CriteriaControlHeliosDB ImplementationEvidence
CC8.1Change authorizationPR approval processGitHub branch protection
CC8.2Change testingCI/CD testingGitHub Actions workflows
CC8.3Change deploymentRelease processRelease process (internal)

CC9: Risk Mitigation

CriteriaControlHeliosDB ImplementationEvidence
CC9.1Vendor managementDependency managementDependency manifest, license review
CC9.2Business continuityBC/DR plansBusiness continuity plan (internal)

Security Controls Summary

Authentication & Authorization

┌─────────────────────────────────────────────────────────────────┐
│ Authentication Flow │
├─────────────────────────────────────────────────────────────────┤
│ Client → TLS 1.3 → PostgreSQL Auth → Row-Level Security │
│ │ │
│ ┌──────┴──────┐ │
│ │ Methods │ │
│ ├─────────────┤ │
│ │ • Password │ (Argon2id/PBKDF2 hashed) │
│ │ • SCRAM-256 │ (PostgreSQL compatible) │
│ │ • JWT │ (HS256, REST API) │
│ │ • mTLS │ (planned) │
│ └─────────────┘ │
└─────────────────────────────────────────────────────────────────┘

Encryption Architecture

┌─────────────────────────────────────────────────────────────────┐
│ Encryption Layers │
├─────────────────────────────────────────────────────────────────┤
│ Layer 1: Transit TLS 1.3 (ECDHE + AES-256-GCM) │
│ Layer 2: TDE AES-256-GCM (server-managed keys) │
│ Layer 3: ZKE client-managed keys (planned) │
│ Layer 4: Field-Level Per-column encryption (optional) │
└─────────────────────────────────────────────────────────────────┘

Audit Logging (Planned)

Built-in audit logging is planned for HeliosDB Lite; the table lists the events it will record. Until it is available, record changes to sensitive tables with triggers (see Audit Logging) and keep the server logs.

Event TypeLogged FieldsRetention
AuthenticationUser, timestamp, IP, result90 days
AuthorizationUser, resource, action, result90 days
Data AccessUser, table, query type, timestamp30 days
Schema ChangesUser, DDL statement, timestamp1 year
Admin ActionsUser, action, parameters, timestamp1 year

Gap Analysis

Available Today

  • Encryption at rest (TDE)
  • Encryption in transit (TLS 1.3)
  • Authentication (multiple methods)
  • Row-level security
  • Secure key management
  • Change management (PR process)
  • Vulnerability scanning (static analysis, cargo-audit)

In Progress

  • SOC 2 Type II audit engagement
  • Penetration testing (annual)
  • Security awareness training documentation
  • Vendor risk assessment process

Planned

  • Built-in audit logging
  • Security Operations Center (SOC) monitoring
  • Bug bounty program
  • Third-party security audit
  • ISO 27001 certification

Evidence Collection

Automated Evidence

Evidence TypeCollection MethodStorage
Access logsApplication loggingLog aggregation service
Change historyGit commitsGitHub
Test resultsCI/CD pipelineGitHub Actions
Vulnerability scanscargo-auditCI/CD artifacts
Code reviewsPull request reviewsGitHub

Manual Evidence

Evidence TypeCollection MethodFrequency
Policy reviewsAnnual review cycleAnnually
Access reviewsManual auditQuarterly
Risk assessmentsSecurity team reviewAnnually
Penetration testsThird-party engagementAnnually

Audit Preparation Checklist

Pre-Audit (3 months before)

  • Review all policies and procedures
  • Conduct internal control testing
  • Update risk assessment
  • Verify evidence collection systems
  • Brief relevant personnel

During Audit

  • Provide auditor access to systems
  • Coordinate evidence requests
  • Address auditor questions
  • Document control walkthroughs

Post-Audit

  • Review draft report
  • Address any findings
  • Implement remediation plans
  • Obtain final report

Contact

For SOC 2 compliance inquiries: