# The CJIS Security Policy version 6.1, its priority markings and the 2027 zero-cycle end, explained

Version 6.1 of the FBI’s CJIS Security Policy, dated June 25, 2026, incorporates the calendar year 2025 changes to the modernized policy. Existing and Priority 1 requirements are sanctionable now; Priority 2 to 4 requirements sit in a zero-cycle that ends September 30, 2027.

Explainer · Government · Regulation & Compliance. Published November 14, 2026. Last reviewed November 14, 2026.

## At a glance

- Version 6.1 is dated June 25, 2026 and was approved by the CJIS Advisory Policy Board and the Compact Council. Version 6.0 was dated December 27, 2024.
- It applies to all entities with access to, or that operate systems that process, store or transmit, criminal justice information, including contractors.
- From October 1, 2024, requirements existing before the modernization and Priority 1 requirements are sanctionable.
- Priority 2, 3 and 4 requirements are in a zero-cycle from October 1, 2024 to September 30, 2027.
- Multi-factor authentication for privileged and non-privileged accounts is Priority 1; one-hour incident reporting (IR-6) is Priority 2.
- Version 6.1 adds the Spring 2025 corrections and additions and administrative changes approved on November 14, 2025.

The FBI’s Criminal Justice Information Services (CJIS) Security Policy gives criminal justice agencies, noncriminal justice agencies and interface agencies a minimum set of security requirements for access to FBI CJIS systems and information and to protect criminal justice information (CJI) [1]. Version 6.1, dated June 25, 2026, is the current release [1] [2]. It incorporates the calendar year 2025 changes to the policy modernization completed in version 6.0, and the zero-cycle for requirements marked Priority 2, 3 or 4 ends on September 30, 2027 [1]. This explainer covers four parts: who the policy binds, how the priority markings and the zero-cycle work, what version 6.1 changed, and what it asks of contracts and providers.

## Who the policy binds

The policy applies to all entities with access to, or that operate systems used to process, store or transmit, CJI. It sets minimum requirements for the creation, viewing, modification, transmission, dissemination, storage or destruction of CJI, and entities that exchange criminal history record information across state lines for noncriminal justice purposes are also governed by the Compact Council’s rules [1]. The executive summary puts it at the level of the individual: the policy applies to every contractor, private entity, noncriminal justice agency representative or member of a criminal justice entity with access to, or operating in support of, criminal and noncriminal justice services and information [1].

CJI covers all FBI CJIS-provided data that law enforcement and civil agencies need for their missions, including biometric, identity history, biographic, property and case or incident history data [1]. The policy is a floor. An agency may use it as its sole security policy, add a local policy or write its own, but the CJIS Security Policy remains the minimum standard and state, local, tribal, territorial and federal agencies may set stricter requirements [1]. The CJIS Systems Agency runs the security program for its user community and its head appoints a CJIS Systems Officer, a role the policy says may not be outsourced [1].

The executive summary cites the federal information security act of 2014 (FISMA) as further legal basis for the security requirements approved by the CJIS Advisory Policy Board [1].

## Priority markings and the zero-cycle

Since version 5.9.5, modernized requirements carry markings. Under an Advisory Policy Board recommendation approved by the FBI Director, from October 1, 2024 the sanctionable requirements are those that existed before the modernization, in version 5.9, and those marked Priority 1. Sections that were not modernized carry no markings and remain auditable and sanctionable as existing requirements. Requirements marked Priority 2, 3 or 4 are in a zero-cycle that began October 1, 2024 and ends September 30, 2027 [1].

The markings decide what an auditor can sanction today and what becomes sanctionable later. Some examples from version 6.1 [1]:

- **Priority 1:** identification and authentication of organizational users (IA-2), including multi-factor authentication for both privileged and non-privileged accounts and replay-resistant authentication; authenticator management (IA-5); account management (AC-2); remote access (AC-17); continuous monitoring (CA-7); vulnerability monitoring and scanning (RA-5); and flaw remediation (SI-2).
- **Priority 2:** incident reporting (IR-6), under which personnel report suspected incidents to the organization’s incident response capability immediately but not to exceed one hour after discovery, and incident information goes to the CJIS Systems Officer, SIB Chief or Interface Agency Official and the FBI CJIS Information Security Officer. An enhancement adds sharing incident information with the supply chain.
- **Priorities 2 and 3:** the supply chain risk management family (SR), from policy and procedures through supplier assessments, notification agreements, component authenticity and disposal.
- **Existing, Priority 4:** audit record retention (AU-11), at least one year or until the records are no longer needed for administrative, legal, audit or other operational purposes.

