SecurityNovember 18, 2026 5 min read

How to answer a customer’s security questionnaire with evidence from your cloud

A customer, a public body or an auditor sends you their security questionnaire. What they usually ask, which framework is behind it, what you can show from your AWS, Azure or Google Cloud accounts and what your team has to provide.

This article is also available in:esfrpt

It almost always arrives the same way: an Excel file with dozens of questions, a short deadline and a salesperson waiting to close the deal. Some questions are about the cloud, others about policies, people and suppliers. Answering well is not saying “yes” to everything, but being able to show where each answer comes from.

What they usually ask

The format changes, but the topics repeat from one questionnaire to the next:

  • Who has privileged access, whether they use MFA and how often access is reviewed.
  • Whether data is encrypted at rest and in transit, and who manages the keys.
  • Which backups exist and whether restoring has been tested.
  • Whether activity is logged, how long it is kept and who monitors it.
  • How vulnerabilities are managed and how quickly they are fixed.
  • How incidents are detected, recorded and reported.
  • Which suppliers take part in the service and under which contracts.
  • Policies, staff training, continuity and physical security.

Which framework is behind each customer

The questionnaire usually comes from a specific framework, and knowing which one helps you understand what they expect:

  • The Spanish public sector and its suppliers: the ENS (Royal Decree 311/2022).
  • Essential and important entities in the EU, such as hospitals or energy companies: NIS2, which requires them to look after the security of their supply chain.
  • Banks, insurers and payment institutions: DORA, which requires them to manage the risk from their ICT third-party service providers as part of their ICT risk (Article 28).
  • Companies that ask for a recognised certification: ISO/IEC 27001.
  • US customers buying software: SOC 2.

The AAA Sentinel website has a page per framework (ENS, NIS2, DORA, ISO 27001 and SOC 2) showing what is checked automatically in each one and a worked example with a fictitious company.

What you can show from the cloud

Part of the answers lives in your accounts’ configuration: privileged roles, MFA, encryption, backups, logging, public exposure and changes. That part can be checked with a scan instead of console screenshots. And it should be, because a screenshot is a picture of one day, and what the customer wants to know is whether it is still the case.

That the cloud allows something does not mean it is done: a service that “supports encryption” does not prove your databases are encrypted. Useful evidence is about your resources, not the provider’s catalogue.

What your team has to provide

Some questions no tool can see from the cloud, and it is better to say so than to make up an answer:

  • Policies, risk analysis and staff training.
  • The contracts with your own suppliers and what you require of them.
  • Backup restore tests and continuity plans.
  • Physical security of your offices and internal procedures.

Answer once, reuse

The second questionnaire looks a lot like the first. If you keep the approved answers with their evidence, the next one starts half done. Returning the customer’s own Excel file filled in, format intact, saves them work too. And the documents you attach have dates: an expired policy in the next questionnaire costs credibility.

Mistakes to avoid

The most common ones:

  • Answering “yes” without being able to show where it comes from.
  • Mixing policy (“we will encrypt”) with practice (“it is encrypted”).
  • Assuming that what the cloud provider guarantees also covers your configuration.
  • Letting an AI answer and send without anyone on the team reviewing it.

How AAA Sentinel does it

With the risk and compliance add-on (€20 per cloud account a month, on top of Pro or Business):

  • You import the customer’s questionnaire, pasted, as CSV or as Excel, or start from the ENS, NIS2, DORA, ISO 27001 or SOC 2 template.
  • In the templates, each question says what the scan of your AWS, Azure and Google Cloud accounts checks and what your team answers; in an imported questionnaire, you link the questions the scan can back to a check. Coverage is partial and varies by framework and cloud.
  • AI drafts answers with the scan’s evidence, but never approves on its own: a person approves.
  • What you approve stays in your library, you link your documents with their expiry date and you return the customer’s Excel file filled in, or a PDF.
  • Every 10 minutes it reads your clouds’ audit logs and alerts you to critical changes. And if a later scan worsens the evidence behind an approved answer, or one of its documents expires, it tells whoever approved it.

What it does not do

It does not certify or replace the audit: it helps you gather the evidence and answer. The organisational side is still your team’s work, and the tool tells you which part is theirs in each question.