ResilientX

SIG Questionnaire: Scoping and Response

Summary:

What the SIG questionnaire covers, how Lite, Core and Detail scoping works, what it costs to license, and a workflow for answering or reviewing one faster.

The SIG questionnaire is a standardized third-party assessment published by Shared Assessments. Instead of writing your own vendor security questions, you license a vetted question library, scope it to the risk the vendor actually carries, and send that. Shared Assessments states the SIG measures risk across 21 risk control areas, or "domains", covering everything from access control and cloud services to Nth party management and operational resilience.

Procurement teams reach for it because it is recognised on both sides of the table: the vendor has probably answered it before, which is the fastest route to a usable answer. If you want the assessment to run itself afterwards, that is what questionnaire automation is for.

What is the SIG questionnaire?

SIG stands for Standardized Information Gathering. It is a question library, not a certification: nobody "passes" a SIG. You send it, the vendor answers, and the answers become evidence in your own assessment.

The content is organised into the 21 domains Shared Assessments publishes: Access Control, Application Management, Artificial Intelligence, Asset and Information Management, Cloud Services, Compliance Management, Cybersecurity Incident Management, Endpoint Security, Enterprise Risk Management, Environmental Social Governance, Human Resources Security, Information Assurance, IT Operations Management, Network Security, Nth Party Management, Operational Resilience, Physical and Environmental Security, Privacy Management, Server Security, Supply Chain Risk Management and Threat Management.

Two things there matter in practice. Nth party management is in the list, so the SIG asks your vendor about their vendors — subcontractors you never signed a contract with. And the domains now include artificial intelligence and ESG, which is why an old internal questionnaire looks thin beside a current SIG.

Shared Assessments also publishes mappings from SIG content to external frameworks, including NIST, ISO, GDPR, DORA, CMMC 2.0, PCI DSS 4.0 and FedRAMP. That is the argument for a standard library over your own: one set of answers reports against several frameworks.

What is the difference between SIG Lite, SIG Core and SIG Detail?

Lite, Core and Detail are scope levels, not separate products. Shared Assessments describes SIG Lite as "a foundation of low-risk level questions for third parties" and SIG Core as "a comprehensive set of questions for third-party service providers that pose a higher risk". Detail is the deepest level available on a custom template.

Scoping, in Shared Assessments' own words, is "the act of configuring or creating a SIG Template by choosing the type and level of questions that are appropriate to your assessment requirements". You pick along three dimensions:

  • Risk domains — which of the 21 areas apply at all. A payroll processor does not need the SCADA-adjacent questions; a hosting provider needs cloud services and server security.
  • Control families — a finer cut within the domains.
  • Scope level — Lite, Core or Detail, setting how deep the questions go.

Either side can drive this: Shared Assessments confirms outsourcers and service providers can each create and complete SIG assessments, which is why vendors often arrive with one in hand.

How do you scope a SIG for a vendor?

Scope to the consequence of the vendor failing, not the size of the contract. A cheap vendor with production data access outranks an expensive one shipping office furniture. Our default:

Vendor tierWhat it looks likeScope levelDomains to always include
Tier 1 — criticalHosts or processes production or personal data; an outage stops a core serviceCore, moving to Detail for the top handfulAll 21, with Nth party management and operational resilience mandatory
Tier 2 — importantSystem access but no production data; a failure degrades rather than stops a serviceCore, trimmed to relevant domainsAccess control, incident management, application management, privacy
Tier 3 — limitedNo system access, no personal data; replaceable inside a weekLiteCompliance management, human resources security, information assurance
Tier 4 — minimalCommodity purchase, no data, no accessNo questionnaire; record the decisionNone

Two rules keep this honest: set the tier before you see the sales deck, and record why — an auditor asking "why was this one Lite?" wants the reasoning, not the score. Keep both in the same risk register you use for internal risks.

What does it cost to license the SIG?

The SIG is licensed, not free. Shared Assessments states it is available as a standalone product subscription and is included with all levels of Membership, and lists a Corporate License at USD 7,000 for one year. Access to the SIG Manager product is licensed to Product Subscribers and Members, in a cloud-based version (SIG EV) and in Excel.

Content follows what Shared Assessments calls an established annual release cycle, so budget for version churn as well as the licence: a library licensed two years ago and never refreshed is a liability, because the domains that changed are the ones your auditor will ask about.

How do you run a SIG without losing three weeks?

