The board brief by noon has five lines, a stated next update time and a rule for when the advisory lands late
The brief template
Directors have two minutes. Write one sentence per line, in this order. Copy the form and fill every field; write "unknown, answer by HH:MM" where a field is not yet known.
The brief is due at 12:00 in the time zone the board meets in, written in the subject line; every time in the brief uses that zone. Which day depends on when the advisory is public. If it is public before 10:00 that day, the full brief is due at noon the same day. From 10:00 on, fewer than two hours remain, so the advisory counts as late: send the interim note within two hours of the advisory and the full brief at noon the next day.
- Subject: [Product] flaw [CVE], brief [n], [date and time, time zone].
- 1. Affected: [product and versions] on [number] systems, of which [number] are reachable from the internet or partner networks.
- 2. Exploitation: [confirmed on our systems, confirmed in the wild, or not known], per [named source], dated [date]. Compromise assessment: [open until HH:MM, or closed with the finding].
- 3. Done: [controls applied] on [number] of [number] systems at [HH:MM]; patched [number] of [number].
- 4. Open: [number] systems not yet fixed, owner [role], fix by [date and time].
- 5. Next update: [HH:MM, time zone].
- Decisions needed: [authority for an outage window, a risk acceptance with an expiry date, spend, or none].
The interim note template
When the advisory is late, as defined above, the interim note keeps the same five lines with unknowns marked and goes out within two hours of the advisory. Use it for the hours before the first full brief:
- Subject: [Product] flaw [CVE], interim note, [date and time].
- 1. Affected: scoping under way; asset list due [HH:MM].
- 2. Exploitation: [vendor or CISA statement and date, or not known].
- 3. Done: [first control, or none yet; first control due HH:MM].
- 4. Open: everything in scope until the list exists.
- 5. Next update: the full brief by noon on [date].
A filled brief: Cisco ISE, CVE-2026-76460
Cisco published advisory cisco-sa-ISE-ABP-VNSW7Tn5 on 16 Sep 2026 at 16:00 GMT. The facts that fill the brief come from the advisory, NVD and CISA. Fields marked in square brackets are counts only your inventory can supply, and no public record can fill them.
Because 16:00 GMT is after the 10:00 cut-off, the rule above applies to a board that meets in GMT: send the interim note by 18:00 GMT on 16 Sep and the full brief by noon on 17 Sep. The interim note comes first below, then the noon brief.
- Interim note, 16 Sep 2026:
- Subject: Cisco ISE flaw CVE-2026-76460, interim note, 16 Sep 2026, 18:00 GMT.
- 1. Affected: scoping under way; Cisco says ISE and ISE-PIC are affected regardless of configuration; node list due 20:00 GMT.
- 2. Exploitation: Cisco states its PSIRT is aware of active exploitation; CISA added the bug to its catalog on 16 Sep 2026.
- 3. Done: nothing yet; Cisco lists no workaround, and the first control, infrastructure access lists on the nodes, is due 22:00 GMT.
- 4. Open: every ISE node until the list exists.
- 5. Next update: the full brief by noon on 17 Sep 2026.
- Noon brief, 17 Sep 2026:
- Subject: Cisco ISE flaw CVE-2026-76460, brief 1, 17 Sep 2026, 12:00 GMT.
- 1. Affected: Cisco ISE and ISE-PIC on every release below 3.1 Patch 12, 3.2 Patch 11, 3.3 Patch 12, 3.4 Patch 7 or 3.5 Patch 4, regardless of configuration, on [number] nodes, [number] reachable from partner networks; and ISE 3.0, which is end of software maintenance and has no fix, on [number] nodes.
- 2. Exploitation: confirmed in the wild. Cisco states its PSIRT is aware of active exploitation and gives no start date. CISA added the bug to its catalog on 16 Sep 2026. Compromise assessment of the [number] nodes: open until [HH:MM]; Cisco's check is the ise-kong access log on every node.
- 3. Done: Cisco has no workaround, so the control is infrastructure access lists that allow only required management and control plane traffic; applied on [number] of [number] nodes at [HH:MM]. Patched: [number] of [number].
- 4. Open: [number] nodes not yet patched, owner [role], fix by [date and time]. CISA's due date for federal agencies is 19 Sep 2026, three days after the advisory.
- 5. Next update: [HH:MM] GMT on 17 Sep 2026.
- Decisions needed: authority to re-image any node the assessment flags, which Cisco strongly recommends if compromise is suspected; approval of the access-list change that cuts off any admin station or integration not on the list; and a migration date for each ISE 3.0 node, because Cisco advises moving to a supported release that includes the fix, with the access lists as the stopgap until then.
Say what is unknown, and ask for decisions
Directors accept uncertainty when it is labeled and dated. They do not accept a surprise. Do not write that there is no impact until the assessment has closed; write "no evidence found as of HH:MM in [the sources checked]; assessment open". BeyondTrust's CVE-2026-102764 shows why: exploitation began on 29 Aug 2026 and the advisory came on 15 Oct 2026, so a brief based on the advisory alone would have missed 47 days.
End with the decisions you need, or the word none. A brief that asks for nothing and names the next update time lets the board stop thinking about it until then. Keep CVSS out unless a director asks; exposure and exploitation matter more to the decision.
Who supplies each line, who approves it, and how the brief fails
The security lead drafts, using the scribe's decision log. The executive approver reads and releases it; the communications lead checks line 4 against the notification duties with legal. The sent brief is filed in the event's decision log with its send time, so brief 2 can be compared with brief 1.
Scroll the table sideways for more columns
| Line | Supplied by | Source of the number | How it typically fails, and the fix |
|---|---|---|---|
| 1. Affected | Platform lead | Inventory export, with its time | A stale count: the inventory was last refreshed days ago. Print "as of HH:MM" beside every count and recount before sending |
| 2. Exploitation | Event lead | Vendor advisory and CISA catalog, with the date of each; assessment result from the SOC lead | Premature "no impact". Keep the wording above until the assessment closes |
| 3. Done | Platform lead | Verification output from the hosts, not the change ticket | The control is reported as applied when it was only requested. Count only hosts where the check in the mitigation guide passed |
| 4. Open | Named owner of each open system | Decision log entry with the fix-by time | A missing owner: the line names a team, so nobody answers the director. Name a person, or do not send |
| 5. Next update | Event lead | The update interval in the plan | The time is missed and nobody says so. If the update cannot be ready, send a one-line note before the stated time with a new time |
| Decisions needed | Executive approver, asked by the event lead | The authority table in the response plan | The question is buried in line 3. Keep it as its own line, with the expiry of any acceptance |
Brief 2 when compromise is found on your own systems
The five lines stay, but the meaning of three of them changes, and the hand-over to the incident response plan is itself an item in the brief.
- Subject: [Product] flaw [CVE], brief [n], compromise confirmed, [date and time, time zone].
- 1. Affected: [number] systems with evidence of compromise, first evidence at [time] in [named log]; [number] more in scope and not yet assessed.
- 2. Exploitation: confirmed on our systems. Evidence preserved before any patch or re-image: yes or no, by [role]. The incident response plan took over at [HH:MM], incident lead [name].
- 3. Done: [number] systems isolated, [number] credentials and tokens reset, [number] systems rebuilt; mitigation and patch status as in brief 1.
- 4. Open: assessment of the remaining [number] systems, owner [role], done by [date and time]. Notification duties: awareness recorded at [HH:MM]; each applicable clock and its deadline, from the table below, with the owner of the decision to notify.
- 5. Next update: [HH:MM, time zone], at shorter intervals than before.
- Decisions needed: authority to rebuild, to notify regulators or customers, and to take the service offline.
Notification clocks that may start the day the brief is written
These apply only if their trigger is met. Put the one that applies, with its deadline, in line 4 of the brief.
Scroll the table sideways for more columns
| Rule | Trigger | Deadline | Source |
|---|---|---|---|
| GDPR Article 33 | A personal data breach, unless unlikely to risk people's rights and freedoms | "without undue delay and, where feasible, not later than 72 hours after having become aware of it"; delay needs reasons | gdpr-info.eu, Art. 33 |
| NIS2 Directive (EU) 2022/2555 | A significant incident at an essential or important entity | Early warning without undue delay and within 24 hours; incident notification within 72 hours of becoming aware | EUR-Lex, Directive (EU) 2022/2555 |
| SEC Form 8-K Item 1.05 | A US-listed registrant determines that a cybersecurity incident is material | "generally" due "four business days after a registrant determines" that; the clock runs from the determination, not from discovery | SEC press release 2023-139 |
The record behind the brief
If a director or auditor asks how you knew, the decision log answers: the advisory link and read time, each decision with its approver and time, the verification result, and each brief as sent. NIST SP 800-61r3 calls incident response "a critical part of cybersecurity risk management that should be integrated across organizational operations", which is where the brief lands. Have an executive read the draft aloud once before it goes out. A brief that reads badly aloud is usually missing a number or an owner.
Related pages
Sources
- Cisco Security Advisory cisco-sa-ISE-ABP-VNSW7Tn5, read 19 Nov 2026
- CISA Known Exploited Vulnerabilities catalog entry for CVE-2026-76460, read 19 Nov 2026
- NVD record for CVE-2026-76460, read 19 Nov 2026
- BeyondTrust blog on BT26-05, read 19 Nov 2026
- GDPR Article 33, read 19 Nov 2026
- Directive (EU) 2022/2555 (NIS2), read 19 Nov 2026
- NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cyber Risk Management, read 19 Nov 2026
- SEC press release 2023-139, cybersecurity risk management and incident disclosure rules, read 19 Nov 2026
Last reviewed 19 Nov 2026.