Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

How do we…

How do we write a customer-facing security overview that answers most questionnaires before they arrive?

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

Add to board memo

The short answer

Recommendation
Build the overview from the library answers that may go out as they stand, copied unchanged with what each covers and naming only the evidence their sharing tiers allow, and leave out any section without one. It describes and promises nothing, names certificates exactly, and is confirmed by people other than the authors before it is issued.
Reasoning
Every statement in the overview is one the organisation is held to, so it must come from an approved, owned answer, not fresh prose. Copying library answers keeps the overview in step with the answers the next form draws on. Ten of its 14 sections draw on one library topic each, and a section with no answer that may go out as it stands is better left out than filled with a statement nobody can support. Periods, recovery objectives, audit rights and liability belong in the agreement, through the standard commitments schedule.
Considerations
  • The overview answers the common questions, not all of them. Questions that depend on the date or on the customer's own contract are answered for each request.
  • Its next review follows the shortest topic interval, 6 months for incident notice and AI in the pack's defaults, and comes sooner when a statement changes.
  • Say the organisation is certified, compliant or aligned only when the evidence index holds a current document that says so for that scope and Legal has confirmed the wording. Describe a supplier's certificate as the supplier's.
  • Nobody approves a statement they wrote. Where the approver wrote one, the next level takes their place.

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 sending forms with the same questions

    A customer-facing overview answers the common questions once, in words the customer can read before the form arrives. It cannot answer every question. Some depend on the date or on the customer's own contract, and those are answered for each request. Every statement in it is a statement the organisation is held to.

    In the pack

  2. Step

    Name the services and the date the overview covers

    Name only the services the statements describe, and date the document. A statement about the online ordering service is not a statement about the warehouses. Do not say whether the organisation is an essential, important or financial entity unless Legal confirms it.

    In the pack

  3. Decision

    Is there a library of approved answers to draw from?

    Each statement in the overview is a library answer, used unchanged. Without approved answers there is nothing to take from, and writing the prose first creates statements nobody owns. If you do not know, answer no.

    In the pack

  4. Outcome

    Build the answer library first, then return

    Start with the questions customers ask most, a few answers for each topic, each with an owner, a scope of claim and evidence or the words Statement only. The overview comes after, as a view of the answers that may go out as they stand.

    In the pack

  5. Step

    Match each section to one library topic

    Ten of the 14 sections draw on one library topic each: governance, access, data protection, incident notice, resilience, development, suppliers, AI, privacy and physical. The other four are fixed text: about the document, who we are, the evidence you can share, and what the document is not.

    In the pack

  6. Decision

    Does the section have an answer that may go out as it stands?

    An answer may go out as it stands when its state is Current, Review due or Evidence expiring (QG-05). An answer with evidence expiring says when it expires. A draft, stale or withdrawn answer is not used. The overview names only the evidence each answer's sharing tier allows, which the evidence check below confirms. If you do not know, answer no.

    In the pack

  7. Step

    Leave the section out and answer it for each request

    A section with no answer that may go out as it stands is left out of the issued overview. Ten sound sections are worth more than fourteen that include a statement nobody can support. Renew or approve the answer in the library, and add the section at the next issue.

    In the pack

  8. Step

    Copy each answer unchanged and show what it covers

    Do not edit a statement in the overview. If it is wrong or out of date, change the library answer first with its owner's approval, then the overview. Each statement carries its scope of claim, so a customer knows how far to rely on it. The statement that the overview describes the organisation as at its date is used as the template gives it, with Legal confirming its wording.

    In the pack

  9. Decision

    Does any sentence give a period, objective, audit right or liability?

    The overview describes and promises nothing. It states no period for telling a customer of an incident, no recovery objective, no right of audit and no liability. Check for dates, actions and absolute words as well. If you do not know, answer yes and look again.

    In the pack

  10. Step

    Remove it and point to the standard commitments schedule

    Those terms belong in the agreement, through the standard security commitments schedule and its negotiation ladder. The overview says only that the schedule exists and that the customer should ask if they need something it does not offer.

    In the pack

  11. Decision

    Does a sentence name a certificate, report or standard?

    Name a certificate by its exact title, scope, issuer and dates, and say whose it is. Say the organisation is certified, compliant or aligned only when the index holds a current document that says so for that scope and Legal has confirmed the wording. If you do not know, answer yes.

    In the pack

  12. Step

    Name it exactly and have Legal confirm the wording

    A supplier's certificate is described as the supplier's, never as the organisation's own. In the pack's example the distributor holds no certificate of its own and the overview says so, which is a way to avoid leaving the customer to assume one. Legal confirms every sentence that names a certificate, a report or a standard.

    In the pack

  13. Decision

    Is each listed document in date and in a tier you may name?

    List Public and Under NDA items only. A Summary only item is listed by its approved summary. A Never shared item is not listed. An expired or withdrawn document is not listed, and a supplier's document appears only as its terms allow. If you do not know, answer no.

    In the pack

  14. Step

    Drop it, or list its approved summary in its place

    Describe each listed item by title, scope, issuer and dates, as the document states them, and no further. Where an item has expired, hold the answers that cite it until the owner renews it or the answers change.

    In the pack

  15. Decision

    Did someone other than the author confirm every statement?

    The topic owner of each section confirms its statements, Legal confirms any sentence that names a certificate, a report or a standard, and the pack's example has the Head of Information Security approve the whole overview (who that is depends on how you are governed). Run the response check on it as on any response. Nobody approves a statement they wrote. If you do not know, answer no.

    In the pack

  16. Outcome

    Hold it. The next level confirms before it is issued

    Where the author is the approver, the next level takes their place. Where the Head of Information Security wrote a statement, the executive decision-maker approves it (judgement on who that is: it follows how the organisation is governed). Do not issue an overview with an unconfirmed statement.

    In the pack

  17. Step

    Issue it with a version, date and review date

    The overview is only as fresh as its oldest answer. Set the next review at the shortest topic interval, which is 6 months for incident notice and AI in the pack's defaults, and sooner when a statement changes. Sales may send it with the Public evidence to a customer or a prospect in a live opportunity.

    In the pack

  18. Decision

    Has an answer, a document or a date changed since issue?

    Check at each review and whenever a certificate, test or policy is renewed or expires. A statement that has not been changed is still being relied on. If you do not know, answer yes.

    In the pack

  19. Step

    Change the index and library first, then the overview

    The order is evidence index, library answer, overview. Editing the overview alone makes it disagree with the library the next form will draw from. A wrong statement already sent follows the correction route.

    In the pack

  20. Outcome

    Offer it with the Public evidence ahead of a long form

    A form above the largest standard question set is first offered the overview and the evidence. Whether the customer accepts that in place of a full answer is for the triage decision.

    In the pack

