Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

How do we…

How do we build and keep a library of security answers we can reuse?

6 decision pointsThe pack behind this answer: Security Questionnaire & Due Diligence Response

Add to board memo

The short answer

Recommendation
Build the library from the questions customers ask most, under ten topics, each owned by the person who runs the control. Give every answer one scope of claim and evidence or the words Statement only, have someone other than its author approve it, and send only answers whose state lets them go out.
Reasoning
Every answer is a statement your organisation is held to, and a customer relies on it when it buys. Answering from the last form or from memory repeats old mistakes. A library lets you answer once, from an approved source, with evidence behind it. The scope of claim stops a true answer for one service being read as true for the company. The library works out each answer's state from its dates and evidence, so a stale answer or one with expired evidence is caught before it goes out.
Considerations
  • The ten topics and the review intervals are the pack's defaults: 12 months, and 6 months for incident notice and AI. Your own method may set different ones.
  • The over-commitment checks can raise the approver. A promise, a right of audit, a liability or a claim of certification or compliance needs Legal and the Head of Information Security, with the Data Protection Officer where personal data is involved.
  • Nobody approves an answer they wrote. A small team names its next level in advance, usually the managing director or an outside adviser who has signed a non-disclosure agreement.
  • A drafting tool, including an AI assistant, may suggest wording only from the library and only if it is approved for the data it sees. What it drafts takes the approval of a new or adapted answer.

The decision, step by step

Select any step for the reasoning behind it and where the pack covers it.

  • Start
  • Step
  • Decision
  • Outcome
  • Loop back

Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.

Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one.

Read as text

