- ClassificationCategoryCybersecurityDomainCybersecurityFramework FamilyOther
- Regulatory ContextTypeFrameworkLegal InstrumentStandardSectorGovernment SectorIndustryGovernment & Public Sector
- Region / PublisherRegionNorth AmericaRegion DetailUnited StatesPublisherFederal Bureau of Investigation (FBI)
- VersioningVersionCJIS Security Policy v6.1 (June 25, 2026); v6.0 completed modernization (December 27, 2024)Effective DateJune 25, 2026 (v6.1); Priority 1 sanctionable since October 1, 2024Issue DateJune 25, 2026
- AdoptionAdoption ModelRegulatory ComplianceImplementation ComplexityHigh
- Official ReferenceOpen Link in New TabSource
License included / downloadable: Yes
The FBI publishes the CJIS Security Policy, version 6.0 and later, as a public document that may be posted and shared without restrictions (section 1.5), and it is included with the platform for reference.
Framework text is licensed by its publisher and is included only where stated above.
- The FBI CJIS Security Policy v6.1 (June 25, 2026) sets minimum security requirements for anyone accessing or handling Criminal Justice Information.
- It applies to criminal justice agencies, noncriminal justice agencies, interface agencies, and their contractors.
- Since October 1, 2024 the pre-modernization and Priority 1 requirements are sanctionable; Priority 2 to 4 wait until September 30, 2027.
- Requirements include multi-factor authentication, FIPS-validated encryption, fingerprint screening and training, and one-hour incident reporting.
- Improper access or dissemination of criminal history records can bring termination of services and criminal penalties.
Overview
The FBI's Criminal Justice Information Services (CJIS) Security Policy, version 6.1 dated June 25, 2026, sets the minimum security requirements for every agency and contractor that accesses FBI CJIS systems or that processes, stores or transmits Criminal Justice Information (CJI). It applies to criminal justice agencies, noncriminal justice agencies and interface agencies, and since version 6.0 (December 27, 2024) it has been a public document.
The FBI CJIS Information Security Officer maintains the Policy, the CJIS Advisory Policy Board (APB) and the National Crime Prevention and Privacy Compact Council approve changes, and each state's CJIS Systems Agency (CSA) administers the security program for its user community through a CJIS Systems Officer (CSO). Since October 1, 2024, the pre-modernization requirements and all Priority 1 requirements are sanctionable, while Priority 2 to 4 requirements are in a zero-cycle status until September 30, 2027 (section 1.4).
Agencies implement the Policy by signing information exchange agreements before sharing CJI (5.1), appointing the roles in section 3.2, fingerprint-screening and training everyone with access (PS-3, AT-2), requiring multi-factor authentication (IA-2), encrypting CJI with FIPS 140-3 certified modules or FIPS 197 (AES) at 256 bits or more (SC-13, SC-28), reporting suspected incidents within one hour (IR-6) and keeping contractors under the CJIS Security Addendum (Appendix H).
Why does it matter?
Misuse or loss of CJI can end an agency's access to FBI systems and expose individuals to criminal penalties. Section 4.2.5.2 states that improper access, use or dissemination of criminal history record information (CHRI) may bring administrative sanctions, including termination of services, and state and federal criminal penalties. The Policy gives agencies one national minimum for preventing that.
Key benefits include:
- One national minimum
The Policy is always the minimum standard; state, local, Tribal, territorial and federal agencies may adopt stricter rules (section 1.3).
- Named roles and owners
Sections 3.2.1 to 3.2.13 define the CSA, CSO, Terminal Agency Coordinator, Agency Coordinator, CSA ISO and others, so each duty has an owner.
- Priorities that guide audits
Each modernized control is marked Existing or Priority 1 to 4, and only existing and Priority 1 requirements are sanctionable until September 30, 2027 (section 1.4).
- A route for contractors
Management control agreements and the CJIS Security Addendum let private contractors support criminal justice functions under FBI-approved controls (sections 3.2.6 and 5.1, Appendix H).
- Public, current text
Version 6.0 and later may be posted and shared without restriction, and version 6.1 folds in the calendar year 2025 changes (sections 1.5 and Change Management).
How does it work?
The Policy has four front sections (introduction, approach, roles and responsibilities, and CJI and personally identifiable information) and section 5, Policy and Implementation, which has 20 policy areas: information exchange agreements (5.1), the control families AC, AT, AU, CA, CM, CP, IA, IR, MA, MP, PE, PL, PS, RA, SA, SC, SI and SR, and mobile devices (5.20). Appendices include the Security Addendum (Appendix H).
Every modernized control carries a marking: Existing, or Priority 1 to 4. Agencies work from the Priority 1 and existing controls first because those are sanctionable, and plan for Priority 2 to 4 before the zero-cycle ends on September 30, 2027. Typical controls include account management (AC-2), literacy training before access and annually (AT-2), weekly audit record review (AU-6), monthly vulnerability scans (RA-5) and assessments at least every three years (CA-2).
In SmartSuite, agencies hold each requirement with its policy area, priority marking, owner and evidence, link it to the systems, vendors and agreements that process CJI, and report readiness by priority.
Key Elements
- Roles and agencies
The CSA appoints a CSO, who cannot be outsourced, and the CSO sets standards for personnel with CJI access. Terminal Agency Coordinators, Agency Coordinators and personnel with security responsibilities support them (3.2).
- CJI and CHRI
CJI covers biometric, identity history, biographic, property and case or incident history data. CHRI is a subset with extra controls, governed by 28 CFR Part 20 (4.1 and 4.1.1).
- NCIC restricted files
Ten NCIC restricted files, including Gang Files and the National Sex Offender Registry Files, are protected as CHRI and may not be disseminated for non-law-enforcement purposes (4.2.2 and 4.2.3.2).
- Information exchange and the Security Addendum
Formal agreements specify security controls before CJI is exchanged, and contractors sign the Security Addendum under 28 CFR 20.33(a)(7) (5.1, Appendix H).
- Identification and encryption
Multi-factor authentication applies to privileged and non-privileged accounts (IA-2(1) and (2)). CJI outside physically secure locations uses FIPS 140-3 certified modules or FIPS 197 (AES) with symmetric keys of at least 256 bits (SC-13 and SC-28).
- Personnel security
Screening before access includes state and national fingerprint-based record checks (PS-3), training before access and annually with records kept three years (AT-2, AT-4), and access disabled within 24 hours of termination (PS-4).
- Incident reporting and logging
Suspected incidents are reported within one hour of discovery, then to the CSO and the FBI CJIS ISO (IR-6). Audit records are reviewed weekly and kept at least one year (AU-6, AU-11).
What does it cover?
The Policy applies to all entities with access to, or operating systems used to process, store or transmit, CJI (section 1.2). Entities exchanging CHRI for noncriminal justice purposes are also bound by Compact Council rules. Transaction control numbers such as the ORI, NIC and UCN are exempt when not accompanied by CJI or personally identifiable information, and CJI released to the public through authorized dissemination, or purged, is no longer protected (4.1).
What are its objectives?
The Policy's essential premise is to protect CJI from creation to dissemination or destruction, whether at rest or in transit (section 1.1).
Protect the creation, viewing, modification, transmission, dissemination, storage and destruction of CJI (1.2).
Keep the Policy the minimum standard while letting agencies set stricter rules (1.3).
Share management among the FBI CJIS Division, CSAs, State Identification Bureaus and interface agencies (2 and 3.1).
Support a risk-based approach to implementing requirements (2.3).
Restrict access, use and dissemination of CHRI under 28 CFR Part 20 (4.2).
Keep the Policy current through the APB's regular updates (Executive Summary).
Framework in Context
The Policy's executive summary cites the Federal Information Security Modernization Act of 2014 as part of its legal basis, and its control families and identifiers follow the NIST SP 800-53 family structure. The Security Addendum rests on 28 CFR 20.33(a)(7), and the Compact Council relies on the Policy as the definitive source for the security and privacy of records exchanged with noncriminal justice practitioners (section 3.1).
Common Framework Mappings
The CJIS Security Policy is often mapped to recognized cybersecurity and compliance frameworks to harmonize security controls, simplify audits, and demonstrate compliance across multiple regulatory and industry requirements.
Mapped frameworks include:
FedRAMP Rev. 5
FISMA
ISO 27001:2022
ISO 27002:2022
NIST CSF 2.0
NIST 800-171 Rev. 3
NIST 800-53 Rev.5
SOC 2
How SmartSuite Supports the CJIS Security Policy
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
Use Compliance Management, Cyber & IT Risk and Third Party Risk Management records to hold the requirement matrix, agreements, training and screening evidence, incident log and vendor files an agency needs to show its CSA.
CJI Boundary and Exchange Agreements
Record where CJI is stored and transmitted, with each information exchange agreement, management control agreement and Security Addendum (5.1, Appendix H).
Requirement Library by Priority
Track requirements by policy area with the Existing or Priority 1 to 4 marking, owner, status and review date (1.4).
Personnel Screening and Training Records
Track screening completion, access approvals, annual training and the three-year training records (PS-3, AT-2, AT-4).
Access, MFA and Audit Log Evidence
Hold account reviews, multi-factor authentication proof and weekly audit record review sign-offs (AC-2, IA-2, AU-6).
Incident Reporting
Record suspected incidents with discovery time, the one-hour report and notices to the CSO and the FBI CJIS ISO (IR-6).
Audit Readiness Reporting
Report evidence coverage by policy area and by sanctionable priority ahead of audits.
Related frameworks

