JuratJURAT

Security & Compliance

Your own deployment, hosted in Jurat Cloud.

Jurat Cloud is built to run your deployment in Azure Government, hosted by Ultrafar. Each agency has its own application, database, and storage account; Ultrafar operates the encryption keys under the CJIS Security Addendum. Officers keep their own Microsoft Entra identity; only the infrastructure moves.

Hosting

We run it for you.

Jurat Cloud

Ultrafar hosts it in Azure Government on your subdomain. You do not need your own Azure Government account or an IT team to run it. Officers still sign in through your agency's own Entra work sign-in. Compliance approvals for a hosted deployment are worked during onboarding, not before.

$95 / OFFICER / YEAR

Reference

CJIS Security Policy section matrix

This is a working reference for your CSO or TAC (your agency's CJIS Systems Officer and Terminal Agency Coordinator). CJI means criminal justice information. It is not a substitute for your security addendum or a formal audit.

FBI CJIS SECURITY POLICY, VERSION 6.1
CJIS §5.4
Auditing & Accountability
Auditable records of system access and CJI-affecting actions.
Every open, creation, signature, revocation, and download is written to a log that can only be added to, never edited, and the database enforces this. The log records who did it, when, and from what internet (IP) address.
CJIS §5.5
Access Control
Role-based access, least privilege, and session enforcement.
Permissions depend on the person's role: officer, admin, or records. An admin is signed out after a period of inactivity, separate from the browser's own timeout.
CJIS §5.6
Identification & Authentication
Unique identification and advanced authentication for CJI access.
Staff sign in with the agency's own Microsoft work account (Entra ID). Jurat keeps no separate passwords, and there are no shared logins.
CJIS §5.9
Physical & Environmental Protection
Physical safeguards for systems that store or process CJI.
U.S. Microsoft Azure data centers — commercial or Azure Government, depending on the model. No on-prem or vendor-office gear in the data path.
CJIS §5.10
System & Communications Protection
Encryption in transit and at rest; boundary protection.
Connections use modern TLS at the strongest level both sides support. Data is encrypted in transit and at rest, using FIPS-validated Azure platform cryptographic modules (FIPS is the federal encryption standard). Every page also tells the browser to apply strict security settings.
CJIS §5.13
Mobile Devices
Controls for CJI accessed from mobile/portable devices.
No native app and no local CJI stored on the device. Sessions run in the browser against a scoped, expiring link or an authenticated session.

Connections are encrypted with modern TLS, the current standard for secure web traffic. The platform uses the strongest version each device supports, so most devices get the latest automatically. A minimum level is set instead of one fixed version, so an agency laptop with an older browser isn't locked out entirely.