7 Practical Tips for Law Enforcement to Meet Latest CJIS Password and MFA Requirements

The FBI's updated CJIS Security Policy designates password management and multi-factor authentication as Priority 1 controls that law enforcement agencies must implement immediately. Compromised credentials remain a leading attack vector, involved in 44.7 percent of breaches according to Verizon data. The policy requires minimum password lengths of eight characters, quarterly checks against breached password lists, and MFA for all privileged and non-privileged accounts across local, network, and remote access. Agencies are advised to enforce longer passphrases, block weak and compromised passwords in real time, and use salted hashing for stored credentials. Solutions from Specops Software, including Specops Password Policy and Specops Secure Access, provide CJIS-aligned templates, continuous breach screening against more than six billion passwords, and MFA extension to Windows logons, RDP, and VPN. Regular audits with tools such as Specops Password Auditor help identify weak credentials and inactive privileged accounts before exploitation occurs.

BleepingComputerTranslated from English

Read at source

The FBI's latest CJIS Security Policy sets clear requirements for password management and MFA. These are Priority 1 (P1) controls, so must be implemented immediately to comply. Compromised passwords and gaps in multi-factor authentication remain common ways attackers gain access to sensitive systems. For law enforcement agencies handling criminal justice information, protecting against these threats is also a matter of compliance.

This guide contains practical tips to help agencies meet the latest requirements, strengthen their defenses against credential-based attacks, and make ongoing compliance easier to manage.

1. Enforce Stronger Minimum Password Lengths

CJIS requires user-selected passwords to be at least eight characters long, or six characters if generated by a credential service provider or verifier using an approved random number generator. However, experts recommend going beyond these minimums and encouraging passphrases of at least 15 characters. Longer passwords are generally harder to crack, and passphrases can be easier to remember than shorter passwords with complex combinations of symbols and numbers. CJIS doesn't require traditional complexity rules, so focus on length and strength rather than arbitrary character requirements.

2. Block Weak and Compromised Passwords

Agencies must maintain a list of commonly used, predictable, and compromised passwords. This should include passwords exposed in previous breaches, dictionary words, sequential characters, and context-specific terms such as usernames or agency names. CJIS requires agencies to update this list at least quarterly, and whenever organizational passwords are suspected of being compromised. Solutions like Specops Password Policy with Breached Password Protection can simplify this process with CJIS-aligned password policy templates.

Verizon’s Data Breach Investigation Report found stolen credentials are involved in 44.7% of breaches. The Breached Password Protection feature delivers continuous screening against a growing database of more than six billion compromised passwords.

3. Reset Passwords Quickly and Give Users Clear Feedback

Agencies must force a password change whenever there's evidence that a credential has been compromised. Don't rely solely on scheduled password changes to address exposed credentials. You must also check existing passwords against the breach list at least quarterly. CJIS also requires users to select a new password immediately whenever compromise is suspected. When a user does need to create or reset a password, provide clear, real-time feedback that helps users understand what makes a password weak and how to improve it.

4. Protect Passwords in Transit and At Rest

CJIS also requires passwords to be transmitted over encrypted, authenticated channels to prevent interception and man-in-the-middle attacks. When stored, passwords must be salted and hashed using a suitable one-way key derivation function, making them more resistant to offline cracking if an authentication database is compromised. Agencies should review how their applications and authentication systems handle credentials to ensure these protections are in place.

5. Require MFA For All Privileged and Non-Privileged Accounts

CJIS requires MFA for both privileged and non-privileged organizational accounts. Don't focus solely on administrator accounts. Standard user accounts can also give attackers access to sensitive data or provide a foothold for further attacks. Review your accounts and access policies to identify where MFA is missing, including accounts belonging to employees and contractors.

6. Extend MFA Across All Relevant Access Methods

CJIS requires MFA for local, network, and remote access. Agencies should review authentication across their environment, ensuring that all systems that touch CJI are adequately protected. Solutions such as Specops Secure Access helps agencies extend MFA to Windows logons, RDP, and VPN connections, with single sign-on support for compatible SaaS applications through OIDC and SAML.

7. Make Sure Your MFA Methods Meet CJIS Requirements

CJIS specifies Authenticator Assurance Level 2 (AAL2), which requires two different authentication factors. This is a combination of something you know (like a password), something you have (like a smart card), or something you are (like a fingerprint). Review your authentication methods to ensure they meet these requirements. Where possible, consider phishing-resistant MFA methods to provide stronger protection against credential phishing and adversary-in-the-middle attacks.

CJIS compliance doesn't end once you've implemented strong password policies and MFA. Regularly reviewing your authentication controls, checking for compromised credentials, and auditing Active Directory can help you identify security gaps before attackers exploit them. As 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.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Policy & Regulation

Microsoft Announces Windows Server 2028 with Hardened Security Defaults and New Baselines
NSA's Classified NSANet Network Suffers Temporary Outage During Routine Maintenance Amid Wave of Government and Corporate System Disruptions
Trump Administration Issues New Rules to Block China From Indirect Access to U.S. AI Chips via Remote Computing