City and county IT teams planning CJIS compliance
Back to Blog
GOVERNMENT Insights Published April 4, 2026 Updated April 4, 2026 9 min read

What Should City and County IT Teams Include in a CJIS Compliance Checklist?

A practical CJIS compliance checklist for city and county IT teams in California covering audits, controls, personnel, and readiness.

By The Datapath Team Primary keyword: cjis compliance checklist city and county IT teams
governmentModestomunicipal

Quick summary

  • Understand how CJIS audits work and what agencies are evaluated on.
  • Build a working CJIS compliance checklist around 13 key control domains.
  • Prepare city and county IT teams for ongoing audit readiness and practical vendor controls.

We understand that for city and county IT teams, managing sensitive data is a core responsibility. When that data includes Criminal Justice Information (CJI), the stakes get significantly higher. This is where the Criminal Justice Information Services (CJIS) Security Policy comes into play. It’s not just a set of guidelines; it’s a mandatory framework established by the FBI to ensure the secure handling, storage, and transmission of CJI. For any agency that interacts with this sensitive data, compliance isn’t optional – it’s essential for maintaining access to critical federal systems and safeguarding national security information. 1

Understanding the CJIS Audit Process

The FBI’s CJIS Division, through its CJIS Audit Unit (CAU) and designated CJIS Systems Agencies (CSAs), conducts formal compliance audits. These audits typically occur on a three-year cycle. 2 While organizations are usually notified months in advance, effective programs operate in a perpetual state of readiness. During an audit, inspectors meticulously evaluate various aspects of your operations. This includes assessing data integrity and handling procedures, inspecting physical security controls, reviewing access management practices, and examining policy documentation and incident response processes. 3 The audit concludes with a debriefing, followed by a formal report detailing findings and required remediation. The CAU then tracks the progress of corrective actions, ensuring documented follow-through.

The 13 Pillars of Your CJIS Compliance Checklist

The CJIS Security Policy (CSP) is built around 13 primary control domains, each representing a critical area that organizations must maintain compliance within to lawfully handle CJI. 4 Think of these as the foundational pillars of your compliance checklist. Let’s break down what each entails for your IT team.

Information Security Policy

At its core, this requires you to have a written policy that clearly outlines how your agency protects CJI. This policy should be comprehensive, accessible, and regularly reviewed to reflect current threats and organizational changes. 5

Security Awareness Training

Your team members are often the first line of defense. Therefore, mandatory security awareness training is crucial. This includes initial training within six months of assignment and regular annual refresher programs to keep staff informed about recognizing cybersecurity threats and protecting sensitive information. 6

Incident Response Plan (IRP)

A robust Incident Response Plan is non-negotiable. This documented plan details the procedures for identifying, containing, reporting, and recovering from any security incidents involving CJI. It ensures a swift and organized response when the unexpected occurs. 7

Auditing and Accountability

This domain focuses on comprehensive logging of all CJI access and activity. It means meticulously tracking who accesses CJI, when they access it, and what actions they perform. This provides an essential audit trail for accountability and forensic analysis. 8

Access Control

Access to CJI must be strictly controlled and limited. This involves implementing role-based restrictions, ensuring that users only have access to the information necessary to perform their specific job functions. 9

Identification and Authentication

Strong credential controls and multi-factor authentication (MFA) are paramount. 10 Every user must be verified before gaining access to systems containing CJI. The recent mandates and increased focus on MFA highlight its critical role in preventing unauthorized access. 11

Configuration Management

This involves maintaining controlled and documented system changes. Any modifications to IT systems must follow a defined process to prevent accidental introduction of weaknesses or deliberate bypassing of security measures. This ensures systems are set up and maintained securely. 12

Media Protection

Safeguards must be in place for both digital and physical media containing CJI. This includes protecting removable media like USB drives and DVDs, as well as ensuring proper disposal of sensitive data when media is no longer needed. 13

Physical Security

Protecting the physical environment where CJI is accessed or stored is vital. This includes implementing facility protections such as surveillance, controlled entry points, and environmental safeguards to prevent unauthorized physical access. 14

Systems and Communications Protection

This domain covers encryption and integrity controls for transmitted and stored CJI. Encryption is required for data in transit over networks, especially when using the internet, and for data at rest. Ensuring systems are configured properly protects data as it moves through your network.

Formal Audit Participation

Successfully completing the triennial compliance reviews is a key requirement. This involves actively participating in audits and demonstrating adherence to the CJIS Security Policy. 15

Personnel Security

This pillar emphasizes thorough vetting of individuals who handle CJI. This typically includes fingerprint-based background checks and lifecycle-based access management, ensuring that only trustworthy personnel have access to sensitive data. 16

Mobile Device Controls and Remote Access

