Secure Data Storage
Simulate.Farm is being designed with strong protections for research data, simulation inputs, and model outputs. The controls below distinguish platform design goals from the smaller set implemented in the current vertical slice.
Current status: ownership and region boundaries, immutable manifests, and allowlisted audit events are being implemented. Regional cloud isolation, deletion workflows, private networking, and operational controls are not yet deployed guarantees.
Security Features
These are target controls for the commercial platform; availability depends on the deployed environment and is not implied by this architecture page.
Encryption in Transit
All communication between users, services, and APIs is encrypted using TLS 1.3. Certificate pinning prevents man-in-the-middle attacks on API connections.
Encryption at Rest
Stored datasets, simulation inputs, and outputs are encrypted using AES-256. Encryption keys are managed through a dedicated key management service with regular rotation.
Access Control
Role-based access controls ensure that only authorized users and systems can access data. Permissions are configurable at the project, simulation, and file level.
Data Isolation
Simulation data is organized and stored in isolated environments that prevent unintended access across projects or organizations. Multi-tenancy is enforced at the infrastructure level.
Reproducible and Auditable Runs
Simulation configurations and results are versioned and tracked. Complete provenance information enables verification and supports reproducibility requirements.
Audit Logging
All data access, modifications, and administrative actions are logged with timestamps and user attribution. Logs are immutable and retained according to configurable policies.
Data Lifecycle Security
Security controls are applied throughout the entire data lifecycle, from initial upload through processing, storage, and eventual deletion.
Ingestion
Data is validated, sanitized, and encrypted before storage. Schema validation prevents malformed inputs.
Processing
Simulations run in isolated compute environments. Intermediate data is encrypted and automatically purged after processing.
Storage
Results are stored in encrypted, versioned repositories with configurable retention policies.
Access
All data access is authenticated, authorized, and logged. Exports are tracked and auditable.
Deletion
Users can request data deletion at any time. Deletion is propagated across all storage tiers and backups.
Security Controls
Target security controls and their present implementation status.
| Control | Implementation | Status |
|---|---|---|
| Data Encryption | AES-256 at rest, TLS 1.3 in transit | Provider baseline |
| Access Control | Role-based with principle of least privilege | In progress |
| Audit Logging | Immutable logs with configurable retention | In progress |
| Data Residency | Configurable regional data storage | Designed |
| Backup and Recovery | Automated backups with point-in-time recovery | Planned |
| Incident Response | Documented procedures and notification protocols | Planned |
Infrastructure Security
The production design calls for private, region-bound cloud infrastructure with layered network and service-identity controls. That environment is not yet provisioned by this repository.
- Virtual private cloud with network segmentation
- Web application firewall with DDoS protection
- Regular security patching and vulnerability scanning
- Intrusion detection and prevention systems
- Secure secrets management with hardware security modules
Each simulation runs in an isolated container with dedicated resources and no shared state.
All internal traffic is encrypted and routed through private networks with strict egress controls.
Data Sovereignty and Ownership
Users retain full ownership of their data at all times. Simulate.Farm does not claim any rights to user-uploaded datasets, simulation configurations, or generated results.
Your Data
All uploaded datasets and configurations remain your property and can be exported or deleted at any time.
Your Results
Simulation outputs belong to you. We do not use results to train models or for any purpose beyond service delivery.
Your Control
Configure retention policies, data residency preferences, and access controls according to your requirements.
Questions about security?
Review our documentation for detailed security information, or contact us to discuss specific compliance requirements.