in this guide
  1. the three questionnaires you will meet
  2. what the access rows ask
  3. “we have a policy” and “we can show it”
  4. answering the company rows from evidence
  5. keep one dated answer set

Picture a 90-person software company about to close its largest deal. The customer’s procurement team sends a spreadsheet with a few hundred rows and a deadline. Somewhere in the middle is a block about access: single sign-on, MFA, admin accounts, leavers, access reviews, who on your side can see the customer’s data. Each row has a yes, a no and a comments cell. The sales lead forwards it to whoever looks after IT.

Every row in that block can be answered in a minute. A yes typed in a minute is a claim that a document exists and that a record shows it is followed. The customer may never ask to see either. Some will.

This guide is about answering that block from evidence when your company is the vendor. It runs in the opposite direction from the SOC 2 guide, which is about reading a vendor’s report as a buyer. It is not legal advice. Whether your answers become part of a contract depends on the contract, and that is a question for a lawyer before you sign one that refers to them.

the three questionnaires you will meet

A customer may send its own spreadsheet. Others send one of three published questionnaires, or a version adapted from one, and knowing which one arrived tells you what kind of answer it expects.

SIG, from Shared Assessments. A licensed product: Shared Assessments says the SIG is not free to download and comes with a subscription or membership, so its questions are not reproduced here. Its product page lists 21 risk domains, with Access Control first, and says the content is updated every year. It comes in a short Lite scope for lower-risk suppliers and a longer Core scope for higher-risk ones. Shared Assessments described the 2023 SIG Lite as 126 risk control questions. Its own page says a vendor can complete the SIG in advance to answer requests as they arrive, and that the customer gathers the vendor’s policies and procedures to look for discrepancies.

CAIQ, from the Cloud Security Alliance. A free download that sits on top of the Cloud Controls Matrix. The CSA’s page for version 4.1, released on 27 January 2026, describes the matrix as 207 controls across 17 domains and the CAIQ as a set of yes or no questions about them. A provider can file a completed CAIQ in the CSA’s STAR Registry. The CSA describes that Level 1 listing as a free self-assessment, publicly visible, valid for one year, with third-party certification reserved for Level 2.

HECVAT, from EDUCAUSE. The questionnaire colleges and universities send. EDUCAUSE lists version 4.1.6 as current, lets vendors use it at no cost for their higher-education business, and folded the old Full, Lite and on-premises editions into one workbook. Questions marked with an asterisk carry the most weight in the score. EDUCAUSE asks vendors to update their copy at least once a year.

All three are built to be filled in once and sent many times. That is the useful part: one honest answer set, kept current, beats a fresh guess for every deal.

what the access rows ask

Read the access block of any of them and two kinds of question sit side by side, often with similar wording.

two kinds of access row in one block

about your product

what the customer's users get

  • Can our users sign in with our SSO?
  • If not, does your login offer MFA?
  • Does a session lock after inactivity?
  • Do you log admin and security events, and for how long?

about your company

how your own people get in

  • Is there an onboarding and offboarding process, and is it followed?
  • Who reviews the list of privileged accounts?
  • Do your cloud administrators use MFA?
  • Which of your staff can reach our data, and how do they get admin access to our instance?

The HECVAT 4 question list that EDUCAUSE publishes alongside the toolkit shows both halves clearly. On the product side it asks whether your solution supports SSO for users and administrators, whether it supports MFA if SSO is not offered, whether sessions time out, and how user and administrator security events are logged and kept. On the company side it asks whether your staff’s access follows structured rules such as role-based access, whether a written procedure covers how employees obtain administrator access to the customer’s instance, whether you require MFA for the administrators of your cloud environment, whether your staff or third parties can reach the customer’s data at all, and, in its health-data section, whether accounts used for your own remote support follow the same login and logging rules as everyone else.

The CSA’s identity and access controls cover the company half in more depth. Its 30 May 2025 article on implementing them lists 16: a written access policy reviewed at least once a year, an inventory of identities, least privilege and separation of duties, a recorded process for granting access, timely removal when people move or leave, periodic access reviews, separate and time-limited privileged roles, one identifiable person behind every account, and MFA at least for privileged users and sensitive data.

The product rows are mostly about features, and your product team can answer them from the product. The company rows are about your own admin consoles, and that is where an answer typed from memory can go wrong. Rows about staff access to customer data deserve a slow read: the support access guide covers what a good answer to them looks like.

“we have a policy” and “we can show it”

Two HECVAT 4 questions about your company carry the same small phrase. The offboarding question asks for a policy that is “documented, and currently implemented” (EDUCAUSE, HECVAT 4 question list), and the privileged-account question asks for a review procedure that is documented and currently followed. A yes to either is two claims. A document exists. Something shows the document is what happens.

