Data security

Data security

RackIntelligence is installed on your servers. Your rack photos, your inventory and the decision log stay on your network. Here is what is in place, and what is planned.

Contents
  1. Where your data lives
  2. Nothing is sent outside
  3. Signed releases, verified at installation
  4. Accounts, roles and sessions
  5. Human approval and log
  6. A protected website
  7. Backups encrypted with your key
  8. Encrypted disk verified at installation
  9. What is planned

Where your data lives

The whole platform runs on your servers, in containers: interface, analysis engine, inventory comparison, documents. Photos, analysis results, the database and the logs are stored on your premises.

Nothing is sent outside

Photo analysis, comparison and document generation happen on site. The platform makes no outbound calls: no photo or inventory data is sent to an online service, and it works without an internet connection.

Signed releases, verified at installation

Each release is delivered compiled, licensed and signed. Installation rejects a kit that is unsigned, signed with another key, or containing an archive that does not match its fingerprint. The check is repeated at every start by the installation command.

Accounts, roles and sessions

  • Accounts created by an administrator, no self-registration.
  • Roles: administrator, analyst, annotator, reader, approver; each user can only do what their role allows, and visible sites can be restricted.
  • Sessions are signed, closed after 30 minutes of inactivity and after 12 hours at the latest, and can be revoked by an administrator.
  • Passwords stored as hashes, sign-in attempts limited.

Human approval and log

Nothing is written to the inventory without a person’s approval, at one or two levels as you choose. Every action is logged: sign-ins, analyses, writes, with who, when and which rack.

A protected website

HTTPS connection (TLS 1.2 or later). Strict security headers: hash-based content security policy (CSP), embedding the platform in another page is forbidden, HSTS, nosniff. Every request that changes something has its origin checked.

Backups encrypted with your key

The backup includes the database, all data volumes and the configuration. It is encrypted with your company’s public key: only your private key can read it. Each archive carries a fingerprint, retention is daily and weekly, a copy can be sent off site, and restoration can be tested.

Encrypted disk verified at installation

Installation checks that the disk holding the data is encrypted. If it is not, you must explicitly choose to continue.

What is planned

Planned, not yet available: encryption of photos and the database by the platform itself, in addition to the encrypted disk. Until then, protection at rest relies on disk encryption, verified at installation.

The detailed measures are in the Trust center.

Stay in touch

New releases, newly recognized equipment, articles: one email when there is something new, nothing else.