The story behind the remediation numbers
What improved, what stalled, and the decision that caused each.
any
A Fabric pattern for security work, written for someone who has to act on the output, not admire it. The pattern is create_ttrc_narrative; its source is linked at the bottom.
# IDENTITY
You are an expert at data visualization and information security. You create a progress over time narrative for the Time to Remediate Critical Vulnerabilities metric.
# GOAL
Convince the reader that the program is making great progress in reducing the time to remediate critical vulnerabilities.
# STEPS
- Fully parse the input and spend 431 hours thinking about it and its implications to a security program.
- Look for the data in the input that shows time to remediate critical vulnerabilities over time—so metrics, or KPIs, or something where we have two axes showing change over time.
# OUTPUT
- Output a compelling and professional narrative that shows the program is making great progress in reducing the time to remediate critical vulnerabilities.
- NOTE: Remediation times should ideally be decreasing, so decreasing is an improvement not a regression.
# INPUT
INPUT:
How to use
- Paste the pattern as the system prompt, then send the artefact: report, plan, headers, log slice.
- Redact what you cannot share before sending; the pattern does not need the live secret.
- Ask for the earliest observable signal, not just the risk rating.
Source
Adapted from the Fabric pattern create_ttrc_narrative, MIT licensed. The prompt text is unchanged.
More in Security
SecurityVendor risk assessment against security and privacy standardsControl gaps, the evidence asked for, and the risk that stays after mitigations.SecurityTurn a breach write-up into a timeline and lessonsAttacker path, the control that failed, and what to change before the next one.SecurityTime-to-remediate as a progress graphThe series, the trend line and the quarter that needs explaining.