Summary
What happened, affected scope, and current status.
Cyber technical writing
Write work people can trust.
Good cybersecurity work is not just finding an issue. It is explaining what happened, what evidence supports it, why it matters, what remains uncertain, and what should happen next.
Report structure
A reader should not need you beside them.
The same structure improves incident reports, vulnerability findings, evidence notes, portfolio writeups, interview stories, and résumé bullets.
Evidence
Sources, timestamps, assets, and confidence.
Analysis
Meaning, ruled-out paths, assumptions, and gaps.
Recommendation
Specific next actions and validation evidence.
Weak record
“It was suspicious.”
No source, scope, timeline, confidence, or next step. The reader cannot inspect the conclusion.
Defensible record
Show the pattern and its limit.
Five failed attempts from one source were followed by a successful login. The events are confirmed; user recognition and source ownership still require validation.
Start writing
Open starter kitUse the free editable kit.
Build an incident report, vulnerability summary, evidence note, portfolio plan, and evidence-backed résumé bullet.