Skip to content
  • There are no suggestions because the search field is empty.

Availability & Continuity

Juristic has clearly defined policies and procedures in accordance with our ISO 27001 certification.

💡 We refer to our Trust Center for access to the docs and policies mentioned below.

Logging and Backups

Logging is carried out in line with the agreement made with each customer. Juristic may, for example, connect tools used for aggregation and analysis of system usage, including troubleshooting.

Juristic operates with two types of environments, depending on the size of the customer:

  • Enterprise environments: Per agreement, our platform can be set up in a dedicated operational environment that can only be accessed by the specific customer (or on-prem). Separate accounts are created to minimise access between environments. Protocols and logs regarding queries and access to databases and servers can be provided to the customer.

  • General environments: If no separate agreement is concluded, customers will run on a general operating environment. Database and application servers may be accessed more frequently, but only to ensure uptime and minimise errors. In this setup, the principle of least privilege is applied – meaning that only employees with a role requiring access to the data will have it.

Backups and Recovery

  • The database instance is automatically backed up every day around 01:00 CET.

  • Backups are stored for up to 30 days.

  • Fallback versions are maintained for both backend and frontend servers, enabling quick rollbacks if a failure occurs.

  • In case of disaster, the operational environment should be up and running again within 30 minutes, unless there is a major outage at a core supplier.

  • Backups are subject to the same protections as original data.

  • Logging and disclosure of backups can be provided at the customer’s request.

  • Backups and disaster recovery capabilities are tested annually.

Business Continuity, Updates and Uptime

A business continuity procedure is in place, with clear requirements for information security and continuity, as set out in our Information Security Policy. We refer to our Trust Center for this documentation.

A defined procedure governs how staff and contractors maintain information security in line with established policies and procedures.

Update Policy

  • New versions of the application are deployed only after 21:00 CET.

  • Server and database updates follow best practices published by 3DS Outscale.

  • Security updates to the source code are included with regular updates.

  • Batch runs that may affect system usage occur only between 00:00 – 05:00 CET.