# What is the HECVAT? A guide for campus security reviewers and the vendors they assess

> Source: https://www.usehabeo.com/blog/what-is-hecvat
> Published: 2026-11-20
> Updated: 2026-11-20
> Tags: compliance, hecvat, security, procurement

*The HECVAT is how higher education asks a vendor about security, privacy and accessibility in one standard workbook. Here's what's in HECVAT 4 and how both sides should use it.*

If you sell software to a college or university, someone in information security will eventually send you a spreadsheet. If you work in that security office, you've probably sent hundreds of them. The spreadsheet is almost always the HECVAT, and both sides get more out of it when they understand what it's for.

## What is the HECVAT?

The HECVAT — the **Higher Education Community Vendor Assessment Toolkit** — is a standardized security and privacy questionnaire that colleges and universities use to assess third-party vendors, particularly cloud and SaaS providers that will store or process institutional data. It's maintained by EDUCAUSE with the higher-education security community, and it's free for both institutions and vendors to use.

The point of a shared questionnaire is reuse. Instead of every campus writing its own 200-question security review, a vendor completes the HECVAT once and shares it with every institution that asks. The institution gets consistent answers it can compare across vendors; the vendor stops rewriting the same answers in fifty formats.

## What changed in HECVAT 4?

HECVAT 4, released in early 2025, consolidated what used to be separate documents. Earlier versions came as a **Lite** questionnaire for lower-risk reviews, a **Full** questionnaire for products handling sensitive data, and an **On-Premise** variant for installed software, plus a short triage form. In HECVAT 4 they're all one workbook.

Instead of choosing a version, the vendor answers a set of scoping questions at the start, and the workbook directs them to the sections that apply to their product. The sections cover the organization, the product, infrastructure, IT accessibility, artificial intelligence, privacy, and case-specific topics such as payment card handling or health data.

The practical effect: "Can you send us your HECVAT Lite?" now usually means "send us the HECVAT 4 workbook," and institutions that built intake processes around Lite-versus-Full routing have had to update them.

## Who fills out the HECVAT, and who reviews it?

The **vendor** completes it, usually a security or compliance lead with input from engineering, legal and product. A good response takes a few days the first time and an hour or two to refresh.

The **institution's information security or IT risk office** reviews it, typically as part of procurement or contract renewal. Depending on the data involved, privacy, accessibility, research compliance, or the registrar (for FERPA-covered student records) may weigh in on their sections.

## How do universities use HECVAT responses?

Most campuses use the HECVAT as the evidence layer of a risk-tiered review:

1. **Classify the data the product will touch.** Public, internal, confidential, regulated. This sets how deep the review goes.

2. **Request the HECVAT,** plus supporting evidence for higher tiers: a SOC 2 report, a penetration-test summary, an accessibility conformance report (VPAT/ACR), insurance certificates.

3. **Score and follow up.** Reviewers look for "No" answers on controls the data classification requires, and for "Yes" answers that need evidence.

4. **Record findings and compensating controls** in the contract or a risk acceptance, with a review date.

The questionnaire doesn't decide anything by itself. It makes the conversation specific.

## HECVAT vs. SOC 2: do you need both?

They answer different questions. A **SOC 2** report is an independent auditor's opinion on whether a service organization's controls are designed (Type 1) or designed and operating effectively over a period (Type 2). The **HECVAT** is the vendor's own description of its security, privacy and accessibility practices, in higher education's vocabulary — including topics SOC 2 doesn't touch, like FERPA, accessibility and campus identity federation.

For high-risk data, reviewers usually want both: the HECVAT for breadth and context, the SOC 2 for independent assurance. For lower-risk tools, a well-answered HECVAT is often enough.

## How should a vendor complete the HECVAT?

- **Answer the question asked.** "Yes" means you do it today. Roadmap items belong in the notes column with a date, not in the answer column.

- **Explain every "No" and every "N/A."** A bare "No" reads as a gap; "No — we don't store payment card data, so PCI scope doesn't apply" reads as a scoped answer.

- **Keep one canonical copy** and date it. Reviewers notice when two institutions received different answers to the same question.

- **Publish it.** A HECVAT on your trust page shortens every security review, because the reviewer can start before the sales call.

- **Refresh it when something real changes:** a new subprocessor, a new hosting region, an audit completed, a feature that touches new data.

## How should a security reviewer read one?

- **Start with the data.** Map the vendor's answers to the classification of the data you'll actually send, and skip sections that don't apply.

- **Check the date and version.** An old response may predate a breach, an acquisition or a re-architecture.

- **Look for the evidence trail.** Claims about encryption, access control, logging and incident response should match the SOC 2 report or other evidence, where provided.

- **Ask about subprocessors.** The HECVAT covers the vendor; your data may also flow to its hosting, email and analytics providers.

- **Write down what you accepted.** A risk acceptance with a review date beats a silent approval nobody revisits.

## Where to find HECVAT examples

Many vendors now publish their completed HECVAT. Habeo's is public on our [compliance page](/compliance/hecvat): the full HECVAT 4 workbook, plus a short narrative summary of the questions reviewers ask most. It's also an honest example of answering with a roadmap — our SOC 2 Type 1 audit is in progress, and the response says so rather than implying a report we don't have yet.

The template itself comes from EDUCAUSE; download the current version there, since revisions are released periodically.

Related reading: the [HECVAT glossary entry](/glossary/hecvat) and [SOC 2 Type II](/glossary/soc-2-type-ii).
