SIG Lite: what the sections cover and how to answer it fast
Short answer: SIG Lite is the shorter, program-level version of the Standardized Information Gathering (SIG) questionnaire published by Shared Assessments. Buyers' third-party risk teams send it to lower-risk vendors, or as a first screen before deciding whether a full SIG Core is needed. It's an Excel workbook (or, since 2026, an assessment in Shared Assessments' web platform, SIG EV) drawn from the same question library as SIG Core, scoped across up to 21 risk domains. Most rows ask for Yes, No or N/A plus a comment. The fastest way to answer it is to keep one current set of approved answers and evidence and reuse them, rather than starting each SIG Lite from a blank sheet.
Who this is for: security, GRC and sales engineering teams at vendors who just received a SIG Lite from a customer's vendor-risk team.
On this page
- SIG Lite vs SIG Core: which one did you get?
- How is a SIG Lite structured?
- What does each domain ask about? (section map)
- How do you answer a SIG Lite row?
- Sample answers (fictional company)
- Evidence checklist
- How to answer a SIG Lite fast
- How Iris handles a SIG Lite
- FAQ
SIG Lite vs SIG Core: which one did you get?
| SIG Lite | SIG Core | |
|---|---|---|
| Purpose | Program-level view; screening and lower-risk relationships | Detailed view for vendors handling sensitive or regulated data |
| Depth per domain | A few high-level questions per domain | Many detailed questions per domain |
| Who chooses | The buyer, based on how they tier your risk | The buyer |
| Length | Shorter. Exact count varies by edition and scope; check the cover tab | Longer, with more detailed questions per domain |
| What it often signals | "We need a baseline before we go further" | "You'll hold data we're accountable for" |
Rule of thumb: answer what you were sent. If you received a Lite, ask the requester whether a Core or follow-up questions are planned, so you don't get surprised two weeks before signature. Buyers can also build a hybrid (Lite in most domains, deeper questions in a few), and Shared Assessments updates the workbook each year, so ask which edition and scope you were sent.
How is a SIG Lite structured?
This is the question behind the long "SIG Lite questionnaire structure fields" searches. A typical SIG workbook you receive has:
| Part | What it holds | What you do |
|---|---|---|
| Instructions / cover tab | Edition, requester's name, due date, scoping notes | Note the edition and due date; don't edit |
| Business information tab | Your company profile: legal entity, locations, services in scope | Fill once, reuse across every SIG |
| Domain tabs or sections | Questions grouped by risk domain | Answer each row |
| Answer column | Usually a Yes / No / N/A dropdown | Pick one; never type free text here |
| Comment / additional information column | Free text | Scope, how, and where the evidence lives |
| Supporting documentation reference | Space to name attached documents | Reference by filename and section |
Requesters sometimes add their own columns (risk rating, reviewer notes). Leave theirs alone and answer only yours.
What does each domain ask about?
Shared Assessments lists 21 risk domains on its SIG page. A requester scopes a SIG Lite to the domains relevant to you, so you'll rarely see all 21. Below, each domain is summarized in our own words; it is not SIG question text.
| SIG risk domain | What reviewers want to know, in plain terms | Usual owner | Evidence to have ready |
|---|---|---|---|
| Enterprise Risk Management | You run a risk program and review it | Security lead | Risk assessment summary, risk register process |
| Compliance Management | You know which laws and standards apply and track them | Compliance / Legal | Compliance obligations list, SOC 2 report |
| Information Assurance | A security program exists with ownership and policies | Security lead | Information security policy, org chart of security roles |
| Human Resources Security | Screening, training, offboarding | HR + Security | Background check and training policy |
| Physical and Environmental Security | Offices and data centers are protected | Facilities / Security | Cloud provider attestation reference |
| Access Control | Least privilege, MFA, access reviews | IT / Security | Access control policy, review cadence |
| Application Management | Secure development, testing, change control | Engineering | SDLC policy, pen test summary |
| Asset and Information Management | Data is classified, inventoried, retained and deleted | Data owner / Privacy | Data classification and retention policy |
| Cloud Services | How you use cloud providers and split responsibility | DevOps | Architecture overview, shared-responsibility notes |
| Endpoint Security | Laptops are managed, encrypted, patched | IT | Endpoint standard |
| Network Security | Segmentation, firewalls, remote access | DevOps | Network security standard |
| Server Security | Hardening, patching, monitoring of hosts | DevOps | Hardening and patching standard |
| IT Operations Management | Backups, capacity, change, operations | SRE / IT | Operations procedures |
| Threat Management | Vulnerability scanning, threat intel, patch timelines | Security | Vulnerability management policy |
| Cybersecurity Incident Management | You detect, respond to and notify about incidents | Security operations | Incident response plan, notification commitments |
| Operational Resilience | Business continuity and disaster recovery, tested | SRE | BC/DR plan and last test date |
| Privacy Management | Personal data handling, rights requests, DPAs | Privacy / Legal | Privacy policy, DPA |
| Nth Party Management | You oversee your own vendors and their vendors | Procurement + Security | Subprocessor list, vendor risk policy |
| Supply Chain Risk Management | Risks from suppliers and components | Procurement + Security | Vendor risk policy |
| Artificial Intelligence | How you use AI, govern it and protect data in it | AI/ML owner + Security | AI usage policy, model provider list |
| Environmental, Social, Governance (ESG) | ESG commitments and reporting | Ops / Legal | ESG statement if you have one |
How do you answer a SIG Lite row?
- Answer column first. Yes, No or N/A. "Partially" belongs in the comment, not the answer.
- Comment: one to three sentences. What you do, its scope, and where the evidence is. "See Access Control Policy §4" beats a pasted page of policy.
- N/A needs a reason. "N/A: we operate no data centers; physical security is inherited from our cloud provider (see its SOC 2 report)."
- Check consistency. MFA, encryption, retention and incident notification come up in several domains. The same fact must read the same way every time, and match your SOC 2 report.
- Don't over-commit. A "Yes" to something your policy doesn't require turns into a contractual promise during negotiation.
Sample answers (fictional company)
Written for a fictional SaaS company, "Fernhill Software." The question themes are paraphrased, not SIG text.
Access Control theme: Is multi-factor authentication required for remote and privileged access?
Answer: Yes
Comment: MFA is enforced through our identity provider for all workforce logins, including remote access and administrative consoles. Privileged access is approved per request and reviewed quarterly. See Access Control Policy §4.
Why it works: direct answer, scope, review cadence, one evidence pointer.
Physical and Environmental Security theme: Are data center facilities secured?
Answer: N/A
Comment: Fernhill operates no data centers or server rooms. Production runs on a major cloud provider whose physical controls are covered by its SOC 2 Type II report, which we review annually under our Vendor Risk Policy §3.
Why it works: N/A with a reason and a pointer to who does own the control.
Artificial Intelligence theme: Is customer data used to train AI models? (honest and specific)
Answer: No
Comment: Fernhill's product uses a third-party large language model through our cloud provider's managed AI service. Our contract with that provider and our DPA prohibit using customer data to train models. Our AI Usage Policy (attached) lists approved model providers.
Operational Resilience theme: Is the disaster recovery plan tested? (honest partial)
Answer: Yes
Comment: We test backup restoration quarterly. A full regional failover exercise is planned for Q1 next year; the last tabletop exercise was in [month, year]. See BC/DR Plan §6.
Evidence checklist
- [ ] SOC 2 Type II report (and a SOC 2 bridge letter if the period ended a few months ago)
- [ ] Penetration test executive summary
- [ ] Information security policy and policy index with review dates
- [ ] Access control, encryption, and vulnerability management policies
- [ ] Incident response plan
- [ ] BC/DR plan and the date of the last test
- [ ] Data retention and deletion policy
- [ ] Privacy policy and DPA
- [ ] Subprocessor list and vendor risk policy
- [ ] AI usage policy, if your product uses AI
How to answer a SIG Lite fast
- Fill the business information tab once and keep it in your answer library.
- Assign by domain on day one. Use the "usual owner" column above. Engineering shouldn't see privacy rows.
- Start from your last completed SIG, then check every reused answer against current policy. Copying an old SIG forward is the most common source of contradictions.
- Answer from policy, not memory. If no policy covers a row, the honest answer is a gap note, not a guess.
- Keep the CAIQ in sync. Many SIG Lite topics overlap the CAIQ; the same approved answer should serve both.
How Iris handles a SIG Lite
- Upload the requester's workbook as-is. Iris annotates each cell as question, answer, dropdown or section across tabs, including the Yes/No/N/A dropdown and the separate comment column, then writes answers back into the original workbook. A SIG delivered in a web portal can be handled in the browser with the Chrome extension.
- Drafts come only from your content: uploaded policies, your SOC 2 report, synced sources such as SharePoint, Google Drive, Confluence, Notion or Vanta, and approved answers from past questionnaires.
- Every answer cites its source and carries a High, Medium, Low or Contradictory label, so reviewers see where two policies disagree.
- When a policy is silent, Iris answers "There is not enough information to answer the question" instead of guessing. Those rows can't be approved as-is and are left blank in the export.
- Assign domains to InfoSec, Legal or IT, and attach evidence once; Iris suggests it again when the answer is reused.
Iris is a respondent tool: it works on the workbook you received. It isn't affiliated with Shared Assessments and doesn't supply SIG content.
Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered — or on a SIG Lite you've already completed, and compare.
FAQ
What is the SIG Lite?
The shorter, program-level version of the Shared Assessments Standardized Information Gathering questionnaire, used for lower-risk vendors or early screening.
How many questions are in SIG Lite?
It depends on the edition and on how the requester scoped it. Check the edition on the cover tab.
Is SIG Lite free?
No. The SIG is a licensed Shared Assessments product (listed at $7,000/year for a corporate licence on its site as of 2026-10-31, and included with membership). The buyer who sends it to you usually holds the licence.
What's the difference between SIG Lite and SIG Core?
Lite asks fewer, higher-level questions per domain; Core goes into detail for vendors that handle sensitive or regulated data. See the SIG guide.
Can we reuse SIG Lite answers for a CAIQ or a custom questionnaire?
Yes, if they're kept as approved answers with owners and review dates. The topics overlap heavily; the wording just needs to fit each format. See security questionnaire frameworks compared.
See it live
Respond to RFPs
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
