IdeaIntake, Hypothesis, Research
Build a baseline
Say what you run and what you collect, and get a first set of detections your telemetry can support: the library's best rule for each technique that is ready to build, in your SIEM's language, in the scorer's order, with the log source silence alert first.
The method behind it First steps, 4.1 Build a baseline
On this page
What does the environment look like?
Each answer sets the platforms in scope and ticks the log sources that environment usually has. Untick what you do not collect in step 4.
Which operating systems do you run?
Host sources, and whether Sysmon is on the Windows fleet, which changes what the endpoint analytics can see.
Which tools and vendors send logs?
A vendor stands for the ATT&CK log sources it emits. Ticking one ticks those sources; the names are ATT&CK's, and some vendors fill several. Cloud platforms and office suites are in step 1.
Which log sources do you collect?
The list the other three questions filled in, out of the log sources ATT&CK's analytics name. This is the list that decides the baseline. Tick and untick freely.
In the coverage map, choose Import, then Merge a teammate's backup, and pick the file. It adds the sources, the platforms, and the baseline's rules as building, and keeps what is already there.
The baseline
Blind spots in this environment
Techniques in scope with no analytic that your sources complete, the ones the most ATT&CK groups use first, and the single log source that would make the most of them ready.
The defaults behind the scores
Rendered from framework.json v0.136.0, CC BY-NC 4.0. Readiness follows the coverage map's rules over ATT&CK Enterprise 20.1; the candidates come from the detection library, each under its own license. Nothing you tick leaves this page.