Skip to article content

How to respond to a client’s security questionnaire

If a client asks about your company’s security, some answers will come from your team and others from your suppliers. Learn how to organise the questions and gather the information you need.

Establish which service your client is assessing

A commercial conversation progresses and a spreadsheet arrives asking about access, backups and incident management. Some questions seem to concern your website; others cover the whole business. Clarify the service, systems and data within the assessment before answering.

A client using a private area of your platform has a different relationship from someone browsing public information. That does not automatically resolve the questionnaire, but helps establish which questions concern the contracted service.

Where wording is ambiguous, agree its meaning with the client. A precise response helps both parties understand the relationship and avoids attributing one service’s controls to another.

Assign questions by responsibility and evidence

One question may need input from several people. Hosting can provide infrastructure details, the technical team can explain application controls, and the business can describe its procedures and decisions.

Illustrative questions written for this guide
QuestionWho to involveEvidence to gather
How is website access managed?Application owner and person managing joiners and leavers.Configuration, roles and the actual process used.
What backups exist and how is recovery checked?Hosting and the backup owner.Coverage, retention and recovery checks.
Who responds to an incident?Security or operations lead.Agreed procedure and contacts.
Where is data hosted?Service owner and relevant suppliers.Current contractual and technical information.
Is there a certification?Person responsible for that accreditation.Current document, certified entity and exact scope.

This is an organising tool, rather than a universal questionnaire or compliance assessment. The NIST cybersecurity supply chain quick-start guide provides context on responsibilities and supplier relationships.

Answer within the limits of verified information

Record the source and date behind each answer. A configuration observed on one website does not necessarily describe all company services. A supplier’s safeguards also need to be read within their own scope.

If information is missing, record what remains open, who can confirm it and when it will be reviewed. For a yes-or-no form, agree how to add the necessary context in comments or a supporting document.

“Not applicable” also needs a reason: identify the service being assessed and why the control falls outside it. That is different from “we do not know yet”. If scope is unclear, resolving it with the client helps avoid a misleading answer.

Describe what exists rather than what would be desirable. Explain which security measures you already use, which are only partly in place and which are planned. This helps the client understand the current situation and what remains to be done.

An example: having backups and being able to recover

Fictional example. These conditions explain how to prepare an answer and do not describe a client.

A company knows its hosting provider takes backups, but has not confirmed what they include or when recovery was last checked. It cannot yet fully answer a question about verified backups.

A working note could say: “The hosting provider reports that backups are taken. We are checking what those backups contain and whether there is evidence that they can restore this service.” The supported answer can follow once documentation is obtained.

Once confirmed, the final answer should describe the backups covering that service and identify the available recovery evidence. Any missing check remains an open item with an owner. A planned improvement should not be presented as an operating control.

Provide enough evidence while protecting internal details

Agree which evidence the client needs and how it will be shared. Avoid routinely sending credentials, personal information or full reports revealing unnecessary system details. Review recipients, permissions and applicable confidentiality commitments.

A summary can identify the control and evidence reviewed without exposing the full configuration. Where more detail is required, the responsible person should prepare and review it.

If a technical scan forms part of the evidence, use our guide to understanding its findings. A dated assessment should retain that time context.

What a website assessment can contribute

A technical review can support evidence about components and configurations within its scope. By itself, it does not establish company-wide procedures, replace certification or constitute a dedicated compliance assessment.

Nodo91 can help define the website security checks you need to gather useful information. If the questionnaire creates several tasks, use the improvement priority matrix and share both confirmed information and work still in progress.