7 Tips for Meeting CJIS Password and MFA Requirements

Summary
A sponsored guide outlines CJIS password and MFA practices for law enforcement agencies, including blocking compromised passwords, resetting credentials when compromise is suspected, protecting stored and transmitted passwords, and extending MFA across accounts and log,
Key points
- The guide recommends passphrases of at least 15 characters, exceeding the stated CJIS minimums of eight characters for user-selected passwords or six for qualifying generated passwords.
- Agencies should block common, predictable, compromised, and context-specific passwords, updating the list at least quarterly and when compromise is suspected.
- CJIS requires password changes when credentials are suspected or known to be compromised; the guide also recommends checking existing passwords against breach lists regularly.
- Passwords must be transmitted over encrypted, authenticated channels and stored using salted hashes and a suitable one-way key derivation function.
- MFA is required for privileged and non-privileged accounts and for local, network, and remote access to systems handling CJI.
- CJIS specifies AAL2, requiring two different authentication factors; the guide recommends considering phishing-resistant MFA and regularly auditing authentication controls.
Article Details
- Defense Focus
- Help law enforcement agencies meet CJIS password and MFA requirements and reduce credential-related risk.
- Detection Methods
- Screen passwords against lists of common, predictable, and previously compromised passwords.
- Check existing passwords against breach data at least quarterly and when compromise is suspected.
- Audit Active Directory for weak or compromised passwords and inactive privileged administrator accounts.
- Review authentication controls and access policies to identify accounts and systems without MFA.
- Data Sources
- Compromised-password lists and breach data
- Active Directory account and password audit results
- Authentication systems and access policies
- Platforms
- Active Directory
- Windows logons
- RDP
- VPN
- Compatible SaaS applications using OIDC or SAML
- Defensive Actions
- Use passwords at least as long as CJIS requires; consider passphrases of at least 15 characters.
- Maintain and update a blocklist of weak, predictable, and compromised passwords at least quarterly and when organizational passwords are suspected of compromise.
- Require password changes when compromise is suspected and give users clear feedback when creating or resetting passwords.
- Transmit passwords over encrypted, authenticated channels and store them using salted hashes and a suitable one-way key derivation function.
- Require MFA for privileged and non-privileged accounts and for local, network, and remote access to systems handling CJI.
- Use MFA that meets AAL2 with two different authentication factors; consider phishing-resistant methods.
- Regularly review authentication controls and audit Active Directory for weak or compromised passwords and inactive privileged accounts.
MITRE ATT&CK
T1078 · Valid AccountsThe article says attackers commonly gain access to sensitive systems using compromised passwords.T1110.002 · Password CrackingThe article discusses offline cracking of authentication databases and recommends salted password hashes using a suitable key derivation function.T1557 · Adversary-in-the-MiddleThe article identifies man-in-the-middle attacks as a risk when passwords are not transmitted over encrypted, authenticated channels.T1566 · PhishingThe article warns that credential phishing can be mitigated with phishing-resistant MFA.
Vendors
Products
Specops Password AuditorAs a starting point, Specops Password Auditor performs a free, read-only AD audit that checks for weak or compromised passwords and inactive privileged administrator accounts.Specops Password PolicySolutions like Specops Password Policy with Breached Password Protection can simplify this process with CJIS-aligned password policy templates.Specops Secure AccessSolutions such as Specops Secure Access helps agencies extend MFA to Windows logons, RDP, and VPN connections, with single sign-on (SSO) support for compatible SaaS applications through OIDC and SAML.
