If you sell software to banks, insurers, healthcare systems or large enterprises, a SIG will eventually land in your inbox: a spreadsheet with hundreds of rows, a due date that is too soon, and questions that span every team in your company.
01What the SIG is
The Standardized Information Gathering (SIG) questionnaire is published by Shared Assessments, a member organisation focused on third-party risk management. It gives organisations a common, repeatable way to collect information about a vendor’s security, privacy and resilience controls, so buyers aren’t each inventing their own questions.
The content is revised on a regular cycle and mapped to widely used frameworks and regulations such as ISO 27001, NIST guidance, PCI DSS and privacy laws. That mapping is one reason risk teams like it: one set of answers can support several compliance obligations.
02Who sends it, and when
SIGs usually come from a buyer’s third-party risk management (TPRM) or vendor risk team, often during procurement and again at renewal. Financial services firms are the heaviest users, followed by insurance, healthcare and large enterprises with mature vendor programmes.
On the vendor side, it usually lands with a sales engineer or account executive, who then has to find answers from security, IT, HR, legal and engineering. That fan-out is where most of the time goes.
03How it’s structured
The SIG is organised into risk domains, each a tab or section in the workbook. Questions are mostly Yes / No / N/A with a comments column for explanation and evidence. Some answers trigger follow-up questions. A representative subset:
| Domain | What it asks about | Usual owner |
|---|---|---|
| Enterprise risk management | Risk governance, risk assessments, ownership | Security / GRC |
| Nth-party management | How you assess your own vendors and subprocessors | GRC / Procurement |
| Information assurance | Security policies, programme governance | Security |
| Human resources security | Background checks, training, offboarding | HR / Security |
| Access control | Identity, MFA, privileged access, reviews | IT / Security |
| Application security | SDLC, code review, testing, vulnerability handling | Engineering |
| Cybersecurity incident management | Detection, response, notification timelines | Security |
| Operational resilience | Business continuity, disaster recovery, testing | Ops / SRE |
| Privacy management | Data handling, data subject rights, transfers | Legal / Privacy |
| Cloud hosting services | Shared responsibility, hosting provider controls | Engineering / IT |
04How long it takes
A SIG Lite answered from scratch commonly takes a few days of elapsed time; a full SIG Core can take several weeks, mostly spent waiting on people outside the sales team. The writing itself is rarely the bottleneck. Finding the current, approved answer is.
05Common pitfalls
- Inconsistent answers across SIGs sent to different buyers. Risk teams compare notes, and auditors notice.
- “Yes” without evidence. A bare yes on encryption or MFA invites follow-up questions. A short explanation with the policy name avoids a second round.
- Stale answers copied from last year’s file after a policy or architecture change.
- Leaking other customers’ details when an old answer mentions a named customer, host or contract.
- Overclaiming. Answering “Yes” to a control that’s only partly in place creates contractual risk later.
06Answer faster with an answer library
The teams that handle SIGs calmly keep an answer library: approved answers to recurring questions, each linked to its source document, an owner and a review date.
- Seed the library from your last three to five completed questionnaires and your core policies.
- Give each answer an owner and a review date so it doesn’t silently go stale.
- Store the source alongside the answer, so reviewers check evidence instead of trusting memory.
- Route anything new or contested to the person who owns it, then add their approved answer back.
Is multi-factor authentication required for all remote and privileged access to systems that store or process client data?
1Access Control Policy v4.2 · Section 3.1 Authentication2Quarterly access review procedureWhy it works: it answers the literal question first, adds the detail a risk analyst would ask next, and points to the documents that prove it.
07How DeelSignal handles a SIG
DeelSignal imports the SIG in the format it arrived in and drafts each answer from your approved sources only: policies, past approved answers, SOC 2 report excerpts and product documentation.
- Sanitized first. Customer names, people, hosts, IPs, keys and amounts are swapped for placeholders before any model sees the text. Try the checker to see the idea.
- Cited, always. Every drafted answer links to the source passage it came from, so reviewers check evidence instead of rewriting.
- Stops and asks. When sources disagree or nothing covers a question, the agent holds it and routes it to the right expert over Slack or email.
- Exports ready to send. An Excel workbook in import order, a portal paste list, DOCX or PDF.