March 8, 2023

SOC 2 Type II compliance

Author
Jason Brovitch
Meet the Team
SOC 2 Type II compliance

Public safety sales decks are full of compliance acronyms like CJIS, FIPS, SOC 2, HIPAA, and ISO 27001, and after a while they all start to blur together. When you're evaluating a digital evidence management system (DEMS), it's easy for IT directors and records supervisors to see these labels as interchangeable. But SOC 2 Type II isn't just another badge. It has real, specific implications for case integrity, even though it's often waved off as marketing fluff.

iCrimeFighter went through an independent SOC 2 Type II audit in September 2022, conducted by Prescient Assurance, a CPA firm that specializes in SaaS security attestations. For law enforcement agencies and prosecutors, knowing what this audit actually checks, and how it's different from a vendor just claiming to be "secure," is a basic part of doing your homework before signing on with a vendor.

What Does SOC 2 Actually Check?

SOC 2 was developed by the American Institute of Certified Public Accountants (AICPA) under the SSAE 18 auditing standard, and it's built specifically to evaluate cloud-based service providers. Rather than running through a generic checklist, auditors measure a company's internal controls against five criteria: security, availability, processing integrity, confidentiality, and privacy.

The scope of the audit shifts depending on what the platform actually does. For a digital evidence platform holding investigative files, juvenile records, sealed warrants, and sensitive victim information, security and confidentiality are the two criteria that matter most.

Type I vs. Type II: What's the Real Difference?

The difference between Type I and Type II boils down to one thing: proof over time.

A Type I report is a snapshot. It checks whether a vendor's security controls were properly designed on the day the auditor looked at them.

A Type II audit is different; it watches the vendor operate for six to twelve months and checks whether employees actually followed those security policies day in and day out, not just on paper. Type I tells you a vendor built a good plan. Type II tells you they actually stuck to it. When a Type II report comes back with an unqualified opinion, that means the auditor didn't find any material problems; it's the strongest level of assurance an independent audit can give.

Why This Matters More for Law Enforcement Than for Most Software Buyers

Most companies ask for a SOC 2 report to protect their corporate data and check a box during procurement. In criminal justice, the stakes are a lot higher. A security gap, a modification that never got logged, or an access attempt that wasn't recorded can put the chain of custody itself in question.

If access logs are incomplete or evidence goes missing during an outage, defense attorneys have an opening to challenge whether a file is authentic, or to argue discovery violations, during suppression hearings. Choosing a DEMS vendor with a verified SOC 2 Type II report is one way to make sure evidence stays protected from the moment it's collected all the way through trial.

How SOC 2 Fits in With Everything Else Agencies Ask About

SOC 2 Type II isn't a replacement for other compliance requirements; it works alongside them. A public safety vendor needs to cover several layers at once:

  • CJIS Security Policy: Federal rules for accessing, handling, and storing Criminal Justice Information (CJI)
  • FIPS Validation: Standards for the cryptographic modules that encrypt data at rest and in transit
  • HIPAA: Governs protected health information, which shows up often in medical examiner reports and assault case files
  • AWS GovCloud Infrastructure: Physical and network infrastructure built to meet federal compliance standards

SOC 2 Type II looks at a vendor's internal business and operational practices, while frameworks like CJIS and FIPS cover the technical side. Agencies should expect a vendor to check all of these boxes, not just one.

What Agencies Should Actually Ask For

A compliance logo on a website doesn't prove anything on its own. During procurement, your evaluation team should ask the vendor directly for their actual SOC 2 Type II audit report, typically under an NDA.

When you get it, check three things: the exact dates the audit covered, whether the auditor gave an unqualified opinion, and whether security and confidentiality were actually part of the scope. A vendor that's confident in their security posture won't hesitate to hand this over.

FAQs

What's the difference between SOC 2 Type I and Type II?

Type I confirms security controls were properly designed at one point in time. Type II confirms those controls were actually followed and worked over an extended period, usually several months, which makes it a much more rigorous check.

Who audits a company for SOC 2 compliance?

An independent, licensed CPA firm handles the audit. iCrimeFighter's was done by Prescient Assurance, a firm that focuses specifically on security and compliance attestation for B2B SaaS companies.

Does SOC 2 Type II replace the need for CJIS compliance in law enforcement software?

No. SOC 2 looks at a company's operational security controls broadly, while CJIS Security Policy covers requirements specific to handling criminal justice information. Agencies should expect both — one doesn't stand in for the other.

How often does a company need to renew its SOC 2 Type II certification?

SOC 2 Type II reports cover a set audit period and get renewed regularly, usually every year, since the certification reflects performance over time rather than something a vendor earns once and keeps forever.

Why does SOC 2 Type II matter more for evidence management software than for typical business software?

Because a failure in access control, data integrity, or availability on an evidence platform can directly affect a criminal case, raising chain-of-custody questions or causing discovery delays, rather than just being an internal headache for the business.

Can an agency request a copy of a vendor's SOC 2 report during procurement?

Yes, and it's a completely normal request. SOC 2 reports are usually shared under an NDA rather than published publicly, so agencies should expect to sign one to review the full report during evaluation.

Built for Public Safety

Every piece of digital evidence. One place.

BWCs, mobile extractions, photos, and more. One secure platform with a complete audit trail.

Free Trial

See it on your own cases.