Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Privacy & Compliance 5 min read

Vendor security questionnaire risks and controls

Where vendor security questionnaires mislead, how to rate the risk they leave behind, and the evidence and contract controls that reduce it.

E
EncryptTechBD · 0 comments
Doctor updating patient notes at a desk
Photo: Direct Media / StockSnap

"We sent them a questionnaire and they passed" is one of the weakest sentences in procurement. A completed form proves that someone answered questions. It does not prove that the answers are true, current, in scope, or relevant to the data you are about to hand over.

Vendor risk is not a paperwork exercise. It is the discipline of deciding which suppliers can hurt you, what evidence you need, and which controls you keep after the contract is signed. This guide covers the risks that hide behind a clean score and the checks that make the questionnaire useful.

What a questionnaire can and cannot tell you

It can tell you what the vendor understands about its own controls. It can also start a useful conversation about ownership, incident contacts and data flows. It cannot tell you whether a control operates every day, whether the audit scope covers the service you bought, whether a subcontractor holds the data, or whether the answer was written by someone in sales.

Treat the questionnaire as a triage tool. It decides who needs deeper evidence and a conversation. It does not decide who is safe.

Eight risks behind a completed form

  1. Scope mismatch. The certification may cover the head office or one product, not the service you are buying. Ask for the scope statement and the systems included.
  2. Certificate confused with a report. A certificate shows that an audit happened. A SOC 2 Type II report shows which controls were tested over a period and what the auditor found. Read the exceptions, not only the opinion.
  3. Subprocessor blind spots. The vendor may use hosting, support, analytics or AI providers you never assessed. Ask for the list and a change-notification clause.
  4. Self-attestation treated as evidence. An unsigned answer or a marketing page is not evidence. Ask for the policy, the log, the report or a walkthrough.
  5. Point-in-time comfort. A report from eighteen months ago says little about the service today. Ask for the latest period and a bridge letter for the gap.
  6. Access that outlives the contract. Admin accounts, API keys and integrations are often forgotten at exit. Design least privilege and offboarding before go-live.
  7. Data use beyond the service. Some terms allow the vendor to use customer data to improve products or train models. A security questionnaire rarely covers this; the contract must.
  8. Concentration risk. One supplier may host the store, process payments and provide support. The questionnaire assesses each service but not the effect of losing all three at once.

Rate likelihood and impact without pretending precision

Do not score vendors out of one hundred. Use High, Medium and Low with a written reason. Consider five factors: the sensitivity of the data, the level of access, whether an action is reversible, how quickly you would detect a problem, and how many customers or systems are affected.

Rate inherent risk first, then the controls, then residual risk. A design agency with email access to a few staff is not the same risk as a payroll provider holding bank details and national ID numbers. The tier should decide the depth of evidence and how often the relationship is reviewed.

Evidence that beats a tick box

  • Audit report: SOC 2 Type II covering the relevant period, with the report scope and any exceptions explained.
  • Certification scope: ISO/IEC 27001 certificate with the scope statement and Statement of Applicability, not just the logo.
  • Independent testing: a penetration test summary with a date and the status of critical findings.
  • Data map: subprocessors, data residency, retention and deletion.
  • Access design: SSO, MFA, role model and privileged access review.
  • Incident terms: notification window, named security contact and cooperation obligations.
  • Recovery evidence: a restore or continuity test result, not only a plan.
  • Contract terms: data processing agreement, audit rights, breach liability and exit assistance.

Controls after signature

The questionnaire is a pre-contract artefact. The risk continues for as long as the relationship does.

  • Use single sign-on and scoped tokens. Avoid shared admin logins.
  • Give the vendor the minimum data and access the service needs.
  • Log vendor access and review it on a schedule.
  • Require notice of subprocessor changes and material security changes.
  • Review the relationship annually, and sooner after an incident or ownership change.
  • Keep an exit plan with data export, deletion confirmation and a transition window.

Questions the board should ask

  • Which vendors can stop revenue, expose customer data or move money?
  • Who owns each relationship, and when was it last reviewed?
  • What changed since approval: new subprocessor, new data, new access?
  • What evidence did we see, and what did we accept without evidence?
  • What would we do in the first 24 hours after a vendor incident?
  • Can we leave within a reasonable period without losing data or service?

Red flags in the process

Be cautious when a vendor refuses to share the audit report, describes itself as certified without naming the scope, cannot list its subprocessors, or routes every security question through sales. A slow answer is not automatically a bad sign, but an unwillingness to provide evidence is. Record what was requested, what arrived and what you accepted, so the decision can be reviewed later.

Where this fits in our work

If you need a defensible vendor review process rather than another spreadsheet, start with Managed Technology & Cybersecurity. The pricing page explains how an assessment is scoped. For the wider programme, read third-party security risk.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes