Trust Centre

Security

How the product protects sign-in, sessions, access and the audit record, as verified against its code.

Scope. This page describes security features built into the ControlMap software when it runs with its application server and database. It is not a statement about any hosting environment, and no certification or audit attestation is claimed.

Sign-in and passwords

  • Local accounts sign in with a username and password. Passwords are stored only as scrypt hashes (N = 2^15, r = 8, p = 1), each with its own random salt, and are compared in constant time.
  • After five failed attempts in a row an account is locked for 15 minutes.
  • Failed and refused sign-ins are written to the audit log.
  • Sign-in through OpenID Connect is supported as an alternative. The identity token's signature, issuer and audience are checked on the server. Keycloak is the tested provider.

Sessions

  • A session lasts eight hours.
  • The session token is 32 random bytes. The database stores only its SHA-256 hash, so a copy of the database does not contain usable tokens.
  • The session cookie is HttpOnly and SameSite=Strict, and is limited to the API path. It is also marked Secure unless that is switched off for local development.
  • Every request that changes data must carry a custom header that a cross-site form cannot set.
  • A local account is re-read on every request, so disabling a user or changing a role takes effect immediately rather than when the session expires.

Roles and access

  • There are three roles: administrator, analyst and viewer. A viewer has read-only access.
  • The organisation and role of a request are taken from the server-side session, never from the request body or headers.

Audit log

  • Audit events are written by the server, which stamps the organisation, the actor, the time and the client address itself.
  • Events are hash-chained: each one includes the hash of the one before, and the chain can be re-verified to detect a change.
  • The database table refuses updates, deletions and truncation through a trigger.
  • Retention is configurable to 30, 90, 365 or 1,095 days. Events older than the chosen period are removed, and the removal is itself recorded as an event.
  • The consent ledger is hash-chained in the same way as the audit log.
  • The ledger identifies a person by a reference you choose. The visitor's network address and browser details are stored only as a salted hash.
  • API keys for connected systems are stored as SHA-256 hashes. Webhooks sent to those systems are signed with HMAC-SHA256 and a timestamp.
  • The public consent endpoints are rate limited by network address and by key.

What this page does not cover

Encryption in transit and at rest, network controls, backups, monitoring and operational access depend on where and how ControlMap is deployed. They are not described here, and no commitment about them is made on this website. Ask us about the deployment you are considering.

To report a security concern, use the contact page. Please do not include details of a vulnerability in the first message; we will arrange a suitable channel.