Ongoing account takeover attempts via stolen credentials and multi-factor authentication (MFA) vulnerabilities represent the most prominent challenge for security agencies in protecting sensitive systems. For law enforcement agencies handling Criminal Justice Information (CJI), securing these aspects is not just a security measure, but a mandatory requirement to ensure compliance with the Criminal Justice Information Services security policy issued by the FBI.
The latest CJIS policies define strict controls classified as Priority 1 (P1), meaning they must be implemented immediately. To facilitate this complex task within agencies' technical infrastructures, we outline below the most prominent recommended practical steps to enhance protection and achieve continuous compliance.
1. Enforcing Minimum Password Length and Focusing on Passphrases
The CJIS policy requires that passwords chosen by users be at least eight characters long, or six characters if generated by a certified service provider using a random number generator. However, it is recommended to exceed this minimum and adopt passphrases of at least 15 characters, as they are harder to crack and easier to remember compared to short, complex ones.
2. Blocking Weak and Compromised Passwords
Agencies must maintain an updated list of common and predictable passwords and those leaked in previous breaches, including dictionary words, numeric sequences, and terms associated with usernames or agencies. The policy mandates updating this list at least every three months, and whenever a breach is suspected.
3. Rapid Password Resets and Providing Immediate User Feedback
The policy mandates changing passwords immediately if there is any evidence of leakage, rather than relying solely on scheduled periodic changes. When creating or resetting a password, it is preferable to provide immediate and clear feedback to the user regarding the reasons for a weak password and how to improve it, instead of generic error messages.
4. Protecting Passwords in Transit and at Rest
CJIS directives require passwords to be transmitted via encrypted and authenticated channels to prevent Man-in-the-Middle (MitM) attacks. Regarding storage, passwords must be encrypted using appropriate one-way key derivation functions (Hashing & Salting) to make them immune to offline brute-force attacks in the event that authentication databases are compromised.
5. Implementing Two-Factor Authentication for All Accounts
The Multi-Factor Authentication (MFA) requirement is not limited to administrator accounts; it extends to include all privileged and non-privileged organizational accounts, including those of regular employees and contractors who may represent an entry point for attackers.
6. Expanding Authentication to Cover All Access Methods
The policy requires enabling two-factor authentication for local access, network connections, and remote access, ensuring the protection of all systems that handle Criminal Justice Information (CJI), whether through direct Windows login or VPN networks.
7. Meeting Authenticator Assurance Level 2 (AAL2) Requirements
The policy specifies Authenticator Assurance Level 2 (AAL2), which requires the use of two different authentication factors based on two of the three elements: something you know, something you have, or something you are (biometrics). It is preferable to rely on authentication methods resistant to phishing attacks.
What Changes Practically for Agencies?
The most significant shift is the transition from traditional, scheduled security measures to continuous monitoring and immediate risk assessment, especially given the increasing reliance on stolen credentials in cyberattacks. Compliance requires a comprehensive review of Active Directory data, updating blocking policies, and integrating periodic scanning tools to ensure vulnerabilities are detected before they are exploited by attackers.