CJIS · United States

CJIS audit logging, with no vendor staff in your chain.

What the FBI's CJIS Security Policy v6.1 asks of your audit records: weekly review, at least a year of retention, and screening for anyone with access to unencrypted CJI. nano runs in your agency's environment, and nano has no standing access to your install.

Buy nano
Talk to sales
What is sanctionable when

Existing requirements now. The rest after 30 September 2027.

Version 6 modernized the policy. Requirements tagged [Existing] and Priority 1 are sanctionable; Priority 2, 3 and 4 requirements sit in a zero-cycle until 30 September 2027.

  1. 1 Oct 2024 In effect

    Zero-cycle begins

    [Existing] requirements and Priority 1 requirements are sanctionable. Priority 2, 3 and 4 modernized requirements enter the zero-cycle.

    le.fbi.gov · CJIS v6.1 ↗
  2. 25 Jun 2026 In effect

    Version 6.1 published

    The current CJIS Security Policy. Version 6.0 was published on 27 December 2024.

    le.fbi.gov · CJIS v6.1 ↗
  3. 30 Sep 2027 Next

    Zero-cycle ends

    After this date, Priority 2, 3 and 4 requirements, including AU-2 and IR-6, are no longer in the zero-cycle.

    le.fbi.gov · CJIS v6.1 ↗
What the policy requires

CJIS logging, control by control.

The policy's own words, what they mean in practice, and where nano fits.

CJIS Security Policy v6.1: audit and accountability, incident response

Binding on agencies with access to CJI, and on contractors through the CJIS Security Addendum, as a condition of CJIS access. Tags are the policy's own: [Existing] requirements are sanctionable now; [Priority 2] requirements are in the zero-cycle until 30 September 2027.

Ref What the policy says In plain English How nano helps
AU-6 [Existing] "Review and analyze system audit records weekly for indications of inappropriate or unusual activity…" le.fbi.gov · CJIS v6.1 Someone looks at the audit records every week, for signs of misuse.
Detections watch every source as events arrive, and a weekly review becomes a saved search or a scheduled report you work through, with findings kept as cases.
AU-11 [Existing] "Retain audit records for a minimum of one (1) year or until it is determined they are no longer needed for administrative, legal, audit, or other operational purposes…" le.fbi.gov · CJIS v6.1 Keep audit records for at least a year.
Retention defaults to 365 days on storage your agency owns, and you can set it longer. Older data can be tiered to your own object storage and stays searchable. For a 12-month rule, set at least 366 days so a full year is always kept.
AU-3 [Existing] Records must establish "What type of event occurred; When…; Where…; Source…; Outcome…; and Identity of any individuals, subjects, or objects/entities associated with the event." le.fbi.gov · CJIS v6.1 Each record answers what, when, where, from where, with what result, and who.
Parsers for the sources you choose from the catalog extract these fields from each event, so you can search by time, source, outcome and user across systems.
AU-2 [Priority 2] Log "All successful and unsuccessful: 1. System log-on attempts…", permission use, password changes, "Actions by privileged accounts", and attempts to access, modify or destroy the audit log file. "Review and update the event types selected for logging annually." le.fbi.gov · CJIS v6.1 Log sign-ins, permission use, password changes, privileged actions and tampering with the logs, successes and failures, and revisit the list every year.
Every install starts with zero log sources: you pick the sources that produce these events from the catalog. The annual review of event types stays with you.
IR-6 [Priority 2] "report suspected incidents to the organizational incident response capability immediately but not to exceed one (1) hour after discovery", and to "the CSO, SIB Chief, or Interface Agency Official, and FBI CJIS ISO." le.fbi.gov · CJIS v6.1 Report suspected incidents internally within an hour of discovery, and to the listed CJIS contacts. In the zero-cycle until 30 September 2027.
Alerts reach your team as detections fire, and cases collect the evidence for the report. Reporting stays with you.

CJIS Security Policy v6.1: personnel and contractors

These decide which vendor staff your agency has to screen.

Ref What the policy says In plain English How nano helps
PS-3 [Existing] "state of residency and national fingerprint-based record checks shall be conducted." le.fbi.gov · CJIS v6.1 People with access to unencrypted CJI, vendor staff included, go through fingerprint-based checks.
nano has no standing access to your install. Support sees only what you choose to share. There are no nano staff to put through your screening for log data.
SA-9 [Existing] "All private contractors who perform criminal justice functions shall acknowledge, via signing of the CJIS Security Addendum Certification page (page H-8), compliance with all aspects of the CJIS Security Addendum." le.fbi.gov · CJIS v6.1 Contractors performing criminal justice functions sign the Security Addendum.
nano is software your agency runs. Who in your own team or your MSP operates it, and what they sign, is your agency's call. nano will sign the CJIS Security Addendum.
Cloud and SaaS A SaaS provider with "unescorted logical or physical access… to… unencrypted CJI" must meet the personnel screening requirements; the cloud provider beneath it does not, where "the SaaS provider maintains the encryption keys." le.fbi.gov · CJIS v6.1 A SaaS SIEM that holds your CJI-bearing logs unencrypted brings its staff into your screening chain.
With nano, the logs stay in your environment and nano never receives them, so there is no SaaS provider in that position for your log data.

