Encryption

At-rest

All data is encrypted with AES-256 at rest.

Communication

HTTPS is required for web interface, with only TLS 1.2 and TLS 1.3 being supported.

SFTP is required for file exchange, with only secured algorithms per ssh-audit (see doc for the list). We provide an optional GPG encryption layer.

Log changes in database

All data updates are tracked in an append-only applicative log stored in database, alongside when the updated data itself changes. For each log event, we store:

• the change in data
• who is responsible for the change
• which transaction caused this change

<aside> ⏳ Retention period: log events are retained for 550 days

</aside>

Live replica in case of hardware failure

At any point of time we have a live full replica of the database that can take over the role of the primary database in case of hardware failure of the primary database hardware

<aside> ⏳ Retention period: this is not a backup or logged event, retention does not apply here

</aside>

Backups and Restoration

Logical backups of the database are performed regularly to ensure the availability, integrity, and confidentiality of data. Each backup represents a complete copy of the data at the time of execution, allowing for full restoration of the system in the event of an incident or data corruption.

Backups are replicated across two geographic regions:

• one copy is stored in the same region as the primary database to enable rapid recovery;