Skip to content

2 · Reading and writing intelligence

Time: 2–3 weeks, then keep practising every week

Writing is the product of CTI. A finding nobody understands, or nobody can act on, is wasted work. This step comes early on purpose: every project after this one ends with something you write.

Threat Landscape Reports (TLRs)Just Hacking Training · Jennifer Funk

A short free challenge from a CTI operations manager: start from business needs, structure a report that informs leadership decisions, and build one for a fictional company.

Free
Want more? (optional)

Your most common outputs are short advisories on a new campaign or vulnerability, weekly summaries for management, and reports for clients. They are often written under time pressure, which is exactly why BLUF and clear confidence statements matter: the reader decides from the first paragraph.

Most of your input will be other people’s reports. For each one, ask:

  • What did they observe, and what do they assess?
  • What is the evidence behind the attribution?
  • How old is the data, and who was the audience?
  • What does it mean for my organisation or client?

Practise on real reports. APTnotes collects public APT reports going back years.

  • BLUF (Bottom Line Up Front): the conclusion and what the reader should do come first.
  • Estimative language: words like likely and almost certainly with agreed meanings, plus a stated confidence level.
  • Audience: an executive brief, a SOC alert and a technical report are three different documents.
  • Facts vs assessments: always visible to the reader.

Take one long vendor report and write two things from it: a one-page brief for a manager (BLUF, what it means, what to do) and a short technical note for a SOC team (TTPs, indicators, detection ideas). Keep both honest about confidence.

  • You can summarise any report in three sentences without losing the key judgment.
  • Your writing separates facts from assessments and states confidence.