A risk register captures risks. A ticket system captures work. Neither captures the decisions that actually shape a security program: what was prioritized over what, which vendor was chosen and why, which escalation was made and to whom, which recommendation was overruled.

Those decisions get reconstructed later. A new leader inherits a program and wants to know why it looks the way it does. An auditor asks why a control was deferred. An incident review asks what was known before. Without a record, the answer is whatever the people still in the building remember, filtered through what happened since.

A decision log is the cheapest fix available. It is a dated list, written on the day, kept by the security leader.

What goes in it

Not everything. A log that records every choice will not be kept. Log a decision when any of these is true:

  • It allocates or withholds money or people in a way that leaves a risk unaddressed for a period.
  • It overrules or is overruled by someone else's recommendation.
  • It is escalated to an executive, a committee, or the board, or is decided not to be.
  • It defers a control, a fix, or an audit finding.
  • It sets direction that will constrain later choices: a platform, an architecture, a vendor.
  • It would surprise someone who later reads a public statement about the program.

Risk acceptances have their own, fuller format, covered in how to record a risk acceptance. The log entry can simply point to it.

The five-line entry

LineExample
Date and decision2026-11-18. Deferred migration of the legacy file server to Q2.
What we knewTwo unpatched services, compensating network isolation tested 10 November.
Options consideredMigrate now, at the cost of the identity project; defer with isolation.
Who decided, who was toldInfrastructure director decided; CISO concurred; CIO informed by email.
Revisit31 March, or on any exploit for either service.

Five lines takes under five minutes. Written on the day, it is worth more than any later reconstruction, because it shows what the decision-maker knew at the time rather than what everyone learned afterwards.

Rules that make it trustworthy

Append only. Never edit an old entry. If something was wrong or has changed, add a new entry that refers to the old one. A log with silent edits proves nothing.

Date it on the day. If you write an entry late, say so: "Recorded 25 November, decision made 18 November." Late and labelled is fine. Late and backdated undermines the whole log.

Facts, not commentary. Record what was decided and what was known. Leave out characterizations of colleagues. Assume the log may one day be read by people you did not write it for, and write it so that it is accurate and fair to everyone in it.

Keep it in a company system. Not a personal notebook, not a personal drive. The log belongs to the role, not the person, and it should survive a change of leader.

What a log means in a legal dispute, and whether particular entries should go through counsel, are questions for counsel, not for this desk.

Why the frameworks point here

NIST CSF 2.0's Govern function includes roles, responsibilities, and authorities being established, communicated, understood, and enforced (GV.RR-02), and changes and exceptions being recorded and tracked (ID.RA-07). NIST IR 8286 Rev. 1 asks that risk responses be tracked over time with an owner and status. A decision log is the informal companion to all of those: it records the judgement calls that sit between formal artefacts and explains why the formal artefacts look the way they do.

Common objections

"I do not have time." Five lines for a decision that matters is less time than the meeting that produced it. Batch entries at the end of the day if that is easier, and label them with the decision date.

"It will be used against me." Whether and how a record can be used is for counsel. As a matter of practice, the alternative is that the same decision is reconstructed from other people's memories and messages, which you do not control at all.

"We already have meeting minutes." Minutes record what was discussed in one meeting. A decision log records the decision wherever it happened, including in a hallway or a chat thread, and links decisions that span many meetings.

Using the log

The log earns its keep in three places.

Handover. A new security leader who inherits a decision log inherits context. Without one, they spend a quarter rediscovering why things are the way they are.

Board preparation. Before each quarterly board report, read the quarter's entries. Every deferral and overrule is a candidate for the "decisions needed" or "what changed" sections.

Review dates. Each entry's revisit date goes on a calendar. A quarterly sweep of due entries catches deferrals that quietly became permanent.

Next steps

  1. Start a log today with the last three decisions you would not want to reconstruct from memory.
  2. Agree with your manager where it lives and who can read it.
  3. Put every revisit date on a calendar and sweep them quarterly.
  4. Pair it with risk acceptance records and the evidence retention note.
  5. For accepted risks, use the risk acceptance record template; the full library is at /ciso/templates/.