What a customer's security questionnaire is really asking you
The form looks like a test of your security. Most of the time it is a test of whether anyone owns the answer.
The questionnaire arrives from a customer's procurement team, usually after the commercial terms are agreed and usually with a deadline. It runs to eighty questions, half of which do not apply to a company your size. The temptation is to answer it the way you would answer an exam: quickly, optimistically, and in a way that gets the deal moving.
Read the form again and notice what it is for. The buyer is not auditing you. The buyer is collecting evidence that their own auditors, their own customers and their own insurers will accept. They need your answers to be consistent, written down, and defensible by someone in their organization who has never met you. A confident answer that turns out to be wrong is worse for them than an honest gap with a plan attached.
So answer the question that was asked, not the one you wish had been asked. If you do not have multi-factor authentication on every account, do not write that you do. Write what is covered, what is not, and when the rest is planned. The same applies to logging, to encryption at rest, and to the phrase everyone reaches for: 'industry standard'.
Consistency matters more than perfection. Your insurance form, your questionnaire answers and anything on your website should describe the same estate. When a buyer spots two different accounts of your backup arrangements, the deal slows down and the questions get harder.
The last thing is ownership. Someone inside the company has to be the person who can say why an answer was given, and answer a follow-up six months later. If that person does not exist, that is the actual finding — and it is usually the reason an assessment is worth doing before the next questionnaire arrives.