Minnesota Security Consortium (MNSec)
9 ALPR audits across 9 agencies. Of the 9 we have read in full, 9 recorded zero findings (100%). Depth: checklist.
9
Agencies audited
9
Audits filed
100%
Zero findings
0
Audits with findings
Flags
The pattern here is a template that clears everyone it touches.
Never recorded a finding
All 9 audits read came back with zero findings.
Checklist template only
Every audit read is a statute-by-statute checklist with no substantive testing.
Audits its own members
A member-funded body auditing the agencies that fund it.
Law enforcement background
The firm’s principal or governing board includes current or former police personnel.
Audits by this auditor
Found compliant on all items; no findings.
Read the audit (LRL 261008) →Found compliant on all items; no findings.
Read the audit (LRL 260987) →Found compliant on all items; no findings. Separate from Richfield BWC audit (260637).
Read the audit (LRL 260900) →Found compliant on all items; no findings.
Read the audit (LRL 260189) →Found compliant on all items; no findings.
Read the audit (LRL 260679) →Found compliant on all items; no findings. First audit of the new Flock system.
Read the audit (LRL 251639) →Found compliant on all items; no findings.
Read the audit (LRL 251619) →Found compliant on all items; no findings.
Read the audit (LRL 251707) →Marked compliant, but the narrative noted the office had not been maintaining a standard set of Log of Use Reports, a subd. 5 requirement, in the now-retired BOSS system. No formal discrepancy was recorded and MNSec offered to assist with future systems. The clearest example of a noticed statutory gap that still ends in a clean result.
Read the audit (LRL 250871) →These figures describe what the filed reports contain. They are not an allegation that any audit was improper or that any agency is out of compliance with Minn. Stat. § 13.824. If you believe a record here is wrong, tell us and we will correct it.
← All auditors