Two points follow from the text. A control can mix markings: IR-6 is Priority 2, but its automated reporting enhancement is marked Existing as well as Priority 2 [1]. And the priority list flags controls carried over from version 5.9 with an asterisk [1]. In our reading, a gap assessment that reads only the control-level priority may miss requirements that are already sanctionable. In our view, the useful work before September 30, 2027 is a requirement-by-requirement map of Priority 2 to 4 items to owners, systems and evidence. The FBI publishes a Requirements Companion Document, in PDF and Excel, on its resource center page [2]. That is our suggestion, not a requirement.

## What version 6.1 changed

The change management table records two releases. Version 6.0, “Policy Modernization Completion,” was produced by the Security Policy Modernization Task Force and dated December 27, 2024. Version 6.1, “Incorporate Calendar Year 2025 Changes,” was produced by the CJIS ISO Program Office and dated June 25, 2026. Both were approved by the Advisory Policy Board and the Compact Council [1].

The summary of changes for version 6.1 lists three Advisory Policy Board topics from the Spring 2025 cycle, each titled “Addressing Omissions, Corrections, and Additions to the Modernized CJIS Security Policy,” parts 1 to 3, plus administrative changes approved by the Security and Access Subcommittee on November 14, 2025 [1]. The policy notes that administrative changes are vetted through that subcommittee rather than the full Board process [1]. The version 6.1 text still states the end of the zero-cycle as September 30, 2027 [1].

As captured by the Internet Archive on November 5, 2026, the FBI’s resource center page offers version 6.1 for download [2]. The version 6.0 file is still served by the FBI’s file repository [3]. Both documents are official, and version 6.1 is the one the resource center offers. Our suggestion: agencies and vendors that link to or store the policy may want to check which file their templates and contracts reference. Since version 6.0, the policy is publicly available and may be posted and shared without restriction [1].

## Contracts, contractors and cloud

Before exchanging CJI, agencies must put formal agreements in place that specify security controls, whether the exchange is by email, messaging, web services, fax, paper or information systems [1]. Services, reports and records from a service provider must be regularly monitored and reviewed, the criminal justice agency, authorized agency or FBI keeps sufficient overall control and visibility, including over vulnerabilities and incident reporting, and the provider’s incident process must conform to the policy’s incident requirements [1]. Changes to a provider’s services are managed by the agency, with a risk evaluation based on the criticality of the data and system and the impact of the change [1].

An agency that contracts with a private company under the CJIS Security Addendum or one of the Compact Council’s outsourcing standards is a Contracting Agency and must appoint an Agency Coordinator to manage the agreement [1]. The policy’s own example shows the chain: a local police department signs a memorandum of understanding with its state CJIS Systems Agency, another with the county IT department that includes a management control agreement, and the county outsources operations to a vendor that signs the Security Addendum [1].

Personnel security turns on access to unencrypted CJI. Its requirements apply to everyone with unescorted access to unencrypted CJI, and whatever the model (physical data center, virtual cloud or hybrid), the agency determines who has that access [1]. In the policy’s infrastructure-as-a-service use case, a local agency runs a secure virtual private cloud and holds sole access to the encryption keys; because cloud provider personnel then have no logical or physical access to unencrypted CJI, no fingerprint-based background checks of those personnel are required [1]. In our view, who holds the keys is therefore a design decision with personnel, contract and audit consequences.

Status as checked on November 14, 2026. This explainer summarizes an FBI policy; it is not legal advice. The policy allows each CJIS Systems Agency to impose more stringent or additional protection measures [1].

Moraph’s teams help organizations with work like this. [See our solutions](https://www.moraph.com/solutions).

## Sources

1. Federal Bureau of Investigation, Criminal Justice Information Services Division. Criminal Justice Information Services (CJIS) Security Policy, Version 6.1 (06/25/2026). <https://le.fbi.gov/file-repository/cjis_security_policy_v6-1_20260625-1.pdf> Checked November 14, 2026.
2. Federal Bureau of Investigation, Criminal Justice Information Services Division. CJIS Security Policy Resource Center, Internet Archive copy captured November 5, 2026. <https://web.archive.org/web/20261105062719/https://le.fbi.gov/cjis-division/cjis-security-policy-resource-center> Checked November 14, 2026.
3. Federal Bureau of Investigation, Criminal Justice Information Services Division. Criminal Justice Information Services (CJIS) Security Policy, Version 6.0 (12/27/2024), superseded. <https://le.fbi.gov/file-repository/cjis_security_policy_v6-0_20241227.pdf> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/cjis-security-policy-6-1-priorities-and-zero-cycle-explained>
Publisher: Moraph Insights
