Security is the foundation of ChartScribe. This page outlines our security practices, certifications, and the measures we take to protect your data and your patients' data.
SOC 2
Controls aligned
ISO 27001
Controls aligned
DTAC
NHS aligned
HIPAA
BAA available
Data Encryption
All data is encrypted at all stages of its lifecycle:
Encryption at Rest
- Algorithm: AES-256-GCM (Galois/Counter Mode) — authenticated encryption
- Key management: Keys are stored in AWS KMS with hardware security module (HSM) backing
- Key rotation: Automatic rotation every 90 days
- Audio recordings: Encrypted on the device before any network transmission
- Clinical notes: Encrypted in the database with per-user encryption keys
- Backups: Encrypted with separate key hierarchy, stored in geographically separate locations
Encryption in Transit
- Protocol: TLS 1.3 (minimum TLS 1.2) with forward secrecy
- Cipher suites: Only AEAD ciphers (AES-GCM, ChaCha20-Poly1305)
- Certificate: Let's Encrypt R3, auto-renewed every 60 days
- HSTS: Enabled with max-age of 1 year, includeSubDomains, preload
- CSP: Content Security Policy enforced with strict directives
Infrastructure Security
ChartScribe runs on Amazon Web Services (AWS) with the following security measures:
- Region: All patient data stored exclusively in AWS London (eu-west-2)
- Network: VPC isolation with private subnets for application and database layers
- Firewalls: AWS WAF with managed rule sets, rate limiting, and IP reputation filtering
- DDoS protection: AWS Shield Advanced for L3/L4/L7 protection
- CDN: Cloudflare with DDoS mitigation, bot management, and edge caching
- Patching: Automated security patching within 24 hours of critical CVE release
- Monitoring: 24/7 infrastructure monitoring with PagerDuty alerting
Authentication & Access Control
- Multi-factor authentication (MFA): TOTP-based 2FA enforced for all admin accounts, optional for clinicians
- Password policy: Minimum 12 characters, complexity requirements, breach detection via Have I Been Pwned API
- Session management: JWT tokens with 15-minute expiry, secure httpOnly cookies, automatic logout on inactivity
- Role-based access control (RBAC): Granular permissions — Admin, Clinician, Viewer, Billing
- Audit logging: All authentication events logged with IP address, user agent, and timestamp
- Brute force protection: Account lockout after 5 failed attempts, progressive delays
- SSO: SAML 2.0 and OIDC integration for organisation plans (Okta, Azure AD, Google Workspace)
Application Security
- Input validation: Strict server-side validation on all inputs, parameterized queries to prevent injection
- XSS prevention: Output encoding, Content Security Policy, and React's built-in escaping
- CSRF protection: Double-submit cookie pattern for all state-changing requests
- Dependency scanning: Automated vulnerability scanning of all dependencies (Snyk, Dependabot)
- Code review: All code changes require peer review and security sign-off
- Secrets management: No hardcoded secrets; AWS Secrets Manager with automatic rotation
- Security headers: Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy
Data Protection Practices
- Pseudonymisation: Patient identifiers separated from audio recordings where technically feasible
- Data minimisation: We only collect data necessary to provide the service
- Retention controls: Configurable retention periods with automatic deletion
- Secure deletion: Cryptographic erasure (key destruction) followed by physical media wiping
- Offline data: IndexedDB on devices encrypted with AES-256-GCM using PBKDF2-derived keys
- Export security: All data exports are encrypted with password-protected ZIP or PGP
Audit & Monitoring
- Access logging: Every access to patient data is logged with user ID, timestamp, action, and IP address
- Log retention: Audit logs retained for 7 years (legal requirement)
- Log integrity: Immutable audit logs with cryptographic hashing
- Anomaly detection: Automated alerts for unusual access patterns (e.g., bulk downloads, off-hours access)
- SIEM: Security information and event management with real-time threat detection
- Penetration testing: Annual third-party penetration tests and quarterly vulnerability scans
Incident Response
Our incident response plan follows the NCSC guidance:
- Detection: Automated monitoring detects anomalies within minutes
- Containment: Automated isolation of affected systems within 15 minutes
- Notification: Data controller notified within 24 hours of confirmed breach
- ICO notification: Where required, ICO notified within 72 hours
- Recovery: Systems restored from clean backups with full audit trail
- Post-incident: Root cause analysis and preventive measures implemented
Business Continuity
- RTO (Recovery Time Objective): 4 hours
- RPO (Recovery Point Objective): 15 minutes
- Backup frequency: Continuous point-in-time recovery
- Disaster recovery site: Warm standby in AWS Dublin (eu-west-1)
- Testing: Full DR drill conducted quarterly
Staff Security
- All employees complete annual security awareness training
- Enhanced DBS checks for all staff with data access
- Principle of least privilege — access granted only when necessary
- NDAs required for all employees and contractors
- Offboarding process revokes all access within 1 hour
Third-Party Security
All sub-processors are vetted against our security requirements:
- SOC 2 Type II or ISO 27001 certification required
- Annual security questionnaires completed
- Data Processing Agreements in place with all processors
- No training on patient data — OpenAI API with zero-retention guarantee
Contact
For security questions or to report a vulnerability: security@chartscribe.io
Responsible disclosure: We operate a bug bounty programme. Details at chartscribe.io/security/disclosure