atlageneSecurity
Patient data, handled on purpose.
What we do today, and what we agree with each laboratory before identifiable data is shared.
In place today.
Separate databases
Genotype data and identity data are stored in two separate databases, reached through separate connections.
Short-lived file links
Genome files are uploaded and downloaded through signed links that expire within minutes.
Sign-in
Lab staff sign in with a one-time code sent to their phone and can add an authenticator app as a second factor.
Encrypted file storage
Genome files are stored in Amazon S3 with server-side encryption (AES-256).
Access logging
Access to patient data is written to an audit log.
Hosting
The platform runs on Amazon Web Services in the EU (Stockholm) region.
Agreed with each laboratory.
What the evaluation needs
Start with assay and workflow details, and agree a transfer process before sharing identifiable material.
Who has access
Your authorised team members, and the person responsible for reviewing and releasing each report.
The full lifecycle
Retention, deletion requests, backups and any records you are required to keep.
Your requirements
Send your security questionnaire or procurement requirements to security@atlagene.com. We share the architecture, providers and documentation for the scope.
The detail, in writing.
Every provider that processes data, what it receives and our agreement with it; how long each kind of record is kept; and how a breach is reported to the laboratory.
Found a security issue?
Please report it to security@atlagene.com with enough detail to reproduce it. Do not access, modify or keep data that is not yours while testing.
Bring us your assay.
Tell us what you run, who reads the report and what you want an evaluation to answer. We reply with a scoped plan.