Security and operations
An application in which a company documents its risks and weaknesses must itself be particularly well protected. This page describes how eunom.io is operated – and where gaps remain.
A dedicated instance per company
Each company receives its own instance with its own database, file storage and sign-in. Data of different companies never shares a database. An instance only knows its own credentials. Customer instances run on dedicated servers, separate from demo and test systems.
Operation in Germany
- The servers are rented from netcup GmbH (Karlsruhe) and are located in data centres in Germany.
- On the application servers, only the services that are strictly needed are reachable from outside. Administrative access is tightly restricted and additionally secured, and operating system security updates are installed automatically.
- Every change to eunom.io goes through version control with automated checks and is first rolled out to a separate pre-release environment.
Encryption
| What | Status |
|---|---|
| Transmission | always encrypted (TLS) |
| Files and documents in file storage | encrypted server-side (SSE-S3). The keys are managed by the storage service on the server itself. |
| Backups | encrypted before they leave the server |
| Database at rest | not separately encrypted at present |
We only list what has actually been implemented. Encryption with keys held outside the server (key management service) and encryption of the database at rest are to be settled before the first customer operation.
Backup and recovery
- Every night the database and files are backed up, encrypted and transferred to a separate server with another provider in Germany.
- Recovery is tested: a test run restores a backup into an empty environment and compares the contents.
- Trial instances are not backed up; they are deleted after three days anyway.
Sign-in
- Sign-in via Keycloak with two-factor authentication (authenticator app or security key) – mandatory for administration and approval roles, available to all other accounts
- Single sign-on with a company’s own directory is possible
- Roles and permissions following the principle of least privilege
Traceability
- Every change is logged with time, person, old and new value. The application itself cannot alter or delete this log.
- Deviations from derived values require a justification; material changes require four-eyes approval.
Trial instances
Each trial instance runs on its own: its own application containers, its own database with its own role, its own file storage with its own key, its own sign-in and its own internal network. It is deleted with all its content after three days. Trial instances are not intended for real data.
Data sovereignty
- Full export at any time as Excel, CSV or JSON
- No AI features; your data is not used to train models
- No tracking or analytics tools, neither on this website nor in the application