MULES compliance for Missouri law enforcement agencies
Missouri agencies accessing CJI answer to the FBI's CJIS Security Policy v6.0 and the Missouri Uniform Law Enforcement System Policy - the MSHP supplement published as SHP-186 - layered on top of it. ComplianceLattice tracks the federal foundation both documents share.
A federal baseline, gated by training
SHP-186 ties compliance directly to activation: before a new ORI or OCA can be turned on for electronic access to criminal history record information, the agency's LASO has to complete training conducted by an MSHP CJIS Trainer/Auditor. Access doesn't come first with training to follow later - the training is a precondition.
Everything beyond that activation gate is the same work every CJIS-connected agency in the country does - access control, authentication, audit logging, incident response, and the rest of CJIS v6.0's 20 policy areas. ComplianceLattice tracks that full federal baseline today, covering most of the ground before you get to Missouri's activation-specific training requirement.
Because the training requirement is tied to standing up new access rather than an annual calendar date, it's easy to lose track of for a growing agency adding new ORIs or OCAs over time rather than one that set everything up once and hasn't changed since. If your agency is working through the MULES Policy (SHP-186) requirements now, reach out - alpha tester feedback directly shapes what we build first.
- All 20 CJIS v6.0 policy areas, the federal baseline MULES builds on
- Evidence vault with expiration tracking for background checks and training renewals
- Pre-built policy templates you can adapt for Missouri-specific requirements
- One-click audit export for your MSHP or FBI assessor