Four Questions To Ask Your Evidence Vendor About CJIS Before October 2027


Most departments do not have an IT director. The chief is the IT department, the policy writer, and the person who answers the city council. Meanwhile, the FBI published a new version of its security policy in June 2026. With the CJIS Security Policy 2027 deadline approaching, your evidence vendor sits in the middle of the work. You do not have to read the policy. You need four answers. These are the CJIS compliance questions to ask an evidence vendor, they take one email, and the answers tell you more about your vendor than a demo will.
What actually changes in October 2027, and what already changed
Two things are true at once. The modernized control set stops getting a free pass on September 30, 2027. And a large part of the policy has already been enforceable at audit since October 1, 2024.
That second sentence is the one that catches departments out. Most coverage of the 2027 date implies that the CJIS multi-factor authentication requirement arrives in 2027. It does not. The policy calls it advanced authentication, and it has been sanctionable at audit since October 1, 2024, per the requirement language carried in CJIS Security Policy v5.9.2. If your agency is not doing it today, you are already exposed, and waiting for 2027 makes it worse.
Here is the rest of the timeline in plain terms. FBI CJIS Security Policy version 6.1 is dated June 25, 2026 and was approved by the CJIS Advisory Policy Board. The 6.x versions reorganized the whole policy around the NIST SP 800-53 Rev. 5 control families, so policy areas 2 through 19 now map to the 18 NIST families. The modernized Priority 2 through Priority 4 requirements are in a zero cycle right now, meaning they get reviewed and educated on but not sanctioned, and that cycle closes September 30, 2027, which is why agencies are being advised to be ready by October 1, 2027. Trade coverage agrees on the approach: Federal News Network argued in September 2026 that the work starts now rather than getting compressed into 2027.
None of that requires you to become a compliance expert. It requires you to know where your evidence lives and who is accountable for it. That is a vendor conversation, so here are the four questions.
The four CJIS compliance questions to ask an evidence vendor
Send all four in one email. Ask for the answers in writing. File what comes back.
Question 1. Will you sign the CJIS Security Addendum with our state CJIS Systems Agency, and can we have a copy?
Yes is the only acceptable answer, and the signed copy should already exist. If the vendor has to go find out, that is your answer.
The CJIS Security Addendum is the document that pulls a private company inside your compliance boundary. Private contractors that store, process, or transmit criminal justice information (CJI) sign it, and the agreement sits between the agency, the vendor, and your state CJIS Systems Agency. It is one of the clearest artifacts an auditor can review, and your agency should keep the signed copy on file.
Watch for one specific bad answer. If a vendor responds with "we are CJIS certified," they have told you something important by accident. There is no such certification. The FBI does not certify software products. The Colorado Bureau of Investigation says it plainly on its CJIS access vendors page. Asked whether an enrolled company can tell customers it is CJIS certified, the answer is no, and enrollment "does not automatically indicate compliance." Compliance comes from agreements and gets verified by audit. CJIS compliance is an ongoing operating responsibility, not a one-time product certification. A CJIS compliant vendor should be able to show you the signed addendum and supporting records. A vendor who leans on a certification that does not exist is either confused about the policy or counting on you being confused.
Question 2. Who at your company can access our evidence, and are they screened?
Only personnel who have passed a fingerprint based background check and completed security awareness training. The vendor should be able to hand you that list without a meeting.
The rule covers more people than departments expect. Vendor employees with physical or logical access to criminal justice information, and the ones configuring systems that have direct access to it, all require a fingerprint based background check, per the Colorado Bureau of Investigation's CJIS vendor FAQ. Ask for the background check records and the training completion records as artifacts, not as assurances.
Remember who is on the hook. The auditor talks to you, not to your vendor. During a CJIS compliance audit, State CJIS Systems Agencies review access logs, role based access control, system access, background check documentation, and signed vendor addendums. Massachusetts, for example, runs triennial on site audits under its CJIS vendor policy guidelines. If the vendor cannot produce the paperwork, the finding lands on your agency.
LensLock answers this question with documented controls. Evidence is hosted in Microsoft Azure Government Cloud. Storage is FBI CJIS compliant, managed exclusively by screened United States citizens, and encrypted in transit and at rest.
Question 3. Where does our evidence physically live, and how is it protected?
You should be able to name the cloud environment and the encryption posture without calling anyone. If you cannot, that is the gap to close first.
When you review CJIS requirements for cloud evidence storage, the cloud name is only the starting point. A government cloud service does not make a system compliant by itself. Auditors also examine application-layer security controls, including role based access control, multi factor authentication, incident response, addendums, and training records. The cloud is the floor, not the finish line. A vendor that names a cloud and stops there has answered only half the question.
A credible vendor compliance answer has two parts: where the evidence is hosted and which controls protect it. That distinction matters when evaluating CJIS compliant evidence storage. LensLock stores evidence on Microsoft Azure Government Cloud infrastructure, and you can see how LensLock handles digital evidence management for the agency facing side of that, including chain of custody and sharing. If you want the longer explainer before you write to your current vendor, our digital evidence management guide covers retention, custody, and procurement in one place.
Question 4. How do you handle identity and multi factor authentication, and what is your plan for the rest of the modernized controls?
The vendor should be able to describe multi factor authentication at AAL2 or greater, and name what they are doing between now and October 2027 on the rest of it.
AAL2 is not vendor jargon. The requirement traces to the identification and authentication controls in the CJIS Security Policy, read against the NIST digital identity guidelines. NIST IR 8523, published in September 2025, covers what it takes to reach AAL2 and hands you the questions to ask in Appendix C, titled "Questions to Ask Your Technology Vendors." So if asking feels aggressive, it is not. The federal government wrote the questions down for you.
This question also covers ground procurement has never had to ask about. The modernized policy brought supply chain requirements with it: a documented supply chain risk management plan reviewed annually, vendor vetting before onboarding, and written breach notification agreements covering incidents that affect government systems. Most of those controls are Priority 2 and Priority 3, which puts them inside the zero cycle that closes September 30, 2027. Ask whether a breach at your vendor triggers a notice to you, in writing, within a defined window. Ask who signs that commitment.

