Security & CJIS

CJIS is architecture, not a checkbox.

TenCode was designed from the start around the FBI CJIS Security Policy. Security controls are part of the platform’s foundation, so they can’t be misconfigured away.

Advanced authentication

Multi-factor authentication is mandatory, using standard OIDC identity — Keycloak or your existing Microsoft Entra ID.

Read auditing

Every record view is logged — who looked at what, and when — not just edits. Audit trails are reviewable by your administrators.

Encryption everywhere

TLS in transit and encryption at rest for the database, attachments and backups.

Least-privilege access

Role, division and record-level permissions decide what each user can see and do, enforced on the server.

No embedded secrets

Credentials and keys live in your secrets store, never in code or default passwords shipped with the product.

Compliant hosting

Designed for CJIS-appropriate government cloud regions or your own facility — the same software either way.

Shared responsibility

Working with your CJIS Systems Officer.

CJIS compliance is ultimately established for each agency and environment. We provide the technical controls, documentation and hosting arrangements your CSO and auditors need to sign off.

  • Security addendum ready. We expect to execute the CJIS Security Addendum for personnel with access.
  • Synthetic data in demos. Our demonstration environments never contain real criminal justice information.
  • Portable by design. Standard containers and PostgreSQL — no lock-in to a single provider.