Practical checklist

  1. Name the services the overview covers and the date it describes.
  2. Match each of the ten topic sections to its library topic, and use only answers that may go out as they stand: Current, Review due or Evidence expiring.
  3. Copy each answer unchanged with its scope of claim, say when any evidence expires, and leave out any section with no such answer.
  4. Remove any period, recovery objective, audit right or liability, and point to the standard commitments schedule instead.
  5. Name each certificate or report by its exact title, scope, issuer and dates, and have Legal confirm the wording.
  6. List only in-date Public and Under NDA items, with a Summary only item listed by its approved summary.
  7. Have each topic owner confirm their section, run the over-commitment checklist, and have the Head of Information Security approve the whole document.
  8. When an answer, a document or a date changes, update the evidence index, then the library, then the overview.

Evidence to have ready

  • The issued overview with its version, as-at date and next review date.
  • For each statement, the library answer it copies, with its owner, scope of claim and evidence reference.
  • The topic owners' confirmations, Legal's confirmation of certificate and standard wording, and the approval of the whole document.
  • The completed over-commitment checklist for the overview.
  • The evidence index entries for every document listed, showing its tier and dates on the issue date.

Assumptions

  • You have, or will build, a library of approved security answers with owners, scopes of claim and evidence references.
  • You have an evidence index that records each document's tier, issuer and dates.
  • The review intervals, the question threshold for offering the overview and the approver roles are the pack's defaults. Your own standard may set others, and the top approver depends on how you are governed.

Not covered here