The FBI's updated CJIS Security Policy tightens password and MFA rules for law enforcement agencies. Here are seven practical steps to meet them without the scramble.
The FBI's latest CJIS Security Policy just raised the bar on passwords and multi-factor authentication. If you work in law enforcement IT, you already know what that means: privileged and non-privileged accounts both need stronger protection, and the clock is ticking. The good news? Getting compliant isn't as painful as it sounds — if you approach it in the right order.
Here are seven practical steps to meet those requirements, block compromised passwords, and keep your compliance auditor smiling.
### 1. Start With a Real Password Policy
Most agencies have a password policy. Fewer have one that actually holds up. CJIS wants minimum length, complexity, and expiration rules that apply to every account — not just the admins. Write it down, publish it, and make sure new hires see it on day one.
### 2. Screen Passwords Against Breach Lists
This is the step people skip. A password can meet every complexity rule and still be sitting in a public breach dump. Screen every new password against known compromised lists and block matches automatically. It's one of the cheapest security wins you'll ever get.
### 3. Enforce MFA Everywhere — No Exceptions
Privileged accounts, non-privileged accounts, remote access, on-site logins. CJIS doesn't want MFA on some accounts; it wants it on all of them. If you're still making exceptions for "that one legacy system," that system is now your biggest risk.
### 4. Kill Shared and Default Credentials
Shared logins are a compliance nightmare and an accountability black hole. Default credentials are worse. Track down every shared account, every vendor default, and every "temp" login that's been alive since 2019. Retire them or convert them to named accounts with proper MFA.
### 5. Lock Down Privileged Access
Admins should have two accounts: one for daily work, one for privileged tasks. That separation limits the blast radius if a standard account gets compromised. Pair it with just-in-time access so admin rights are granted when needed — not standing open all day.
### 6. Audit, Log, and Review
Compliance isn't a one-time project. Set up logging for authentication events, failed logins, and MFA changes. Then actually review those logs. An auditor will ask how you'd catch a compromised account, and "we'd probably notice" isn't an answer.
### 7. Train Your People — Then Test Them
Technology only goes so far. Run short, regular training on phishing, password hygiene, and MFA fatigue attacks. Then send a test phishing email and see who clicks. The results will tell you more than any policy document ever could.
> "Compliance isn't about passing an audit once. It's about building habits that hold up when nobody's watching."
### The Bottom Line
CJIS password and MFA requirements aren't going away, and they'll likely tighten again. Agencies that treat this as a checklist will keep scrambling every cycle. Agencies that build it into daily operations — breach screening, universal MFA, privileged access separation — will barely notice the next update.
Start with the gaps you already know about. Fix the shared accounts. Turn on MFA everywhere. Screen those passwords. You'll be surprised how much ground you cover in a week.