Security & CJIS Posture
Built to stay out of your CJI scope.
There is no such thing as CJIS-certified software. What there is, is scope — and Command Post is built to give your TAC the facts to make that determination with.
No structured fields for DOB, SSN, or system returns.
The application provides no field for them. Command Post never asks for the identifiers used to query a criminal history system.
Meant to be sourced from your case file.
Subject information should come from the warrant, the case file, and public court record. What makes data CHRI is where it came from, not what it says.
Notes and attachments stay under your policy.
Command Post accepts narrative notes and document uploads. What your people put in them is governed by your agency’s policy and scope determination — do not paste or upload IDACS, NCIC, or III returns unless your agency has determined that use is in scope.
Your agency owns its data.
You decide who sees an operation and which teams it is shared with; every cross-jurisdiction share is your agency’s logged decision. We administer accounts — teams, users, tiers — and hold no standing access to your operational content.
We do not advertise Command Post as “CJIS certified” — no such certification exists for software, and any vendor claiming it is telling you something that cannot be true. What we will do is work with your TAC or CSO on a written scope determination, and sign the CJIS Security Addendum where your agency requires one.
Scope determination guide for your TAC