Run weekly reviews with scheduled reports, keep findings and evidence in case management, and set retention in storage and retention.

Vendor access and screening

Your logs can be CJI. Keep them where you screen the people.

Logs from CJI systems, such as query terms and record identifiers, can themselves be CJI. Who can reach those logs decides who your agency has to screen.

Your environment

Your agency's network, your own cloud account, or an air-gapped network

01 · Sources
  • CAD / RMS
  • firewall
  • VPN
  • identity provider
  • Windows
  • mobile data terminals
02 · nano
  • Collect and parse
  • Detections and alerts
  • Search and cases
03 · Your storage
  • Disks you own
  • Optional object storage tier
  • Retention you set
Optional · AI pivt AI calls your model endpoint directly: any OpenAI-compatible API (including self-hosted models) or the Anthropic Messages API. Off by default; model calls never go through nano.
nano, the vendor

Never receives your logs.

Connected
  • Daily license check-in: deployment ID, install ID, version
  • Hourly content and enrichment-feed updates (no data sent; can be turned off)
  • One number per day: total GB ingested
  • Downloads: log-source catalog, detection rules and SOAR content, enrichment feeds, releases
Air-gapped
  • No connection to nano at all
  • Offline license file, renewed by hand
fig 01 · nano runs inside your agency's environment. Log data is never sent to nano.
No standing access

Support sees only what you share.

nano has no standing access to your install. Support sees only what you choose to share. nano staff do not join your CJI screening chain for log data. You don't need to send support any CJI, and nano will sign the CJIS Security Addendum.

One year · AU-11

Retention on storage you own.

Event retention defaults to 365 days. Keep what your policy needs, and tier older events to your own object storage, where they stay searchable. Storage and retention

Air-gapped

No connection to nano at all.

Included with every license, if your network requires it: a signed image bundle, content packs you import by hand and an offline license. Air-gapped deployment

FAQ

Questions we get asked.

What is the CJIS Security Policy?

The FBI Criminal Justice Information Services (CJIS) Security Policy sets the security requirements for agencies, and their contractors, with access to criminal justice information (CJI). Compliance is a condition of CJIS access and is enforced through audits and sanctions. The current version is 6.1, published on 25 June 2026.

How long must CJIS audit logs be kept?

AU-11 requires audit records to be retained "for a minimum of one (1) year or until it is determined they are no longer needed for administrative, legal, audit, or other operational purposes". It is tagged [Existing], and the policy says [Existing] requirements "continue to be auditable and sanctionable."

How often must CJIS audit logs be reviewed?

Weekly. AU-6 requires agencies to "Review and analyze system audit records weekly for indications of inappropriate or unusual activity". It is an [Existing] requirement.

What is the CJIS zero-cycle?

Section 1.4 of the policy says that from 1 October 2024, requirements that existed before the modernization (version 5.9) and Priority 1 requirements are sanctionable. Priority 2, 3 and 4 modernized requirements are in a zero-cycle that began on 1 October 2024 and ends on 30 September 2027. AU-2 (event logging) and IR-6 (one-hour incident reporting) are Priority 2.

Is there a CJIS certification? Is nano CJIS compliant?

There is no CJIS certification: the FBI does not certify products. Agencies are audited on how they meet the policy. nano, LLC holds no CJIS-related certification or approval. It is the SIEM you run to collect, review and keep the audit records the policy asks for.

Does a SIEM vendor need CJIS fingerprint checks?

Under PS-3, people with access to unencrypted CJI, vendor staff included, go through state of residency and national fingerprint-based record checks, and the policy's cloud example applies this to a SaaS provider with unescorted access to unencrypted CJI. Logs from CJI systems can themselves contain CJI. A SIEM you run yourself, where the vendor never receives the logs, does not put vendor staff in that position for log data.

Does nano have access to our CJI?

No. nano runs in your agency's environment, and nano has no standing access to your install. Support sees only what you choose to share. A connected install sends nano a daily license check-in and one usage number per day (total GB ingested), and downloads content and feeds; air-gapped installs send nothing.

Who has to follow the CJIS Security Policy?

Agencies with access to CJI, such as state and local law enforcement, sheriff's offices and other criminal justice agencies, and private contractors performing criminal justice functions for them, through the CJIS Security Addendum.

Primary sources

Read the rules yourself.

  1. FBI, Criminal Justice Information Services (CJIS) Security Policy, version 6.1 (25 June 2026)

Last reviewed 13 November 2026. Regulations and guidance change, so read the current version at the source.

Start with nano.

From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.

Buy nano
Talk to sales