SIG Questionnaire: SIG Lite vs SIG Core | Safe Security

What Is the SIG Questionnaire? SIG Lite vs SIG Core, and When to Use Each

Nov 12, 2026 11 minute read


Should you send this vendor a SIG, or is that the wrong tool?

Here is the scenario most TPRM teams know too well. Procurement needs a new payroll processor approved by Friday. Someone on your team sends the full SIG because that is “what we send.” Three weeks later the vendor returns a workbook with hundreds of answers, half of them “Yes” with no evidence attached, and the contract has already been signed on a business exception.

The SIG is not the problem. It is one of the most widely used standardized vendor questionnaires in the market, and for good reason. The problem is how it gets used: sent at the wrong depth, to the wrong vendors, and treated as proof when it is really a starting claim. This guide explains what the SIG is, how SIG Lite and SIG Core differ, and how to decide when a SIG is the right instrument and when it is just paperwork.

San Francisco Health Plan Cut Costs by 89% 200+ vendors. AI-driven assessments. One unified platform.

What is the SIG questionnaire?

The SIG (Standardized Information Gathering questionnaire) is published by Shared Assessments, a member organization focused on third-party risk practice. Shared Assessments describes its third-party risk toolkit as used by more than 15,000 organizations worldwide. The SIG gives outsourcers and vendors a common set of questions across risk domains such as information security, privacy, business resilience, and supply chain, so a vendor can answer once and share the result with many customers.

A few facts matter for planning:

  • It is updated every year. Each edition is named for its year. The current edition is SIG 2026.
  • It is licensed content. Organizations get access through Shared Assessments membership or through licensed platforms. It is not a free, open download.
  • It is scoped, not one size. According to Mitratech, a SIG licensee, the 2026 release formalizes scoping presets (Lite, Core, and Detail) so teams can match depth to a vendor’s risk profile without manually editing the workbook.
  • It is following the risk. The same licensee reports that SIG 2026 adds a mapping to ISO/IEC 42001 (AI management systems), integrates the Business Resilience Council’s Operational Resilience Framework, and deepens its NIST SP 800-171 mapping. No new risk domains were added in 2026.
  • It is leaving Excel, slowly. Shared Assessments has introduced SIG EV (Evolution), a browser-based platform, while the Excel workbook format remains available.

What is the difference between SIG Lite and SIG Core?

SIG Lite is the short form. It covers the highest-priority controls across domains and is built for initial screening or for vendors whose access and data exposure are limited. SIG Core is the comprehensive form, built for vendors that store, process, or can reach sensitive or regulated data, or that support critical operations. The Detail preset added in 2026 sits between and around those, giving teams a middle setting.

Question counts change with each edition and with scoping, so check the current release rather than relying on figures quoted in older articles. The planning rule is simpler than the counts: Lite answers “is there an obvious gap?” and Core answers “show me the full control picture.”

Why do SIG-based programs stall?

Most SIG problems are operational, not content problems. Four failure modes show up again and again.

Everyone gets SIG Core

When the default is the full questionnaire, a marketing analytics tool with no data access gets the same workload as your core banking processor. Vendors push back, completion rates drop, and your analysts spend the same review hours on a low-risk vendor as on a critical one. The fix is inherent-risk tiering at intake, before a questionnaire is ever chosen. Teams that route by tier typically send Core to their top 10 to 15 percent of vendors and something lighter to everyone else.

Answers get treated as evidence

A SIG response is a self-attestation. “Yes, we enforce MFA for privileged access” is a claim until a SOC 2 report, a policy, or a configuration screenshot backs it up. Programs that score raw answers end up with a risk register full of unverified statements. Strong programs cross-check answers against audit evidence and flag where they disagree. This is where evidence-backed risk assessment separates from questionnaire collection.

The vendor sends last year’s SIG

