Casebook PBC

What SOC 2 Means When Choosing Case Management Software

Your caseworkers are recording clients’ health histories and home addresses in case management software, so a breach at the vendor could expose your clients to identity theft or reveal where a domestic…

Casebook PBC

October 9, 2026 7 min read

Your caseworkers are recording clients’ health histories and home addresses in case management software, so a breach at the vendor could expose your clients to identity theft or reveal where a domestic survivor lives. Your IT team can check how well a vendor protects that data by reviewing its Systems and Organization Controls (SOC) 2 report. This guide explains how case management SOC 2 reports work and how to use them when comparing platforms.

What Is SOC 2 Compliant Software?

A vendor with SOC 2 compliant software has hired a licensed Certified Public Accountant (CPA) firm to complete a SOC 2 examination of the controls that protect customer data. That CPA firm then issues an attestation report that states its opinion on those controls. No organization issues SOC 2 certificates or badges, so the CPA firm’s report is the document a vendor can show buyers. 

Your organization isn’t legally required to follow SOC 2. The American Institute of Certified Public Accountants (AICPA) created this voluntary framework for organizations that want to take extra steps to protect client data. Some government agencies still require it from vendors that respond to their requests for proposals (RFPs). For example, Illinois requires cloud vendors on state contracts to submit a security audit report and strongly prefers a SOC 2 Type II.

CPA firms audit the company that stores and processes data for its customers, which in this case is your case management vendor. Your agency’s responsibility is to request the vendor’s report and review it.

Agencies that request proof of SOC case management compliance from vendors may also see SOC 1 and SOC 3 reports. A SOC 1 covers controls that affect a customer’s financial reporting, while a SOC 3 covers the same areas as a SOC 2 in a shorter public report that vendors can post online.

SOC 2 Type I vs. Type II

A SOC 2 Type I audit evaluates how a vendor designed its data security controls, while a SOC 2 Type II audit tests if those controls worked over three to 12 months. Those controls include the rules a vendor sets on who can open a client record and the encryption it uses on stored files.

What Does a SOC 2 Audit Evaluate?

Auditors test a vendor’s data security controls against the AICPA’s five Trust Services Criteria during a SOC 2 audit. Security is mandatory, but the vendor picks which of the other four to include, so you should check which criteria its report covers.

The CPA firm reviews these areas under each criterion:

  • Security: The vendor must show how it blocks unauthorized access and manages threats through its risk mitigation strategies.
  • Availability: Your staff relies on the vendor to keep its software online when they need to open client records.
  • Processing integrity: The vendor should process data accurately so the service hours a caseworker logs match your funder reports.
  • Confidentiality: Only approved users should see confidential information, such as contracts with partner agencies.
  • Privacy: The vendor should collect and use personal information only as its privacy notice describes.

Why SOC 2 Compliance Matters in Choosing Case Management Software

A CPA firm tests your vendor’s security controls on your agency’s behalf during a SOC 2 audit, so your IT team can rely on an independent review of safeguards it couldn’t inspect directly. Executive directors can also point to that report when board members of funders ask how the agency protects client data.

You can use a SOC 2 report to check a vendor’s Health Insurance Portability and Accountability Act (HIPAA) safeguards because the U.S. Department of Health and Human Services does not offer HIPAA certification for vendors. Agencies covered by HIPAA must also sign a business associate agreement (BAA) with any vendor that stores their clients’ health information. When signing the agreement, the vendor commits in writing to protect the client’s information, so your agency can hold it legally responsible for the safeguards in its SOC 2 report.

Co-responder programs that handle criminal justice information follow the FBI’s Criminal Justice Information Services (CJIS) Security Policy, which also has no vendor certification. You can use a vendor’s SOC 2 report as independent evidence of its security controls and confirm the vendor signed the CJIS Security Addendum, where it commits in writing to following the policy. 

How to Evaluate a Vendor’s SOC 2 Report

You should request a vendor’s most recent SOC 2 Type II report and review it before you sign a contract. Vendors might share it through a secure portal or under a nondisclosure agreement (NDA) because the report includes details on their security systems.

Check the Report’s Scope and Audit Period

You should confirm the CPA firm examined the platform your agency plans to buy and check the report for excluded services, such as an outsourced data center. The review period should end within the past year so the auditor’s tests are representative of current controls. 

Auditors will also list tasks your agency must handle for the vendor’s controls to protect your data, like removing system access when staff leaves. You should assign each task to someone on your team because a former employee could still log in and view client records if no one at your agency removes the account.

Review the Findings and Ask Follow-Up Questions

The CPA firm will state its opinion of the vendor’s controls and list any exceptions, which are cases where a control failed during testing. A vendor whose SOC 2 audit keeps failing would receive a qualified or adverse opinion year after year, while a vendor with working controls would receive a clean opinion. You should ask the vendor how it fixed each exception and bring in your IT staff to interpret technical findings.

SOC 2 Vendor-Review Checklist for Case Management Software

Your procurement team and IT staff can use this checklist to compare vendors on the same SOC 2 points. They can review these five areas for each vendor on their shortlist:

  • Report type: The vendor should provide a Type II report so you can see how its controls performed over months of daily work.
  • Audit period: The most recent review period should have ended within the past year so the auditor’s findings still apply to the current system.
  • Report access: Your team should read the full report under NDA because vendors might leave the exceptions out of the public SOC 3 version.
  • Audit scope: Vendors that sell more than one product might have a SOC 2 report for only one of them, so you should confirm the CPA firm examined the case management platform your agency plans to buy.
  • Audit findings: The vendor should explain how it fixed each exception so you can judge the risk of the same failure happening again.

Casebook PBC is SOC 2 Compliant Software for Human Services

Casebook PBC is a case management platform where human services agencies keep sensitive client records secure as they add programs and staff. An independent CPA firm audits Casebook’s security controls each year in a SOC 2 Type II examination, so your executive director can give board members and funders an objective report when they ask how client data stays safe.

Admins at agencies with several programs can set permissions down to the individual record so staff see only the clients they serve. Casebook also signs BAAs on Team and Enterprise plans and the CJIS Security Addendum for agencies that handle criminal justice information. You can explore Casebook’s case management solution to see how these protections fit your programs.

Make Security Part of Your Case Management Software Decision

Your team should bring specific questions from each vendor’s SOC 2 report to the next sales call, such as why a service fell outside the audit’s scope. You’d then know if any part of the system that stores your client data wasn’t covered by the vendor’s last SOC 2 audit. You should also check each platform against your agency’s other requirements, like HIPAA, before you choose one.

Our team can walk your IT staff through our latest SOC 2 report and any exceptions in it. Book a demo to review a Casebook SOC 2 Type II report with us before you sign a contract.

See it on your caseload

Turn casework into proof funders trust.

A short, tailored walkthrough of Casebook on your programs — intake, notes, and the reporting that comes out the other side.