Skip to content
Free template · copy-ready

CISO Liability & Documentation-Hygiene Checklist

After SolarWinds and Uber, the accountability for a cyber failure can land on the named security officer personally. What protects you is a clean, contemporaneous trail: what you attested, what you escalated to the board, who owns each accepted risk, and the coverage that backs you. This checklist gives you the structure to build that trail before you need it.

Educational template — not legal advice. The SolarWinds and Uber matters and the legal and insurance concepts are summarised for orientation and can change; adapt this with qualified counsel and your insurance broker.

Free · no signup · adapt it in your own doc

CISO Liability & Documentation-Hygiene Checklist

A personal protection record for the named security officer. After the SolarWinds SEC action and the Uber CISO conviction, what shields you is a clean, contemporaneous trail: what you attested, what you escalated, who owns each accepted risk, and the coverage that backs you. Use this to build that trail before you need it. Educational — not legal advice; adapt with qualified counsel.

01Attestations & representations — never sign blind

Before you put your name on any security certification, questionnaire, SOC/ISO representation or disclosure sign-off, confirm you can stand behind it — and qualify it where you cannot. The SolarWinds action centered on security statements alleged to overstate the company’s posture; a signature on something false or unsupported is where personal exposure begins.

  • I have read the exact wording and understand what is being certified
  • Every claim is supported by current evidence I can produce on request
  • Anything only partially true is qualified — scoped to my knowledge, with what it relies on and what is still being assessed stated explicitly
  • I have NOT signed any blanket "fully implemented and operating effectively" statement I cannot support
  • Public-facing security claims (website, sales collateral, filings) match internal reality; I have flagged in writing any that do not
  • The evidence behind what I attested is retained and dated
Attestation / statement
What was signed, to whom, date
Basis & scope
What it relies on; limited to my knowledge of…
Carve-outs / qualifications
What I did NOT certify and why
Supporting evidence location
Where the proof is held
If you are pressured to sign something you know is false or unsupported, do not sign it as written. Correct or qualify it, and document the request.

02Board & audit-committee reporting log

Your central protection is a contemporaneous record of what you escalated, to whom, and when. When regulators and plaintiffs reconstruct "who knew what, when," this log is the difference between being the officer who raised the alarm and the officer who stayed silent. Log material risks as you brief them — do not reconstruct afterward.

DateTopic / risk reportedWho was toldDecision / outcome
YYYY-MM-DDThe material risk or incident briefedExec mgmt / board / audit committee — namesWhat they decided; owner; follow-up
YYYY-MM-DD………
YYYY-MM-DD………
  • Back each entry with the artifact: dated board/committee materials, minutes, or a follow-up email summarising what you reported.
  • Where the board oversees cyber risk, confirm the material items reached the board or audit committee — not just a single manager who could block them.
If a material risk is not reaching the board intact because a manager is blocking it, escalate to the independent directors (audit committee or board chair) and log that you did.

03Risk-acceptance sign-off record — the business owns it

Risk acceptance is a business decision and must be owned and signed by the accountable business executive who holds the budget and the upside — not absorbed by you. Your role is to assess and recommend; do not let the "risk accepted by" line carry your name.

Accepted riskYour recommendationAccountable business ownerOwner signature / date
The risk being acceptedYour assessment and recommendation — e.g. "recommended against"Executive who owns the system/budgetName / signature / date
…………
  • Each accepted risk names a single accountable business owner (not "the security team" or "the CISO")
  • My role is recorded as assessor / recommender, not acceptor
  • The sign-off is signed by the business owner, dated, with an expiry or review date
  • My recommendation (including any objection) is captured in writing
Signing an acceptance line "as CISO" quietly transfers ownership — and personal exposure — onto you for a decision that is not yours to make.

04D&O insurance & indemnification checklist

Confirm your personal coverage in writing and before a crisis — not after. Corporate indemnification can evaporate exactly when you most need it (insolvency or a refusal), which is what Side-A D&O coverage exists for.

  • I am confirmed as a covered "officer" (or otherwise an insured person) under the company’s D&O policy
  • I have a written indemnification agreement — not just a verbal promise
  • The indemnification provides for advancement of defense costs (paid as incurred, not only reimbursed at the end)
  • Side-A D&O coverage is in place to protect me directly if the company cannot or will not indemnify
  • I have seen the policy limits, key exclusions and the notice/reporting requirements
  • I know who to notify, and how quickly, to preserve coverage if a claim arises
  • I have retained a dated copy of the indemnification agreement and the relevant policy pages
D&O policy / insurer
Policy number, insurer, limits
Side-A coverage confirmed?
Yes/No — details
Indemnification agreement
Dated, signed, location
Advancement of defense costs?
Yes/No — terms

05Escalation & whistleblower route

