Weak credentials and incomplete multi-factor authentication deployments remain primary attack vectors for unauthorized access to critical systems. For law enforcement organizations managing criminal justice information (CJI), these vulnerabilities carry regulatory weight—the FBI's current CJIS Security Policy mandates strict controls over both password management and MFA as Priority 1 (P1) requirements, meaning immediate implementation is necessary for compliance.
Achieving these standards across law enforcement IT infrastructure presents real challenges, particularly given the distributed and complex environments typical of the sector. This guide outlines practical strategies to help organizations meet current CJIS mandates, reduce credential-based attack surface, and streamline ongoing compliance efforts.
1. Enforce Stronger Minimum Password Lengths
CJIS establishes a floor of eight characters for user-selected passwords, or six characters when a credential service provider or verifier generates them using an approved random number generator. Moving beyond these baselines to require passphrases of at least 15 characters significantly improves security posture. Extended passwords present substantially greater resistance to cracking attempts, and memorable passphrases often outperform shorter strings laden with symbols and numerals in both security and usability.
The CJIS framework does not mandate traditional complexity rules, allowing organizations to prioritize length and overall strength over prescriptive character-type requirements.
2. Block Weak and Compromised Passwords
Organizations must maintain and enforce a blocklist of commonly used, predictable, and previously compromised passwords. This inventory should encompass passwords surfaced in historical breaches, dictionary terms, sequential character patterns, and organization-specific strings including employee names and agency identifiers.
CJIS mandates quarterly updates to this blocklist, plus immediate updates whenever organizational credentials show signs of compromise. Tools offering breach-aware password policy templates aligned with CJIS can streamline implementation, enabling creation of unlimited custom dictionaries tailored to each agency with fine-grained controls for blocking weak patterns. Continuous screening against databases containing more than six billion documented compromised passwords provides ongoing protection as new breaches emerge.
3. Reset Passwords Quickly and Give Users Clear Feedback
When evidence surfaces that a credential has been exposed, CJIS requires immediate password replacement rather than reliance on periodic scheduled changes. Quarterly checks against breach databases are mandatory; more frequent validation can surface compromised credentials sooner, giving security teams time to respond before exploitation occurs.
CJIS also stipulates that users immediately select new passwords upon suspected compromise. During password creation or reset operations, organizations should provide actionable, real-time guidance rather than generic error messages—helping users understand password weaknesses and how to strengthen them. This approach reduces help desk load while supporting users in creating credentials that are both strong and memorable.
4. Protect Passwords in Transit and At Rest
Strong password requirements represent only part of the equation. CJIS mandates that passwords traverse encrypted, authenticated channels to prevent interception and man-in-the-middle attacks. When stored, passwords must undergo salting and hashing via a suitable one-way key derivation function, substantially reducing vulnerability to offline cracking if an authentication database is compromised.
Organizations should audit how applications and authentication systems manage credentials throughout their lifecycle to confirm these protections are operational.
5. Require MFA For All Privileged and Non-Privileged Accounts
CJIS mandates MFA for both privileged and non-privileged organizational accounts. Limiting MFA deployment to administrative accounts leaves standard user accounts exposed—these can serve as entry points to sensitive data or springboards for lateral movement. Organizations must inventory their accounts and access policies to identify MFA gaps, including those belonging to employees and external contractors.
6. Extend MFA Across All Relevant Access Methods
CJIS requires MFA coverage for local, network, and remote access pathways. Organizations should conduct a comprehensive review of authentication across their infrastructure to ensure all systems handling CJI receive adequate protection. Solutions enabling MFA for Windows logons, RDP, and VPN connections—with single sign-on support for compatible SaaS platforms via OIDC and SAML—help close gaps across diverse access methods.
7. Make Sure Your MFA Methods Meet CJIS Requirements
CJIS specifies Authenticator Assurance Level 2 (AAL2), requiring two distinct authentication factors drawn from three categories: something known (password), something possessed (smart card), or something inherent (biometric). Organizations should validate that their authentication methods satisfy these specifications. Where feasible, phishing-resistant MFA approaches—such as hardware security keys—offer enhanced protection against credential phishing and adversary-in-the-middle scenarios.
Keep Your Authentication Controls Effective
CJIS compliance extends beyond initial implementation. Continuous review of authentication controls, periodic checks for compromised credentials, and Active Directory auditing help organizations identify security gaps before attackers can exploit them. Free, read-only directory audits can assess password strength, identify compromised credentials, and flag inactive privileged administrator accounts, with results presented in interactive reports that clarify current exposure.
By layering robust authentication controls with regular security assessments, law enforcement agencies can substantially reduce credential-related risk and sustain CJIS compliance over time.