what one yes rests on

  1. 1the rowLeavers lose access promptly.
  2. 2the policyA page that says who disables what, and when.
  3. 3the gapThe policy exists. Nobody has checked a leaver against it.
  4. 4the recordA dated list: leaving date, account disabled date, who did it.

The same split runs through MFA, and the admin consoles draw it for you.

Google Workspace keeps two columns. Google’s documentation for the security user report lists one column for whether a user is enrolled in 2-Step Verification and another for whether the user is required to be. The report downloads as a CSV.

Microsoft counts capability. Microsoft’s documentation for the authentication methods activity report defines “MFA capable” as registered for a strong method and enabled by policy to use it. Whether MFA was required at sign-in shows in a separate usage view that splits sign-ins into single-factor and multifactor. Both views need an Entra ID P1 or P2 licence, and disabled users do not appear in the registration list.

Support and enforcement are separate facts in a product too. In its June 2024 report on the intrusions into Snowflake customer accounts, Mandiant found the affected accounts were not configured with MFA, and it found no evidence that Snowflake’s own environment had been breached. The Snowflake case is what “the product supports MFA” looks like when nobody turned it on. If a row asks whether your product supports MFA, say so. If it asks whether your staff use it, answer from the enforcement column.

answering the company rows from evidence

Take each company row, open the setting or the record behind it, and write the answer the record supports.

MFA for staff and admins. Export the enforcement view from your directory and list everyone it does not cover, with the reason. Emergency accounts are a legitimate exception, and the break-glass guide explains why they exist. A listed exception with a reason reads better than an “all” that a reviewer can disprove.

Leavers. Take your last five leavers and record, for each, the leaving date and the date the main account was disabled. If the dates are not recorded anywhere, the honest answer describes the process you follow and says it is not yet logged.

Access reviews. A row asking how often privileged access is reviewed wants a frequency. The CSA’s control says the frequency should match your tolerance for risk, so once a year can be a defensible answer if there is a dated record of last year’s review. Without one, the answer is that reviews are not yet recorded.

Who grants access. Some rows ask whether access is approved before it is given. If approvals happen in chat messages, the access requests guide covers how to leave a trail that answers this row next year.

Logs. Rows about logging ask how long you keep records and whether the customer can see them. Check the retention setting before you answer: the logs guide explains where that number comes from and how far back it reaches.

Partial answers go in the comments cell. EDUCAUSE tells institutions to compare each answer with the expected response and then read the vendor’s additional information column for context, and its reviewers can send the file back with questions. A no with a sentence explaining what you do instead gives the reviewer something to weigh. A yes that fails a follow-up question is harder to take back.

Some details stay out. EDUCAUSE’s FAQ for vendors says a completed HECVAT should not contain information that would weaken your security if disclosed, and recommends redacting it. Count your admin accounts for your own folder. The questionnaire can say that the list exists and when it was last reviewed.

keep one dated answer set

The questionnaire publishers expect reuse. Shared Assessments says a vendor can fill in a SIG response ahead of requests, a CAIQ filed with the CSA is valid for a year, and EDUCAUSE asks for a HECVAT update at least once a year. A customer can also accept other evidence: EDUCAUSE says most colleges and universities accept a recent SOC 2 Type 2 report, and many consider a CAIQ. If you send a report instead, the SOC 2 guide is what a careful customer will read it against.

That points to one folder, owned by one named person: the latest answers, the policy each yes points to, and the dated export or screenshot behind each company row. When a new questionnaire arrives, its access block gets mapped to answers that already have evidence behind them, and only the rows that are new get a new look.

If the customer from that spreadsheet asked tomorrow for the record behind your answer on leavers, who at your company would know where to find it?

sources

  1. Shared Assessments: SIG, third party risk management standard (product page)
  2. Shared Assessments: what is the SIG?
  3. Shared Assessments: SIG FAQ
  4. Cloud Security Alliance: Cloud Controls Matrix and CAIQ v4.1 (released 27 January 2026)
  5. Cloud Security Alliance: Implementing CCM, identity and access management controls (30 May 2025)
  6. Cloud Security Alliance: CSA STAR certifications, what are they? (3 November 2023)
  7. EDUCAUSE: Higher Education Community Vendor Assessment Toolkit (HECVAT)
  8. EDUCAUSE: HECVAT FAQs for corporations
  9. EDUCAUSE: how to use the HECVAT
  10. EDUCAUSE: HECVAT 4 issue tracker and 3 to 4 migration guide
  11. Microsoft Learn: authentication methods activity
  12. Google Workspace Admin Help: user reports, security
  13. Google Cloud / Mandiant: UNC5537 targets Snowflake customer instances for data theft and extortion (10 June 2024)