The same flow written out: each step, its reasoning and where the pack covers it. 20 steps.
  1. Start

    Customers keep asking the same security questions

    Every answer you give a customer is a statement your organisation is held to. A customer reads it as a description of what you do and relies on it when it buys. Answering from the last form or from memory repeats old mistakes. A library lets you answer once, from an approved source, with evidence behind it.

    In the pack

  2. Step

    Group the questions under ten topics, each with one owner

    The pack uses ten topics: Governance, Access, Data protection, Incident notice, Resilience, Development, Suppliers, AI, Privacy and Physical. Each topic has a named owner, the person who runs the control. The review intervals are the pack's defaults: 12 months, and 6 months for incident notice and AI. Change an interval only if your own method says so.

    In the pack

  3. Step

    Start with the questions customers ask most

    Judgement call. The pack lets a small organisation begin with the questions it is asked most and grow the library from the forms it receives, leaving other topics empty until a customer asks. A short library you keep in date is worth more than a long one that goes stale. Take the questions from forms you already hold and answer each once.

    In the pack

  4. Step

    List the evidence you can show in an evidence index first

    An answer that states a control, a test or an assurance must cite evidence or say it is a statement only. So list the documents you could show a customer first: certificates, reports, test summaries, policy extracts, attestations. Give each an issuer, a scope, an expiry date and a sharing tier. The library copies from this index, which stays the master.

    In the pack

  5. Step

    Write one customer-ready answer per question

    Write in the first person plural with no internal document or rule IDs in the words. The topic owner writes or confirms each answer. A drafting tool may suggest wording only from the library, and only if it is approved for the data it sees. What it drafts is a new or adapted answer and takes its approval. A questionnaire never goes into a tool that is not approved for Confidential data.

    In the pack

  6. Decision

    Does the evidence support the scope you want to claim?

    Every answer carries one scope of claim: whole company, a named service, a named site, a named system or tool list, a supplier's service, a written policy only, or a plan with a date. The scope must be no wider than the evidence supports. A control at one service is a control at that service. A written policy shows what you require, not that every case meets it. If you are not sure, take the narrower branch.

    In the pack

  7. Step

    Narrow the scope, state a dated plan, or mark it statement only

    Name the service or site the control really covers. If the control is planned, give it the plan scope with its date and never word it as present. A supplier's control is about the supplier's service, so say whose it is. With no evidence at all, the entry says it is a statement only. An answer with no scope, or with a scope its evidence does not support, is not used.

    In the pack

  8. Decision

    Do the words trip an over-commitment check?

    The checklist runs eight checks on the wording: absolute words, time and frequency promises, claims about everything, certification and compliance claims, promise verbs, audit and access rights, liability and remedy, and plans worded as present. A flag does not mean the answer is wrong. It means someone with the right authority reads it first. If you have not run the checks, answer yes.

    In the pack

  9. Step

    Reword it, or send the flag to the approver it sets

    Describe what is done today in the present tense, or point to the standard commitments schedule instead of stating a period. A check raises the answer to a kind, and the kind sets who clears the flag in writing. A promise, a right of audit, a liability or a remedy goes to Legal and the Head of Information Security, as does a claim of certification or compliance. Absolute words, claims about everything and a plan worded as present make it an adapted answer, which the topic owner confirms. The Data Protection Officer joins where a commitment or claim concerns personal data. A cleared flag stays on the library entry while the words stay the same.

    In the pack

  10. Decision

    Is the approver also the person who wrote the answer?

    Nobody approves an answer they wrote. The kind of answer sets the approver: a new answer needs the topic owner and the Head of Information Security, an adapted answer needs the topic owner, and a promise or a claim needs Legal and the Head of Information Security. If the author is one of those people, the next level takes their place. If you are not sure who wrote it, answer yes.

    In the pack

  11. Step

    Name the next level to approve in their place

    The pack names the next level for each author. For example the questionnaire response lead's answers go to the Head of Information Security, and the Head of Information Security's go to the executive decision-maker. A small team names its next level in advance, usually the managing director or an outside adviser under a signed non-disclosure agreement, and keeps a short written record of each approval. The response lead records who was replaced.

    In the pack

  12. Step

    Enter it as Approved with owner, scope, evidence and review date

    A new answer is a Draft until its approver approves it. Then set it to Approved and enter the day the owner last reviewed it. The review date follows from the topic's interval. The entry now holds the answer, its scope, its evidence IDs, its owner and any cleared flags, so the next person need not raise them again.

    In the pack

  13. Step

    Answer forms from the library and change the library first

    For each question in a customer's form, find the matching library answer and copy it unchanged. If the words must change, change the library entry first, with its owner's approval, and then use it. Never edit an answer inside the customer's form. A question with no match goes to the topic owner and joins the library once approved. Do not send the workbook itself, because its basis column is internal.

    In the pack

  14. Decision

    Can the answer go out as it stands today?

    The library works out a state from the dates and the evidence. Current, Review due and Evidence expiring may go out, and the last two prompt a review or a renewal. Withdrawn, Not approved, No scope, No evidence reference, Evidence expired and Stale may not. If you cannot tell the state, answer no. The response lead reports the count past review and the evidence expiring as counts, never a score.

    In the pack

  15. Outcome

    Send it as it stands, then review or renew if prompted

    Send the answer word for word. If its state is Review due or Evidence expiring, say when the evidence expires where that applies, and schedule the owner's review or the evidence renewal now, so that the answer is not Stale or expired by the next request.

    In the pack

  16. Decision

    Is the answer still true for the scope it claims?

    The topic owner checks the answer against what happens on a bad day. If the answer differs from the practice, the answer follows the practice. A Stale answer can be confirmed or changed. For Evidence expired, the owner either renews the evidence or changes the answer. Not approved, No scope, No evidence reference and Withdrawn are faults in the entry, not matters to confirm: take the no branch. If the owner cannot say, take the no branch.

    In the pack

  17. Outcome

    Owner confirms or renews, with a new review date and no other change

    For a Stale answer, a confirmation changes the review date and nothing else. If any word needs to change, it is a change, not a confirmation. For Evidence expired, renew the evidence in the index first. Once the owner has done so, the answer can be Current again and the next request can use it.

    In the pack

  18. Decision

    Did an earlier response already send the wrong answer?

    Search the tracker and the stored responses for every response that used the answer. If a customer has the old text, withdrawing it from the library is not enough. If you cannot search the old responses, answer yes.

    In the pack

  19. Outcome

    Withdraw it and correct the customer by the correction route

    Withdraw the answer at once and keep it in the library with the reason, so the affected responses can be found. The pack rates a correction minor or material. For a material one, Legal and the Head of Information Security approve a written correction, and the account owner sends it within the pack's correction window. A control that does not work, or exposed personal data, also goes to the incident route. Take it to the correction route.

    In the pack

  20. Step

    Change the entry and put it through approval again

    Rewrite the answer as the owner states it. A changed answer is checked for flags again and approved by the approver its kind sets. For a Withdrawn answer, the changed wording is a new entry. No earlier response used the wrong text, so no customer notice is needed.

    In the pack

Practical checklist

  1. Group the questions under the ten topics and name an owner for each, the person who runs the control.
  2. Start with the questions customers ask most, taken from forms you already hold.
  3. List the evidence you can show in an evidence index, with its issuer, scope, expiry date and sharing tier.
  4. Write one customer-ready answer per question, with one scope of claim and evidence or the words Statement only.
  5. Run the over-commitment checks, reword where you can, and send any remaining flag to the approver its kind sets.
  6. Have the approver for the answer's kind approve it, never its author, then enter it as Approved with its review date.
  7. Copy answers into forms unchanged, changing the library entry first when the words must change.
  8. Have the owner confirm, renew or change a Stale or Evidence expired answer, and withdraw a wrong one and find every response that used it.

Evidence to have ready

  • The library: each answer with its topic, owner, scope of claim, evidence IDs or Statement only, status and review date.
  • The evidence index, with each item's issuer, scope, expiry date and sharing tier.
  • The approval for each new or adapted answer, with the approver's role, and the written clearance of each flag.
  • Withdrawn answers kept with their reason, and the stored copies of the responses that used them.
  • The counts of answers past their review date and of evidence items expired or expiring.

Assumptions

  • Customers send you security questionnaires or due diligence requests, and you answer them as a supplier.
  • Someone is named as questionnaire response lead, and each topic can be given an owner who runs the control.
  • You keep the tracker and a stored copy of each response you send, so that the responses which used an answer can be found later.

Not covered here