Security

Security by Design

Layered controls for sensitive clinical information across authentication, authorization, encryption, network isolation, auditability, and infrastructure discipline.

Behavioral health software handles deeply personal information. Security cannot be treated as a feature added after the product is built, it must be part of the platform's foundation.

Leitara was designed with layered security controls that protect sensitive clinical information through authentication, authorization, encryption, network isolation, auditability, and infrastructure discipline.

Our approach emphasizes defense in depth, ensuring that multiple independent controls work together to protect client data.

Defense in Depth

Leitara applies security controls at every layer of the platform.

User Authentication
Application Authorization
Database Row-Level Security
Encrypted Storage
Network Isolation
Audit Logging

Rather than relying on a single security boundary, each layer reinforces the next.

Identity and Access

Authentication is provided through AWS Cognito using modern OAuth 2.0 and OpenID Connect standards.

Every authenticated request establishes a role-aware execution context before application logic is executed.

Separate security boundaries exist for providers, clients, billing services, background workers, and infrastructure operations.

Identity controls

AWS Cognito authentication

OAuth 2.0 / OpenID Connect

JWT-based API authorization

Role-specific application services

Least-privilege workload identities

Multi-factor authentication for infrastructure access

Database Security

Tenant isolation is enforced at the database layer using PostgreSQL Row-Level Security (RLS).

Each request establishes provider or client identity before database access, allowing PostgreSQL policies to determine which records are visible.

This provides an additional layer of protection beyond application authorization alone.

Data protection

PostgreSQL Row-Level Security

IAM-authenticated database connections

Transaction-scoped execution context

Optimistic concurrency control

Role-aware data access

Encryption

Sensitive information is protected both at rest and in transit.

Encryption standards

Database — AWS KMS encryption

File storage — KMS-encrypted S3 buckets

Network traffic — TLS

Authentication — Signed JWT tokens

Configuration secrets — AWS Systems Manager & Secrets Manager

Encryption is applied throughout the platform without requiring provider configuration.

Infrastructure

Leitara runs on AWS using private infrastructure designed to minimize public exposure.

Production workloads operate within private subnets behind load balancers, with no direct public access to application servers.

Administrative access is performed through AWS Systems Manager Session Manager rather than SSH.

Infrastructure controls

Private VPC networking

Web Application Firewall (WAF)

CloudFront content delivery

Private EC2 application servers

Managed PostgreSQL (Amazon RDS)

Systems Manager administrative access

Infrastructure as Code (Pulumi)

Audit and Accountability

Clinical systems require accountability as well as security.

Leitara records sensitive operations through an audit pipeline that supports traceability while separating operational activity from long-term audit storage.

Audit information is retained independently of application workflows, supporting future compliance and operational review.

Audit capabilities

Audit logging

Background audit processing

Long-term encrypted archive

Correlation identifiers

Structured operational logging

Secure AI

Compass operates within the same security boundaries as the rest of the platform.

AI does not bypass authorization controls, independently modify clinical records, or communicate directly with clients.

Every recommendation is reviewed by the provider before becoming part of the clinical workflow.

This allows AI to participate safely within existing authorization, audit, and review processes.

Operational Maturity

Leitara's infrastructure emphasizes repeatability and controlled deployment.

Operational practices

Infrastructure as Code

Immutable application deployments

Environment separation

Automated deployment pipelines

Health monitoring

CloudWatch logging

Versioned releases

These practices reduce operational risk while supporting reliable software delivery.

Security Highlights

AWS-hosted infrastructure

Architecture designed to support HIPAA compliance responsibilities

PostgreSQL Row-Level Security

End-to-end encryption in transit and at rest

KMS-managed encryption keys

Private application infrastructure

Immutable deployments

Comprehensive audit logging

Role-based authorization

AI integrated within existing security boundaries