Vendors who answer the SIG often keep a completed copy and send it to every customer. That is the point of a standard, and it saves real time. The catch: the copy may be a year old, scoped to a different preset, or answered for a different service line than the one you are buying. If nobody checks the edition, the scope, and the date, you accept answers that do not describe your engagement.

Review does not scale past a few dozen vendors

Reading a full SIG Core response line by line, then reconciling it against a SOC 2 report, can take an analyst most of a day. Multiply that across a reassessment cycle and the backlog becomes the program. Teams stop reading and start skimming, which is how real gaps get missed.

How do you decide when to use the SIG? A four-step model

Here is the decision model we recommend. It mirrors how SAFE TPRM structures assessments, but it works in any program.

Step 1: Score inherent risk before you pick a questionnaire

Capture what the vendor will touch: data types (PII, PHI, payment data, intellectual property), system access, business criticality, and whether the vendor is customer facing. Assign a tier. A simple four-tier model works for most programs:

  • Tier 1 (critical): sensitive data at volume or critical operational dependency. Full-depth assessment.
  • Tier 2 (high): sensitive data or meaningful system access. Full or detailed assessment.
  • Tier 3 (moderate): limited data, limited access. Short-form assessment plus external monitoring.
  • Tier 4 (low): no sensitive data, no access. Attestation or external monitoring only.

For a deeper treatment, see our guide to the vendor risk tiering model.

Step 2: Match the instrument to the tier

Use SIG Core (or the Detail preset) for Tier 1 and Tier 2. Use SIG Lite for Tier 3 when you want standardized coverage. For Tier 4, a questionnaire is often unnecessary. Consider other standards too: the CSA CAIQ for cloud providers, HECVAT for higher education, and the Vendor Security Alliance questionnaires for technology vendors. Our VSAQ guide covers when that option fits. If you do not hold a SIG license, our free SIG-style questionnaire alternative gives you comparable domain coverage.

Step 3: Verify, do not just collect

Request supporting evidence for the controls that matter most to the tier: a current SOC 2 Type II or ISO/IEC 27001 certificate, a recent penetration test summary, and incident response and business continuity documentation. Then cross-check. Where the SIG says “Yes” and the SOC 2 shows an exception, that discrepancy is your finding. In SAFE, document analysis supports SIG responses alongside SOC 2, ISO/IEC 27001, HECVAT, NIST CSF, and PCI DSS artifacts, and AI review compares vendor answers against attached audit evidence, sorting questions into Passed Review, Needs Attention, or Not Reviewed so analysts start with the exceptions.

Step 4: Reuse what you already validated

On reassessment, start from the prior response and the prior evidence, and ask the vendor to confirm or update. Only the changed answers need fresh review. Pair that with continuous external monitoring so you know which vendors need a full reassessment early and which can wait for the scheduled cycle.

What should you check before accepting a vendor’s existing SIG?

A completed SIG from the vendor’s trust center can save weeks, but only if it actually describes your engagement. Run five checks before you accept one:

  • Edition. Is it the current year’s SIG or one from two cycles ago? Older editions may miss AI governance and resilience content you now expect.
  • Preset and scope. Was it answered at Lite depth when your tier calls for Core?
  • Service line. Does it describe the product you are buying, or a different business unit or hosting environment?
  • Date and signatory. Is it dated within the last 12 months, and was it signed off by someone accountable for security?
  • Evidence. Are the material “Yes” answers backed by a current SOC 2 Type II, ISO/IEC 27001 certificate, or equivalent?

If any check fails, accept the SIG as partial evidence and send targeted follow-up questions for the gaps, rather than restarting the whole questionnaire.

Scale Your TPRM. Keep Your Headcount. Overcome five common roadblocks with autonomous workflows across the vendor lifecycle.

What breaks when you run the SIG at scale?

