Minnesota Security Consortium (MNSec)

Found compliant on all items; no findings.

Found compliant on all items; no findings. Separate from Richfield BWC audit (260637).

Found compliant on all items; no findings.

Clean sheet. Zero findings and zero exceptions recorded across all nine statutory areas: policy (Policy 427), record retention, data security and access control, data classification, interagency sharing, public log of use, BCA notification, biennial audit, and breach notification (Policy 805). The report contains no recommendations at all. Retention confirmed at the Flock 30-day manufacturer default, inside the 60-day statutory cap; 17 stationary Flock units. The auditor reviewed a sample of all data search requests for July 2026 ("all samples had a justifiable reason by the requesting agency"), audited the administrative control panel for retention settings, and ran "a review of all users" ("users were deactivated when no longer with the agency or using the system"). The Flock console "did not show any out-of-State sharing." First Flock ALPR audit for the department; it "plan[s] on continuing an independent audit every two years." Conducted by Dimitrios Hilton, Senior Auditor, MNSec.

No findings or recommendations recorded. All 8 statutory sub-areas (policy, retention, data security/access, data classification, inter-agency sharing, public log of use, BCA notification, biennial audit planning) marked compliant. Auditor reviewed the Flock admin/retention control panel and sampled one month (July 2026) of inter-agency data-sharing requests; no exceptions surfaced in that sample.

First audit of West Saint Paul PD's new Flock system (10 stationary units, operational 9/1/25–6/30/26). MNSec found the agency compliant on policy, retention (30-day Flock default), access control (inactive users confirmed deactivated), data classification, interagency sharing (a full month sampled, all justified), public log of use (monthly reports reviewed), BCA notification, and breach notification. No exceptions noted. Companion AXON-system audit filed the same season under LRL 261168.

CLOSEOUT AUDIT. All 8 statutory sub-areas (policy, retention, data security/access, data classification, inter-agency sharing, public log of use, BCA notification, biennial audit) marked compliant; no findings or recommendations recorded. This is a closeout audit covering the full life of White Bear Lake PD's Motorola embedded ALPR system (7 mobile squad units, no stationary cameras), which was operational 2024-10-26 to 2026-07-29 and has since been terminated. Auditor verified the 60-day retention setting in the control panel, reviewed user accounts/roles, and sampled a full month of inter-agency search justifications (all found justified). The report also states the department asked BCA to remove its listing from the public LPR-agency roster following the shutdown.