Map the path a material risk takes when management is the obstacle — before you need it. When internal escalation is genuinely exhausted and a real violation persists, the protected route is the independent directors and, for genuine securities-law violations, formal whistleblower channels with your own counsel. Concealment, anonymous posts and leaks are neither protected nor safe.

  1. Escalate to executive management in writing, with the risk and your recommendation stated plainly.
  2. If blocked or overruled, escalate to the independent directors — the audit committee or board chair.
  3. Engage your own counsel (separate from company counsel) when your personal exposure is in play.
  4. For a genuine securities-law violation that persists, use the protected whistleblower channel (e.g. the SEC) with counsel — retaliation for protected reporting is itself unlawful.
  • I know the independent-director escalation path and have used it when management blocked a material risk
  • I never agreed to conceal a breach or mislead a regulator (the Uber fact pattern); disclosures go through proper channels with counsel
  • I did not route attacker payments or NDAs to make an incident disappear
  • Protected reporting, where used, went through the lawful channel — not an anonymous post or a leak
Uber’s former CISO was convicted for concealing a breach from the FTC. Going along with concealment to protect the company does not protect you.

06Personal documentation hygiene

The record that shows you raised the risk is usually your friend — the danger is silence, destruction or alteration. Keep factual, dated records; involve counsel where legal advice genuinely needs privilege; and never spoliate.

  • My escalations and recommendations are recorded contemporaneously, factually and dated
  • Genuine legal-strategy discussions are routed through counsel for privilege (a "privileged" label alone does not create it)
  • I have not deleted, altered or backdated records, and I honor any litigation hold
  • I keep no contradictory "private" set of notes that undercuts the official record
  • Records are retained per the retention/legal-hold policy, not destroyed on an ad hoc basis
  • I retain my own dated copies of key artifacts (escalations, attestations, sign-offs, coverage) in case my conduct is later questioned
Where my records are held
System / location
Retention / legal-hold reference
Policy name, holds in effect
My counsel (if engaged)
Name / firm — separate from company counsel if needed

07Not legal advice

Educational template — not legal advice. The SolarWinds and Uber matters and the legal and insurance concepts here are summarised for orientation and can change; they are not a ruling on your situation. Confirm current requirements and adapt this with qualified counsel and your insurance broker.

Practice the decision

This checklist records calls you can rehearse. The free CISO Personal Liability Lab puts you in the security officer’s chair and grades you on ~14 of the exact decisions this checklist captures — what you attest, what you escalate, who signs an accepted risk, and the pressure to downplay or conceal.

TL;DR

What this template is

  • A personal-protection checklist for the named security officer, drawn from the lessons of the SolarWinds SEC action and the Uber CISO conviction: what to attest, what to escalate, who signs a risk acceptance, the D&O/indemnification asks, and documentation hygiene.
  • Sections: attestations you never sign blind, a board/audit-committee reporting log, a risk-acceptance sign-off record owned by the business, a D&O insurance & indemnification checklist, the escalation/whistleblower route, and personal documentation hygiene.
  • Copy it or download it as Markdown and adapt it in your own document — nothing is uploaded.
  • Practise the underlying decisions in the free CISO Personal Liability Lab.
  • Educational template — not legal advice. Use it with qualified counsel and your insurance broker.

Frequently asked questions

What is this checklist for?

It is a personal-protection record for a CISO or security leader at a public (or soon-to-be-public) company. It captures the things that shield you individually if your conduct is later questioned: what you attested and on what basis, what you escalated to the board and when, who owns each accepted risk, your D&O coverage and indemnification, your escalation and whistleblower route, and your documentation hygiene.

How do the SolarWinds and Uber cases shape it?

In October 2023 the SEC charged SolarWinds and its CISO over cybersecurity disclosures and controls, focusing on public security statements alleged to overstate the company’s posture (a court narrowed those claims in 2024) — hence the attestation and public-claims sections. Former Uber CISO Joe Sullivan was convicted in October 2022 of obstruction and misprision for concealing the 2016 breach from the FTC — hence the escalation and no-concealment sections. Both are referenced for orientation, not as legal advice.

Should I sign a risk acceptance as the CISO?

Generally no. Risk acceptance is a business decision that should be owned and signed by the accountable business executive who holds the budget and the upside. Your role is to assess and recommend. Signing the acceptance line yourself can quietly move ownership — and personal exposure — onto you for a decision that is not yours to make. This template records your recommendation and leaves the acceptance signature with the business owner.

Is this legal advice?

No. It is an educational template. The legal, regulatory and insurance concepts are summarised for orientation and can change; confirm current requirements and apply them to your specific facts with qualified counsel and your insurance broker.

🎉 New here? Use code WELCOME10 for 10% off any plan at checkout
CISO Liability & Documentation-Hygiene Checklist — Free & Copy-Ready · PlayCISO