[LESSON] 03.3 Threat-Informed Requirements #30

Lesson

Module: 03 Detection Requirements

Lesson: 3. Threat-Informed Requirements

Target file: core/03-detection-requirements/03-threat-informed-requirements.md

Research issue: #12

Scope

Copied from the module README, which is the source of truth. If the scope needs to change while writing, change the README in the same pull request and say why.

Learning Objectives

• Build a detection threat model.
• Translate threat scenarios into expected behaviors and required telemetry.
• Use ATT&CK to provide structure and find gaps without using it as a checklist.
• Derive requirements from a threat model.

Key Topics

• Why "detect everything" fails
• Threat modeling for detection
• Who attacks, what they want, how they get in, what they do next, and what they leave behind
• Threats to behaviors to telemetry to gaps to requirements
• ATT&CK as a tool
• Living threat models

Out of Scope

• Asset and exposure context (Lesson 4)
• Coverage analysis of existing detections (Module 04)
• Researching a behavior in depth (Module 04)

Goal of This Issue

Write the lesson. The lesson is complete when a pull request is merged that:

• adds the target file, based on templates/lesson-template.md and written to the Style Guide
• meets each learning objective above and stays out of the out-of-scope topics, pointing to the lesson or module that covers them instead
• passes the checklist for authors
• links the lesson from the module README's lesson list
• updates the module's ai_assistance field and README AI Assistance section to cover this lesson

The module's status stays draft. Technical review happens at the module level once its lessons are written (Review Process).

How to Participate

• Claim: comment on this issue to take it. A maintainer will assign you and add you to the Contributors section below. One writer leads each lesson; others are welcome to contribute.
• Collaborate: open a draft pull request early and link this issue. To let co-contributors push to your branch, add them as collaborators on your fork (fork Settings → Collaborators). Every commit must be signed off (DCO).
• Boundaries: if the lesson starts covering material owned by another lesson or module, raise it here or in the pull request rather than expanding the scope.
• Inactivity: claims with no activity for 4 weeks may be released after a reminder.

Contributors

Writer:

Contributors:

Additional Context

None yet.