CJIS-CT compliance for Connecticut law enforcement agencies
Connecticut agencies accessing the Connecticut Information Sharing System (CISS) answer to the FBI's CJIS Security Policy v6.0 and the CJIS-CT Security Policy, which comes with a fixed annual deadline the federal policy doesn't set. ComplianceLattice tracks the federal foundation both share.
A federal baseline, on a fixed calendar
The CJIS-CT Security Policy requires every agency to submit a certification form to the Department of Information Technology's CJIS Support Group annually, on or before June 30th - not a rolling anniversary date tied to when your agency first connected, but the same fixed date for every agency in the state. Noncompliance can mean removal of access rights to CJIS-CT applications.
The substance behind that certification - access control, authentication, audit logging, incident response, and the rest of CJIS v6.0's 20 policy areas, plus CJIS-CT's explicit FIPS 140-2 encryption requirement - is largely the same work every CJIS-connected agency in the country does. ComplianceLattice tracks that full federal baseline today, covering most of what the certification actually attests to.
A fixed June 30 deadline shared across every agency in the state means there's no individualized reminder built into the system the way an anniversary date might prompt one - it's on your agency to track it independently. If your agency is working through the CJIS-CT Security Policy requirements now, reach out - alpha tester feedback directly shapes what we build first.
- All 20 CJIS v6.0 policy areas, the federal baseline CJIS-CT builds on
- Recurring task tracking so the June 30 annual certification doesn't get missed
- Evidence vault with expiration tracking for background checks and training renewals
- One-click audit export for your CJIS-CT or FBI assessor