Clean sheet. Zero findings recorded across all nine statutory areas reviewed: policy (General Order #528), retention, access control, data classification, interagency sharing, public log of use, BCA notification, biennial-audit commitment, and breach notification (handled by cross-reference to the Protected Information Policy, Minn. Stat. 13.055). Retention confirmed at the Flock 30-day manufacturer default, inside the 60-day statutory cap; four stationary Flock units. The report's only recommendation is scope-limiting rather than corrective: "We recommend that all ALPR policies be reviewed by Minnetrista's legal and compliancy departments, as this audit does not render a legal opinion on policy matters." Conducted by Dimitrios Hilton, Senior Auditor, MNSec.

Second Flock-system audit for this agency. No findings.

First Flock-system audit (system installed 2024). No findings.

Companion audit to Robbinsdale PD's Flock-system report (LRL 251675); this one covers the department's AXON mobile ALPR system — 11 active mobile units, installed January 2024 and operational 1/1/2024 through 12/31/2025. MNSec (Dimitrios Hilton, Senior Auditor) found the department compliant on every audited area: policy, record retention (30-day manufacturer default), data security and access control, data classification, sharing among law enforcement agencies, public log of use, BCA notification, the biennial public accountability audit itself, and breach notification (City Incident Response Policy, Minn. Stat. 13.055). The report states the AXON administrative control panel was audited, all user and administrator roles were reviewed against job descriptions, and the system's audit trail was sampled to confirm it logs user access; BCA notification was validated on the BCA website. No findings, exceptions, or recommendations recorded.

GHOST FINDING — a problem found and fixed during the audit but never recorded as a finding. The report states Oakdale 'now compiles monthly reports' meeting the subd. 5 public-log requirement and that 'as a result of this audit' the department 'is now in compliance with this part of the statute' — meaning it was out of compliance until the auditor showed up. Final report: compliant, no findings recorded. Rated as no findings because that is what the report records. See FinePrint feed: The ghost findings of Minnesota's ALPR audits.

No findings. Auditor given direct administrative access to the live Axon system rather than relying on screen prints supplied by the agency.

No findings. Auditor given direct administrative access to the live Flock system rather than relying on screen prints supplied by the agency.

GHOST FINDING — MNSec records zero findings, but its own narrative states that UMN PD "now compiles" the monthly public log of use required by Minn. Stat. § 13.824 subd. 5, and that only one month of sample reports was reviewed. No exception was recorded for the rest of the period. Same language and same pattern as the companion Flock report and as the Olmsted County Sheriff's Office audit. First audit of UMN PD's new AXON system, roughly 29 mobile units operational 3/11/25 to 8/31/25 alongside the agency's existing Flock deployment. Every other section was marked compliant: ALPR Policy 654, 60-day read and hit retention confirmed in the AXON retention settings, access control with a full user and role review, data classification, interagency sharing, BCA notification validated on the BCA website, and the University's data security breach policy. Checklist-depth executive summary of five pages.

Compliant on all nine checklist areas, zero findings recorded: department policy & procedures, record retention, data security and access control, data classification, sharing among law enforcement agencies, public log of use, BCA notification, biennial public accountability audit, and breach notification. 18 stationary Flock cameras, no mobile units; retention set to the Flock 30-day default (statutory max 60). Auditor's conclusion states only that Edina was "using the ALPR System as an effective law enforcement tool for the purpose of combating auto theft and other crimes linked to vehicle license plates." No recommendations, no exceptions, and none of the usual ghost-finding language ("recommend", "should", "did not", "as a result of this audit") appears anywhere in the report.

GHOST FINDING — MNSec records zero findings, but its own narrative states that UMN PD "now compiles" the monthly public log of use required by Minn. Stat. § 13.824 subd. 5, and that only one month of sample reports was reviewed against a two-year audit period running 9/1/23 to 8/31/25. A log-of-use practice that began at or near the audit leaves the earlier months of the period unaccounted for, and the auditor recorded no exception for them. Same pattern as the Olmsted County Sheriff's Office audit. Every other section was marked compliant: ALPR Policy 654, the 30-day Flock default retention confirmed in the administrative control panel, access control with a full user and role review, data classification, interagency sharing documented by agency and case number, BCA notification validated on the BCA website, and the University's data security breach policy. Checklist-depth executive summary of five pages, first audit of the new Flock system.

GHOST FINDING — The report records zero findings, yet its own narrative recommends that Orono "develop a standalone breach policy," noting that breach procedures currently exist only as a reference inside the department's ALPR policy (Policy 3059.0) rather than as a standalone document. A missing or partial breach-notification policy scores as Material under FinePrint's calibration; MNSec described the gap, recommended a fix, and still returned a clean sheet. Everything else was reported compliant: 30-day Flock retention (statutory max 60), role-based access with regular administrative review, ALPR data classified as private, inter-agency sharing requests tracked by agency/requesting party/case number, monthly compliance reports available on records request, BCA notification confirmed, and a commitment to biennial independent audits. Three stationary/flex Flock devices, no squad-mounted units. See "The ghost findings of Minnesota's ALPR audits."

GHOST FINDING — a problem the audit describes but never records. Marked compliant with zero findings, yet the narrative notes the office had not been maintaining a standard set of Log of Use reports, a Minn. Stat. 13.824 subd. 5 requirement, in the now-retired BOSS system. No formal discrepancy was recorded and MNSec offered to assist with future systems. Rated as no findings because that is what the report records; flagged as a major issue because the described gap appears to violate the statute. See FinePrint feed: The ghost findings of Minnesota's ALPR audits.

No findings. MNSec was given administrative access to the PIPS Technology BOSS system; all 6 mobile devices carried 2-day retention settings and no plate reads were detectable after 2 days. Audit trail sampled; log of use reports maintained in BOSS; no inter-agency sharing requests during the period.