CIS Controls v8.1 is a prioritized set of 18 Controls and 153 Safeguards, in three Implementation Groups, with a new Govern function.

COBIT 2019 is ISACA's framework for governing and managing enterprise IT, with 40 objectives in five domains, six governance principles and 11 design factors.

FedRAMP Rev5 is the legacy FedRAMP certification type: NIST SP 800-53 Rev. 5 baselines, 3PAO assessment and agency authorization for cloud services used by U.S. agencies.

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.
Frequently Asked Questions For CJIS Security Policy (Criminal Justice Information Services Security Policy)
The Policy applies to all entities with access to, or operating systems used to process, store or transmit, Criminal Justice Information (section 1.2). That includes criminal justice agencies, noncriminal justice agencies, interface agencies and private contractors under a management control agreement or the CJIS Security Addendum (sections 3.2.4 to 3.2.6).
CJI is all FBI CJIS-provided data needed by law enforcement and civil agencies, in five categories: biometric, identity history, biographic, property and case or incident history data (section 4.1). Criminal history record information (CHRI) is a subset with extra controls, and 28 CFR Part 20 governs its dissemination (4.1.1). Ten NCIC restricted files are protected as CHRI (4.2.2).
Since October 1, 2024, requirements that existed before the policy modernization and all Priority 1 requirements are sanctionable. Priority 2, 3 and 4 requirements are in zero-cycle status until September 30, 2027 (section 1.4). Version 6.1, dated June 25, 2026, incorporates the calendar year 2025 changes approved by the APB and the Compact Council.
Multi-factor authentication is required for privileged and non-privileged accounts (IA-2(1) and (2)). CJI outside physically secure locations uses FIPS 140-3 certified cryptographic modules or FIPS 197 (AES) with symmetric keys of at least 256 bits, and FIPS 140-2 certificates are not accepted after September 21, 2026 (SC-13, SC-28). Suspected incidents are reported within one hour of discovery (IR-6).
Before exchanging CJI, agencies put formal agreements in place that specify security controls (section 5.1). Private contractors performing criminal justice functions sign the CJIS Security Addendum (Appendix H), authorized by 28 CFR 20.33(a)(7). CJI may be stored in cloud environments only within the physical boundaries of an APB-member country and under the legal authority of an APB-member agency (SC-28).

Put this framework to work in SmartSuite
Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.