One more question worth asking while you have them on the phone
Ask what happens to your evidence if you leave. The answer tells you whether you are on an open platform or a closed platform.
It is not a CJIS question, and it belongs in the same email anyway. A vendor who can describe a clean export in operational detail has thought about the day you leave. A vendor who gets vague about it has thought about it too, just differently.
What to do with the answers to the CJIS compliance questions to ask an evidence vendor
File them. That is the whole step, and it is the one departments skip.
Most municipal police departments do not have dedicated IT staff, and the agencies that struggle at audit are usually not the ones missing controls. They are the ones where the controls exist and nothing was written down. Documentation gaps can create audit findings even when the underlying controls exist.
So keep four things in one folder your successor can find:
The signed CJIS Security Addendum for every vendor that touches criminal justice information.
Background check and security awareness training records for vendor personnel with access.
Your encryption and audit log configuration, written down, with the date it was last reviewed.
The vendor's written answer to Question 4, including its plan through October 2027.
Together, those records form the core CJIS audit vendor documentation your agency should be able to produce. It costs you one email and an afternoon.
Frequently Asked Questions
What is the October 2027 CJIS deadline?
The modernized CJIS Security Policy controls that have been in a review and educate zero cycle stop being unsanctioned. The zero cycle ends September 30, 2027, which is why agencies are being advised to be ready by October 1, 2027.
Does the 2027 deadline mean we have to add multi factor authentication by then?
No. Multi factor authentication, which the policy calls advanced authentication, has been sanctionable at audit since October 1, 2024. An agency that is not doing it today is already exposed, regardless of what happens in 2027.
Does my body camera and evidence vendor have to be CJIS compliant?
Any vendor whose systems store, process, or transmit criminal justice information falls inside your agency's compliance boundary. The vendor signs the CJIS Security Addendum with your agency and your state CJIS Systems Agency.
Is there such a thing as CJIS certified software?
No. The FBI does not certify products. Compliance is established through agreements among the agency, the state CJIS Systems Agency, and the vendor, and it is verified by audit. Treat "CJIS certified" as a warning sign, not a credential.
Who is allowed to access our evidence at the vendor?
Only personnel who have passed a fingerprint based background check and completed security awareness training. A credible vendor can produce that list, along with the records behind it.
What documents should we have on file for our evidence vendor before an audit?
A signed CJIS Security Addendum, background check records for vendor personnel with access, security awareness training completion records, and your encryption and audit log configuration.
What should a department with no IT staff do first?
Send these four questions to your current vendor and file the answers. Documentation, not technology, is what agencies usually fail on, and the paperwork is the part you can finish this month.
Four questions. One email. If your vendor answers them with documents, you are in good shape. If your vendor answers them with a sales call, you learned something.
Want to see how we answer them? Call us. We answer. 866-536-7562, Press 2 to reach our Sales team. Press 3 to reach our Client Services team. Or start with the body camera and evidence platform.
LensLock has been building body cameras, in-car video, and evidence management for law enforcement agencies since 2015. Evidence is stored on Microsoft Azure Government Cloud, FBI CJIS compliant, managed exclusively by screened United States citizens, with encryption in transit and at rest.




Comments