Trust Center

This Trust Center summarizes the controls LuminLogic applies to its hosted production environment. It is intended as a customer-facing reference for security, IT, and audit teams evaluating or operating with LuminLogic. 

To receive a completed, signed security questionnaire, a current Installation Qualification (IQ) summary, or to discuss customer-specific control requirements, please contact your LuminLogic representative. 

Hosting environment 

LuminLogic is hosted on Amazon Web Services (AWS) in the United States. The production environment runs in a dedicated AWS account that is isolated at the account boundary from all other LuminLogic environments, with no shared networks, data stores, or credentials between accounts. 

Production infrastructure is provisioned and managed through version-controlled infrastructure-as-code, ensuring that the deployed environment corresponds to a reviewed, approved baseline. The architecture includes: 

• Dedicated Virtual Private Cloud (VPC) networking deployed across multiple AWS Availability Zones, with application servers and databases in private subnets that are not reachable from the public internet. 

• Containerized application services fronted by managed load balancers that terminate TLS at the edge. 

• A managed, encrypted relational database service for primary application data. 

• Object storage for customer files, provisioned on a per-customer basis with isolation enforced at the resource boundary. 

• A managed identity service for user authentication. 

Further architectural detail is available under NDA on request. 

Encryption methods 

Customer data is encrypted both at rest and in transit. 

At rest. All storage layers used by LuminLogic  including the primary database (and its automated backups, snapshots, and replicas), per-customer object storage, secrets storage, message queues, application logs, container images, and ephemeral compute storage  are encrypted at rest using AWS-managed keys. Customer-managed keys can be supported under specific contractual arrangements. 

In transit. All client and service-to-service connections that carry customer data use TLS 1.2 or higher with modern cipher suites. Deprecated protocols (TLS 1.0, TLS 1.1, SSLv3) are not accepted. HTTP requests to the application are redirected to HTTPS, and resource policies on internal AWS services deny non-TLS access where applicable. 

Authentication controls 

User authentication is provided by a managed identity service that enforces an organizational password policy covering length, complexity, and reuse. Key controls include: 

• Individual user accounts. Each user authenticates with a unique identity. Shared accounts are not supported for actions that require accountability. 

• Standards-based sign-in. The application uses an industry-standard authentication flow over TLS; session tokens are issued by the managed identity service and validated by the application. 

• Session controls. Sessions expire after a configurable period of inactivity, and re-authentication can be required for sensitive actions. 

• Signature re-authentication. Electronic-signature workflows require the signer's credentials at the moment of signing, supporting the identification requirements of FDA 21 CFR Part 11. 

• Account lifecycle. Authorized administrators provision, modify, and deprovision users. Deactivated users lose their ability to authenticate immediately. 

• Administrative access. LuminLogic personnel who administer the underlying AWS environment follow SOC2 Type II controls and use named, scoped identities under a least-privilege model, with multi-factor authentication where applicable. Administrative credentials are never shared with customers. 

Backup and recovery approach 

LuminLogic maintains layered backups, and recovery procedures are exercised as part of its validation program. 

• Primary database. Automated backups are taken on a continuous basis with a 30-day retention window, supporting point-in-time recovery across that window. Backups inherit the encryption applied to live data. 

• Customer file storage. Per-customer object storage uses versioning, so prior versions of objects remain recoverable in the event of accidental modification or deletion. All access is enforced over TLS, and public access is blocked. 

• Configuration and releases. Infrastructure and application releases are deployed from version-controlled, source-controlled artifacts, allowing a known-good baseline to be redeployed when required. 

• Restoration testing. Restoration from backups is tested as part of LuminLogic's validation program; restoration evidence is retained and reviewable on request. 

Disaster recovery summary 

LuminLogic's resilience posture is built into the architecture rather than dependent on standby procedures: 

• Multi-AZ deployment. Database tiers are distributed across multiple AWS Availability Zones. Loss of a single zone does not interrupt service. 

• Managed database resilience. The primary database service maintains redundant storage across multiple zones and supports automatic failover. 

• Stateless application tier. Application containers are stateless and can be rescheduled or scaled by the orchestration layer without manual intervention. 

• Point-in-time recovery and versioned storage provide additional recovery paths for data-level incidents that are not infrastructure failures. 

• Incident response and recovery procedures are documented and maintained by the operations function, with periodic review and exercise. 

Specific recovery time and recovery point objectives are defined in customer agreements where applicable. 

Access control philosophy 

LuminLogic applies the principle of least privilege at three layers. 

Infrastructure. Access to the AWS environment hosting LuminLogic is restricted to a limited group of authorized personnel using named, scoped identities. Privileged actions are logged centrally. Access is reviewed periodically and revoked promptly on role change. 

Network. Application and database tiers reside in private network segments that are not reachable from the public internet. Only the application's public entry point is exposed, and traffic is filtered at multiple layers. Network activity and account-level activity are continuously monitored, and anomalous-behavior detection is enabled at the AWS-account level. 

Application. Inside LuminLogic, role-based permissions restrict what each user can see and do. Customer data is logically segregated by tenant identifier at the database layer and additionally segregated at the resource boundary for file storage. Changes to the platform follow a separation-of-duties model: the roles that author, review, approve, and deploy changes are distinct, so no single individual can introduce an unreviewed change to production. 

Audit trail functionality 

LuminLogic maintains complementary audit trails at the application and infrastructure layers. 

Application audit trail. Changes to controlled records — including documents, CAPAs, change requests, complaints, training records, and electronic signatures — are captured in an immutable audit trail that records: 

• the authenticated user who performed the action, 

• the specific change (with before-and-after values where applicable), 

• the timestamp of the change, and 

• a reason where required by the workflow. 

These audit trails cannot be edited or deleted by users and are designed to support the audit-trail and electronic-records expectations of FDA 21 CFR Part 11 §11.10(e) and ISO 13485:2016 Section 4.2.5. 

Infrastructure audit trail. Administrative actions against the AWS environment are recorded centrally and retained per LuminLogic's internal control program. Application, platform, and network-level logs are captured and monitored, with anomalous-activity detection enabled. 

Data retention policy 

Customer records. Records created in LuminLogic including documents, CAPAs, change requests, training records, and signed approvals are retained for the life of the customer subscription. The platform does not automatically delete customer records. Records can be archived or marked obsolete through application workflows; archived records remain retrievable, and their audit trails are preserved with the record. Customers can export their data to support their own long-term retention obligations. 

Operational data. Operational logs and system telemetry are retained for windows appropriate to their purpose, balancing incident-investigation needs against minimization principles. Specific operational retention values are available under NDA. 

Where to go next 

• Audit Trail How the application audit trail works day-to-day. 

• Electronic Signatures Overview How LuminLogic's signature workflow meets FDA 21 CFR Part 11. 

• Contact your LuminLogic representative for a signed security questionnaire, IQ summary, or customer-specific control discussions.