That gap matters at audit time. Policies may describe one environment while staff rely on shared workstations, printed records, informal file storage, older integrations, or vendor support paths nobody has reviewed in years. When the documented boundary drifts from daily operations, the LASO ends up hunting for missing facts while leadership is asked to vouch for a scope it never really approved.
The goal is not to treat the whole environment as CJIS scope. It is to identify where criminal justice information (CJI) lives, how it moves, who can reach it, and which CJIS security policy protections apply. This guide is written for the people who must defend that answer: agency leaders who approve scope and own risk, LASOs who maintain the System Security Plan and evidence, and the agency, city, or county IT staff who run the systems. Scoping sets the boundary; it does not operate the controls or produce audit evidence on its own.
Define your CJIS scope by mapping how criminal justice information moves Many agencies start CJIS preparation by asking which controls to satisfy. Controls only mean something once leadership and the LASO agree on which systems, people, devices, vendors, facilities, and data flows fall inside the boundary.
Follow the work, not the org chart. Look at how records staff, officers, dispatchers, evidence personnel, supervisors, IT staff, and vendors actually interact with CJI, and compare that with what is documented.
The decision rule for the LASO is simple: include an asset, user, process, location, or connection when it handles criminal justice information, and document its exclusion when you can show it does not. If you cannot support either conclusion, the boundary is not ready.
A five-step CJIS scoping process for LASOs and IT staff
A repeatable scoping process gives the LASO and IT staff decisions, owners, and artifacts they can maintain:
- Discover and classify. Inventory systems, devices, users, applications, vendors, locations, and interconnections that may handle CJI, including where it enters and leaves.
- Map access and data flows. Document how staff and third parties access, process, transmit, print, discuss, or store the information, including paper and physical workflows.
- Define and validate the boundary. Record what is in and out, why, and which agency leader approved it. Check the result against frontline workflows.
- Assign remediation and evidence. Name owners, target dates, dependencies, and the evidence the LASO will need to show protections are operating.
- Review and improve. Revisit the boundary when systems, policies, vendors, integrations, facilities, or practices change.
The process is done when the agency can defend the boundary and keep it current, not when interviews end.
Five questions LASOs should answer before leadership approves scope
LASOs can use these questions to check whether the proposed boundary reflects actual operations before presenting it to leadership:
- Where is criminal justice information handled? Does the inventory cover access, processing, transmission, printing, discussion, storage, and disposal?
- Who or what can reach it? Are staff roles, shared devices, service accounts, vendor support paths, and system connections represented?
- How does it move? Do data-flow records cover exchanges among municipal, county, state, federal, and third-party systems?
- Does documentation match daily work? Have frontline personnel validated the processes described by leadership, policies, and the System Security Plan?
- Can the organization defend exclusions? Is there a documented basis for keeping unrelated systems, users, or locations outside the boundary?
If any answer lacks evidence, narrow your claims and keep discovering before treating the scope as settled.
Why under-scoping fails CJIS audits and over-scoping strains budgets
Under-scoping happens when an agency misses a device, application, location, vendor, or exchange that handles CJI . It usually surfaces during an audit, an incident, or a modernization project, and it lands on the LASO to explain.
Over-scoping is the opposite problem, and it lands on leadership’s budget. Treating every system as in scope adds cost, complicates operations, and applies controls to staff and systems that do not need them. During a cloud migration, it can turn a manageable compliance effort into a broader redesign.
Include what you can show handles the information, exclude what you can show is separated, and investigate the rest. More scope is not automatically safer scope.
Test the boundary against what officers, dispatchers, and records staff actually do
Agency leaders can explain policy, ownership, and risk tolerance. Frontline staff can explain how work actually happens. A defensible boundary needs both.
Consider an officer querying records from a patrol vehicle, a records clerk printing documents, an evidence technician keeping physical files, a dispatcher in a shared space, and a vendor supporting an application after hours. The LASO should confirm which systems and accounts each uses, where the information travels, which locations are involved, and whether all of it appears in the documented scope.
These conversations surface forgotten integrations, shared devices, paper workflows, external support accounts, and undocumented systems. If the System Security Plan does not describe what staff actually do, it is not ready to defend.
Six CJIS audit readiness artifacts your LASO should maintain after discovery
Discovery should leave agency leaders and the LASO with materials they can use for planning, remediation, audits, and change control:
- A scope statement: Included and excluded systems, with the basis for each decision.
- An inventory: Devices, users, applications, vendors, locations, and interconnections associated with the boundary.
- Data-flow documentation: A record of how criminal justice information enters, moves through, and leaves the environment.
- A System Security Plan: An accurate description of the agency’s actual operating environment.
- A gap register: Immediate risks separated from longer-term maturity work.
- A remediation roadmap: Accountable owners, target dates, dependencies, and evidence requirements.
A polished document is no substitute for an accurate one. Do not claim processes staff cannot follow consistently or protections you cannot evidence.
Where IT staff and smaller agencies should start remediation
For IT staff, a practical roadmap starts with asset inventory, access control, multifactor authentication where applicable, secure configuration, patching, change management, physical access, vendor oversight, incident response, and evidence retention. The point is to make these processes repeatable so they survive staff turnover and audit pressure.
Smaller agencies, where the LASO often wears several hats, do not need a large compliance program at once. Document where criminal justice information is accessed, identify supporting systems and vendors, set the initial boundary, prioritize the highest-risk gaps, and assign next actions. Then keep the documentation current.
CJIS audit readiness starts with a boundary leadership can approve and the LASO can defend. Follow the information, validate the work, assign ownership, preserve evidence, and let operational reality decide what belongs in scope.
Get help defining your agency’s CJIS boundary
Planet works across Commercial, GCC, and GCC High environments to help law enforcement agencies and the IT teams that support them document current environments, find overlooked access points, define defensible CJIS boundaries, and build System Security Plans, gap registers, and remediation roadmaps. If your leadership team or LASO needs a clearer path before an audit, migration, or modernization effort, contact Planet Technologies today.
Learn More
- Get CJIS v6.0 Ready with Planet
- Microsoft Sentinel for CJIS Compliance
- CJIS Security Awareness Training Program
- Microsoft Managed Services
- Microsoft Expertise
- Microsoft Accelerators
Something else or not sure where to start? Email us at [email protected]
