Updated 15 November 2026 · about 7 minutes
The SIG — Standardized Information Gathering questionnaire — is published by Shared Assessments and used by many larger companies to assess their vendors. SIG Lite is the shorter version, often sent to lower-risk vendors or as a first pass. If one lands in your inbox, here's how to scope it, answer it and avoid the usual mistakes.
This guide contains no SIG question text. The SIG is licensed by Shared Assessments; the customer who sent it to you has a license to use it with vendors.
What SIG Lite is (and isn't)
- A risk-tiering tool. Your customer uses your answers to decide how risky you are and whether you need a deeper review (often the fuller SIG Core, an interview or evidence requests).
- Organized by risk domains. Expect areas such as risk management and governance, security policy, organizational and HR security, asset and information management, access control, application security, operations and network security, incident management, business resilience, privacy, third-party management and physical security. The exact domains and question count depend on the SIG version your customer uses.
- Mostly Yes / No / N/A with a comments column. The comments are where you win or lose.
- Not a certification. Completing a SIG doesn't make you compliant with anything; it describes your controls.
Step 1: Scope before you answer
The SIG is written to cover every kind of vendor, so many questions won't apply to you. Settle scope with the customer first:
- Which services are in scope? Answer for the product they're buying, not your whole company.
- What data will you handle? If you won't process their personal data, many privacy questions become N/A — but say why in the comments.
- Is the scoping section filled in? Some SIG workbooks have a scoping tab that switches whole sections on or off. Ask the customer to set it, or set it with them.
N/A is a legitimate answer. Unexplained N/As are not: always add a one-line reason (“N/A — we don't operate our own data centres; hosting is provided by our cloud provider”).
Step 2: Answer in the comments, not just the Yes/No column
Reviewers read the comments to decide whether a “Yes” is real. For each answer, add:
- The specific control (“quarterly access reviews of production and customer data access”).
- The scope if it's narrower than the question implies.
- Where evidence lives (“policy available under NDA”, “see SOC 2 report section 4”).
Keep comments to one to three sentences. If the honest answer is “partly”, choose No (or the closest option) and explain the partial control — don't tick Yes and hope.
Step 3: Watch the classic traps
- Policy vs. practice. Many questions ask whether a documented, approved and reviewed policy exists — not whether you do the thing. If you do it but haven't written it down, say so and write it down.
- Inherited controls. Physical security, hardware disposal and environmental controls usually belong to your cloud provider. Answer “Yes — inherited from [provider]” and point to their report.
- Subcontractors. Questions about fourth parties (your vendors) are increasingly common. Keep a current subprocessor list.
- Frequency words. “Annually”, “at least annually”, “periodically” — answer with your real frequency and the date of the last occurrence.
- Over-answering. Don't volunteer architecture details, internal hostnames or vulnerability specifics in a spreadsheet that will be emailed around.
Step 4: Reuse your answers next time
SIG questions overlap heavily with CAIQ questions and with custom vendor assessments. The wording differs; the answers don't. Write each answer once, approve it, and attach the different phrasings to it. Next time — SIG, CAIQ or a customer's own spreadsheet — you match instead of rewriting. Our free 60-question starter set covers most of the same ground in original wording.
Step 5: Return it cleanly
SIG workbooks have many sheets, drop-downs, formulas and protected ranges. Edit only your answer cells and send back the customer's file. Don't rename sheets, insert columns or paste formats — the customer's tooling may read the file automatically.
What reviewers look for
- Answers that are consistent with each other and with your public materials.
- Evidence offered without being asked (a SOC 2 report, pen test summary, policies under NDA).
- Honest gaps with compensating controls and dates.
- A named security contact who replies to follow-ups quickly.
Doing it in RFPKit
Upload the customer's SIG workbook as a project, map the question and answer columns on each sheet, and RFPKit matches every question to your approved library. Use matches, ask for AI drafts written only from approved answers, assign the rest to experts, and export back into the same workbook — only the answer cells change.