Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Questionnaire
Governance, Ownership & Risk

Questionnaire

← Back to Glossary
By NHI Mgmt Group Updated October 29, 2026 Domain: Governance, Ownership & Risk

A questionnaire is a structured set of questions used to collect information from people in a consistent way. In cybersecurity, identity and risk teams use questionnaires for vendor due diligence, security assessments and control attestation, often to gather details on access controls, authentication, data handling and incident response.

What a questionnaire does in cybersecurity

A questionnaire turns a broad information request into a repeatable evidence-gathering process. In security work, that structure matters because it lets teams compare answers consistently, spot gaps, and document what a vendor, business unit, or system owner says about controls.

The value is not the form itself, but the discipline it creates. Well-designed questionnaires reduce ambiguity, make review workflows more consistent, and help separate claims from evidence when an organisation needs to understand how a third party or internal service handles security obligations.

How questionnaires support due diligence and assurance

Questionnaires are common in vendor due diligence, security assessments, and control attestation because they scale review across many parties. They help teams ask the same core questions about access control, authentication, logging, data handling, incident response, and ownership, then compare responses against a baseline expectation.

That consistency is useful, but it is not proof. A questionnaire can tell you what someone says they do; it cannot by itself show whether controls are operating effectively. Strong programmes treat responses as an input to evidence review, not as the final answer.

For that reason, teams often pair questionnaires with policy review, technical evidence, audit artefacts, and follow-up interviews. The most useful questionnaires are precise enough to reveal control design, yet short enough that responders can answer accurately.

Questionnaire design, scope, and quality

Good questionnaires are built around the decision the reviewer needs to make. A vendor onboarding questionnaire should not look like a generic compliance survey if the real concern is privileged access, data residency, or incident notification. The wording should match the control being evaluated and avoid vague prompts that produce marketing language instead of operational detail.

Scope also matters. If a questionnaire mixes product security, corporate governance, privacy, and contractual terms without clear boundaries, it becomes harder to interpret answers and harder to assign ownership. Clear sections, plain language, and narrowly framed questions improve response quality.

In practice, the best questionnaires ask for concrete facts, such as whether a control exists, who owns it, how often it is reviewed, and what evidence supports the claim. That makes later verification much easier than relying on high-level yes or no answers alone.

Questionnaires in control verification and risk decisions

In security and identity programmes, a questionnaire is often the first pass in a larger decision workflow. It helps identify whether a supplier, system, or team may introduce exposure through weak access controls, incomplete incident response, unclear data handling, or poor segregation of duties. It also helps focus follow-up work where the answers suggest higher risk.

Questionnaires are most effective when they are tied to a review process, versioned over time, and kept aligned to the actual control objectives being assessed. Used well, they create an auditable trail of what was asked, what was answered, and what needs confirmation before trust is extended.

Risk and Threat Considerations

Questionnaires can create false confidence when organisations treat self-reported answers as equivalent to verified control performance. That is especially risky in vendor assessments and assurance workflows, where incomplete answers, vague language, or deliberate overstatement can mask real exposure.

Failure mechanism: Weak questionnaire design, poor follow-up, or overreliance on self-attestation can hide gaps in access control, authentication, incident response, or data handling until an audit, incident, or third-party failure exposes them.

Impact: The result can be unmet control expectations, delayed remediation, contractual exposure, and greater operational or security risk from relying on controls that were never adequately evidenced.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 and SOC 2 (AICPA) define the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5CA-3 — System InterconnectionsQuestionnaires support structured third-party control review before interconnection or reliance.
SA-9 — External System ServicesVendor questionnaires assess security claims about external services and supplier responsibilities.
RA-3 — Risk AssessmentQuestionnaires gather security facts used to identify and evaluate control gaps and residual risk.
Recommendation — Use CA-3 to require documented control terms and evidence before approving external system connections. Apply SA-9 to define security expectations and evidence for external service providers. Use RA-3 to collect consistent control data that feeds formal risk assessment decisions.
ISO/IEC 27001:2022A.5.19 — Information security in supplier relationshipsQuestionnaires are a common way to assess supplier security obligations and control maturity.
A.5.22 — Monitoring, review and change management of supplier servicesQuestionnaires help monitor whether supplier security commitments remain current over time.
Recommendation — Use A.5.19 to define security requirements and verification for supplier relationships. Use A.5.22 to review supplier security posture and update expectations when services change.
SOC 2 (AICPA)CC3.2 — Risk AssessmentQuestionnaire responses often support assurance over control design and risk identification.
CC9.2 — Third-Party Risk ManagementQuestionnaires are a standard assurance artifact for evaluating service providers and vendors.
Recommendation — Use CC3.2 to gather and evaluate information needed for control-risk assessment. Use CC9.2 to collect and review supplier control evidence before relying on their services.

Practitioner Guidance

Why practitioners should care: A questionnaire is only as good as the decisions it supports. If the questions do not map to a control objective, the output is difficult to verify and easy to misread.

What to watch for: Look for ambiguous wording, overly broad answer options, and requests that invite assertion instead of evidence. Those are common signs that the instrument will produce inconsistent results.

Practitioner takeaway: Treat questionnaires as a structured intake mechanism, not as proof, and always pair them with evidence review when the decision carries security or trust implications.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 29, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org