The SIG was designed to reduce duplicated effort, and at small volumes it does. The math changes as the portfolio grows.

  • 200 vendors: a team of two or three can still read every response. The pain is chasing vendors for completion and evidence. Spreadsheet tracking holds, barely.
  • 1,000 vendors: if even 15 percent are Tier 1 or Tier 2, that is 150 full-depth reviews a year, plus reassessments. Line-by-line reading becomes impossible. Reviews compress into spot checks, and evidence cross-checking is the first thing dropped.
  • 5,000-plus vendors: the program needs automation at intake, at answer review, and at reassessment, or it becomes a backlog with a dashboard on top. Version drift also bites here: vendors answer different SIG editions and presets, and nobody can compare results across the portfolio.

This is the point where SAFE TPRM earns its place. Intake AI extracts business context and recommends a tier and assessment depth. Auto-answering pre-populates questionnaire responses from documents the vendor has already supplied, with page and paragraph citations analysts can check. AI review flags vague, contradictory, or unsupported answers. Analysts spend their time on the Needs Attention list, not on rereading answers that already match the evidence. Kyriba used SAFE to streamline the assessment of 300+ vendors in one week.

What are the real trade-offs with the SIG?

Standardization vs. fit

A standard questionnaire saves your vendors time and improves response rates. A custom questionnaire asks exactly what you care about. Most mature programs land in the middle: SIG content for the baseline, plus a short set of engagement-specific questions (data residency, specific integrations, AI usage). The risk of going fully custom is that vendors cannot reuse prior answers, so completion slows.

Depth vs. completion

SIG Core gives you full coverage, but every extra question costs vendor attention. If your Tier 2 vendors take eight weeks to return Core, you may get better risk insight from SIG Lite plus targeted evidence requests completed in two weeks. Measure time to completion by tier and adjust.

Accepting the vendor’s SIG vs. sending your own

Accepting a vendor’s existing SIG is fast, but it may be stale or scoped to the wrong service. Sending your own guarantees fit, but duplicates the vendor’s work. With SAFE TPRM, you do not have to pick. The vendor’s existing SIG and supporting documents can be ingested as evidence and used to pre-populate answers to your own questionnaire, with citations, so you keep your question set and the vendor avoids starting from zero. Any gaps are flagged for follow-up rather than silently accepted.

Why SAFE TPRM for SIG-based assessments?

We built SAFE because the questionnaire was never the hard part. The hard part is knowing which answers to trust, which vendors to look at first, and what changed since the last review. SAFE treats a SIG response as one input to an evidence-based risk view, not the conclusion.

What the platform does today:

  • Risk-based intake and tiering. Intake AI parses request forms and contract summaries, extracts data types and access, and recommends a tier and assessment depth. The Intake Score captures inherent risk at onboarding, kept separate from the evidence-based Exposure Score that tracks residual risk over time. See vendor onboarding.
  • Document analysis and citation-backed auto-answering. SIG responses, SOC 2 reports, ISO/IEC 27001 certificates, and custom questionnaires are parsed and mapped to controls. Suggested answers carry page and paragraph citations. Analysts approve.
  • AI review and discrepancy detection. Vendor answers are compared against audit evidence. Unsupported claims and expired certifications are flagged with an explanation.
  • Reassessment reuse. New assessments can be pre-filled from prior responses, and previously submitted documents can be reused to answer new questions.
  • Continuous outside-in monitoring. External exposure, breach signals, and vulnerability findings on the vendor’s attributed infrastructure show what changed and why, so reassessment is driven by evidence, not just the calendar. See continuous monitoring.
  • Findings to remediation. Gaps become issues with owners, action plans, and status tracking through vendor interaction workflows.

San Francisco Health Plan speeds up third-party risk assessments by 90% with SAFE. If your team is drowning in SIG workbooks, bring one of your real vendor responses and a SOC 2 report and watch the review run. See SAFE TPRM in action or schedule a demo.

Recognized as a Leader. Ready for Your Team. Explore how SAFE’s autonomous TPRM can transform your vendor risk program.

Frequently Asked Questions