board-report
/board-report
Zamienia surowe dane bezpieczeństwa w zwięzły raport dla zarządu lub komitetu audytu, opisany językiem biznesu.
- Autor
- Cyhelm-Vciso ↗
- Repozytorium
- ciso-toolkit ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 05.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 05.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zamienia surowe dane bezpieczeństwa w zwięzły raport dla zarządu lub komitetu audytu, opisany językiem biznesu.
Wyzwalacze z opisu
Oryginalny opis (EN)
Turn raw security data (metrics, incident notes, project status, audit findings, spreadsheets) into a concise board, audit-committee or executive security report written in business language. Use when the user asks for a board report, CISO update, quarterly security report, exec summary of security posture, cyber risk briefing, or wants to "explain security to the board".
Jak działa
- 1. Establish the brief (ask only what is missing)
- 2. Process the inputs
- 3. Write the report
- Writing rules
- 4. Quality check before returning
Podgląd SKILL.md
--- name: board-report description: Turn raw security data (metrics, incident notes, project status, audit findings, spreadsheets) into a concise board, audit-committee or executive security report written in business language. Use when the user asks for a board report, CISO update, quarterly security report, exec summary of security posture, cyber risk briefing, or wants to "explain security to the board". --- # Board Report Produce a security report that a non-technical board can read in five minutes and act on. The output is judged on one question: **does a director know what is at risk, whether it is getting better or worse, and what decision is being asked of them?** ## 1. Establish the brief (ask only what is missing) Infer from what the user has already provided; ask in a single message only for gaps that change the output: - **Audience**: full board, audit/risk committee, or executive team (committees tolerate more detail). - **Period**: quarter / month and the previous period for trend comparison. - **Organisation context**: industry, size, regulators, risk appetite statement if one exists. - **Format**: memo (default), slide outline, or both. Length cap (default: 2 pages memo / 6 slides). - **The ask**: is there a decision, budget, or risk acceptance the CISO needs? If unknown, ask — every board report should have one or explicitly say "no decision required this period". If the user gives no data at all, offer to produce a template with clearly marked `[PLACEHOLDER]` values rather than inventing numbers. ## 2. Process the inputs 1. Read every provided file. Normalise metrics into a table: metric, current value, previous value, target, source. 2. Select **at most 5 headline indicators**. Prefer Key Risk Indicators tied to business impact over activity counts. Use `references/metrics-catalog.md` to pick and define them. 3. Translate each technical item into business impact: revenue, operations downtime, regulatory exposure, customer trust, or strategic delivery. Use the phrasing pattern: *"Because <condition>, we are exposed to <business consequence>; we are <action> by <date>."* 4. Determine trend (▲ improving, ▼ worsening, ► stable) against the previous period. Never show a trend you cannot support with two data points — write "baseline" instead. 5. Assign RAG status using explicit criteria stated in the report (e.g. Green = at/better than target; Amber = within 10% of target or on a recovery plan; Red = off target with no funded plan). 6. Identify the top 3–5 risks, their movement, and whether each is within risk appetite. ## 3. Write the report Use `references/board-memo-template.md`. Mandatory sections, in this order: 1. **Bottom line up front** — three sentences: overall posture, biggest change since last period, the ask. 2. **Decisions / asks** — numbered, each with cost, deadline and consequence of not deciding. 3. **Headline indicators** — table with value, target, trend, RAG. 4. **Top risks** — risk, business impact, trend, within appetite (Y/N), owner, next milestone. 5. **Notable events** — incidents, audit results, regulatory changes; one line each, impact-first. 6. **Programme progress** — major initiatives, % complete, on track / at risk. 7. **Appendix** (optional) — definitions of metrics and RAG criteria. ## Writing rules - No unexplained acronyms. "EDR" becomes "endpoint protection software". CVE IDs never appear in the body. - Numbers over adjectives: "patched 94% of critical vulnerabilities within 14 days (target 95%)", not "patching is strong". - Lead with impact, not activity. Boards do not care that 4,000 phishing emails were blocked; they care whether staff are being compromised and what it costs. - Be candid about bad news. Put it early, with a plan. Never soften a Red into an Amber. - Each paragraph ≤ 3 sentences. Use tables for anything comparative. - Mark every figure supplied by the user vs. any you estimated. **Never invent data**; use `[DATA NEEDED: …]` instead. ## 4. Quality check before returning - [ ] A director could answer: what is at risk, better or worse, what must we decide? - [ ] ≤ 5 headline indicators, each with target and trend. - [ ] Every Red item has an owner and a date. - [ ] No jargon, no unsupported numbers, no fabricated incidents. - [ ] Length within the agreed cap. End by listing any data gaps the CISO should fill before sending, and offer a slide-outline version if only a memo was produced (or vice versa).
Pliki w paczce (3)
- SKILL.md 4 KB
- references/board-memo-template.md 2 KB
- references/metrics-catalog.md 3 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · Cyhelm-Vciso/ciso-toolkit | 90 | MIT |
| apache/incubator | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki 236692be2fec (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100cyber-impact-statement
Generuje zwięzłe oświadczenia o wpływie na poziomie CISO dla awarii kontroli bezpieczeństwa, tłumacząc podatność techniczną na język biznesowy dla zarządu. - 90chief-information-security-officer
Wspiera szefa bezpieczeństwa IT w strategii programu, raportach dla zarządu, apetycie na ryzyko i eskalacji incydentów. - 100committee-report
Zamienia rejestr ryzyk w raport dla komitetu lub zarządu, z mapą ryzyk, ryzykami ponad apetytem i decyzjami do podjęcia. - 90board-deck
Przygotowuje prezentację o bezpieczeństwie dla zarządu: ryzyka w języku biznesu, postęp programu i inwestycje powiązane z ryzykiem. - 90ciso-advisor
Działa jak doświadczony CISO: doradza w decyzjach o ryzyku cyber, raportowaniu do zarządu, strategii bezpieczeństwa, NIS2, DORA i RODO. - 100vciso
Pełni rolę wirtualnego CISO dla organizacji bez etatowego CISO: ocenia program bezpieczeństwa, gotowość do zgodności, zarządza ryzykiem i przygotowuje raporty dla zarządu.