With the increasing use of mobile devices and remote work, securing these endpoints is critical. This requires establishing acceptable use policies and enforcing safeguards for smartphones, tablets, laptops, and any remote devices accessing CJI. 17

For IT departments in city and county governments, the path to CJIS compliance can present unique challenges and considerations. Understanding these nuances is key to building an effective strategy.

The Role of IT Departments

Your IT department is central to CJIS compliance. You are responsible for implementing and maintaining many of the technical controls required by the CSP. This includes managing network security, access controls, system configurations, and ensuring data is protected both at rest and in transit. 18 You’ll also play a crucial role in supporting audits by providing system logs, documentation, and technical explanations.

Managing Third-Party Vendors and Outsourcing

Many government agencies rely on third-party vendors or outsourced services for IT operations. When these vendors handle CJI, they must also be CJIS-compliant. This often involves signing a CJIS Security Addendum to their agreements, which ensures they adhere to the same security standards. 19 It’s essential to have clear Information Exchange Agreements (IEAs), such as Memoranda of Understanding (MOUs) or Management Control Agreements (MCAs), that define data-sharing protocols, logging, audit, and security control requirements between your agency and any external entities, including other government departments or private contractors. 20

Common Pitfalls and How to Avoid Them

Even with diligent efforts, common gaps can emerge. These might include a lack of Multi-Factor Authentication (MFA) on all systems accessing CJI, missing background checks for personnel, weak password policies, insufficient audit logs, noncompliant mobile device usage, or inadequate user training on data handling. 21 The surprise MFA mandate in October 2024, for instance, caught many organizations off guard. 22 Proactive internal audits and a thorough understanding of the CSP can help identify and rectify these issues before an official audit.

Achieving and Maintaining CJIS Compliance

Compliance isn’t a one-time task; it’s an ongoing commitment. Building a sustainable compliance program requires a strategic approach.

Proactive Preparation and Documentation

Operating in a constant state of readiness is key. This means regularly assessing your current security measures, conducting internal pre-audits using the CSP as a checklist, and meticulously documenting all policies, procedures, and rectifications. 23 Maintaining detailed logs and documentation is crucial for demonstrating adherence during audits. 24

Leveraging Technology and Expertise

While your IT team is vital, the complexity of CJIS compliance can be overwhelming. Consider leveraging technology solutions designed for CJIS compliance, such as those offering encrypted network connections, zero trust security, and continuous monitoring. 25 Partnering with experienced compliance consultants or technology providers who understand CJIS requirements can also significantly lighten the load, assisting with risk assessments, control implementation, documentation review, and remediation planning. 26 Some services even offer “Compliance as a Service” (CaaS) models to augment your internal IT resources. 27

Conclusion: Your Path to CJIS Readiness

Achieving and maintaining CJIS compliance is a multifaceted endeavor that touches upon technical, administrative, and physical security domains. For city and county IT teams, it requires a deep understanding of the CJIS Security Policy, a commitment to rigorous auditing and documentation, and a proactive approach to managing risks associated with data handling, personnel, and third-party vendors. By systematically addressing each of the 13 control domains, staying informed about evolving requirements, and leveraging available expertise and technology, your agency can build a robust compliance posture, ensuring the security of Criminal Justice Information and maintaining vital access to federal systems.

Additional Resources

Footnotes

  1. CJIS Compliance Checklist | Omega Systems

  2. CJIS-Compliance Guide for Police Chiefs and Municipal Leaders | VC3

  3. Criminal Justice Information Services (CJIS) Security Policy

  4. Your CJIS compliance checklist for public safety tech rollouts

  5. Information Security Policy - NIST SP 800-53

  6. Security Awareness Training Overview

  7. Incident Response Plan Requirements

  8. Auditing and Accountability Controls

  9. Access Control Guidance

  10. MFA and Identity Controls

  11. October 2024 MFA Guidance

  12. Configuration Management Best Practices

  13. Media Protection Guidance

  14. Physical Security in Government Networks

  15. Formal Audit Participation Requirements

  16. Personnel Security and Background Checks

  17. Mobile Device Controls and Remote Work

  18. CJIS CSP Overview

  19. CJIS Security Addendum Requirements

  20. Information Exchange Agreements

  21. Common CJIS Gaps

  22. MFA Mandate for CJIS Users

  23. Pre-audit Readiness Checklist

  24. Audit Evidence and Documentation

  25. SASE and Zero Trust for Public Sector

  26. Compliance Consultants and Vendor Support

  27. CJIS compliance as a service

See also

Disclaimer: This blog is intended for marketing purposes only, and nothing presented in here is contractually binding or necessarily the final opinion of the authors.

Need a practical roadmap for regulated-industry IT performance?

Datapath can benchmark your current model and define the next 90 days of high-impact improvements.

Book a Consultation