The questionnaire is rarely the bottleneck. Chasing it is. This workflow survives a real procurement cycle:

  1. Tier first, send second. Assign the tier and scope from the table above before the questionnaire leaves your hand.
  2. Set the response window in the request, not a follow-up. Ten business days for Lite, twenty for Core, with a named owner on both sides.
  3. Ask for evidence with the answers, not after them. A "yes" on encryption is worth nothing without the policy or certificate attached. Name the three or four artefacts you will actually read.
  4. Review by exception. Read the answers that contradict the tier, contradict each other, or arrive blank. Do not read all 21 domains at equal depth.
  5. Convert findings into dated obligations. Every gap gets an owner, a fix and a date, or becomes an accepted risk with a named accepter.
  6. Re-assess on the tier's clock, not the contract's. Tier 1 annually; the rest on renewal or material change.
  7. Keep the trail. Who asked, who answered, what was attached, what was decided.

Step 3 is where most programmes leak. Two domains reward attached evidence most: identity and access management, where answers are easy to overstate and easy to verify, and anything touching third-party code, where a software composition analysis report says more about dependency hygiene than a questionnaire answer will. Across dozens of vendors, TPRM software keeps steps 2, 5 and 7 from becoming someone's full-time job — book a demo to see the workflow end to end.

Where does the SIG fit under NIS2 and DORA?

A completed SIG is evidence, not compliance. But it maps onto duties both regulations impose.

NIS2, Directive (EU) 2022/2555, lists supply chain security among the minimum measures in Article 21(2)(d), covering security-related aspects of relationships with direct suppliers and service providers. Article 21(3) goes further: entities must take into account the vulnerabilities specific to each direct supplier and the overall quality of products and cybersecurity practices of their suppliers, including their secure development procedures. "Specific to each direct supplier" is the phrase that rules out one questionnaire for everyone — which is what scoping addresses.

For financial entities, DORA Article 28(4) requires that before entering an ICT services contract you identify and assess all relevant risks and undertake all due diligence on the prospective provider. Article 28(5) allows contracts only with providers that comply with appropriate information security standards. A scoped SIG with attached evidence is a defensible way to show both — but not sufficient alone: DORA also wants the register of information, concentration risk analysis and audit rights, none of which a questionnaire produces.

SIG, CAIQ or your own questionnaire?

Be honest about when the SIG is the wrong instrument.

SIGCAIQCustom questionnaire
Best forMixed vendor estates across regulated sectorsCloud service providers specificallyA narrow, unusual risk nobody standardised
Breadth21 domains, multi-framework mappingsCloud controlsWhatever you write
LicencePaid subscription or membershipFreely published by the Cloud Security AllianceFree to write, expensive to maintain
Vendor familiarityHighHigh among cloud providersNone

If your estate is mostly SaaS and your budget is nil, CAIQ answers more for less. If you need one instrument across cloud, payroll, logistics and a bank, the SIG's breadth wins. If you have three questions about one exotic dependency, write those three questions.

Frequently asked questions

Is the SIG questionnaire free?

No. Shared Assessments states it is available as a standalone product subscription and is included with all levels of Membership, with a Corporate License listed at USD 7,000 for one year. A vendor who already subscribes may share a completed SIG at no cost to you, which is the cheapest route to an answer.

How many questions are in SIG Lite?

Shared Assessments does not publish a Lite question count on its public pages, and the figures circulating on vendor blogs are not sourced to the publisher. Lite is defined by depth, not a fixed number, and the count moves with each annual release.

Who fills in the SIG — us or the vendor?

The vendor answers it; you scope and review it. Many vendors keep a current completed SIG and send it on request.

Does a completed SIG make us NIS2 or DORA compliant?

No. It is evidence toward specific duties — NIS2 Article 21(2)(d) and 21(3), DORA Article 28(4) and 28(5) — but neither regulation asks for a questionnaire. Both ask for risk-based decisions you can defend, with the register, monitoring and contractual terms around them.

How often should we re-send it?

On the vendor's tier, not the calendar. Annually for critical vendors, at renewal or on material change for the rest. Sending a full Core to a Tier 3 vendor every year trains everyone to ignore the process.

Standardising the questions is the easy half. What decides whether third-party risk is managed or merely documented is what happens after the answers arrive: chasing, scoring, evidence, dated remediation, the next cycle. That is the loop ResilientX automates — automate third-party risk with ResilientX TPRM, and browse the ResilientX Learning Center for the assessment and monitoring stages either side of the questionnaire.

Assess, monitor and remediate vendor risk in one place
Explore Third-Party Risk Management →