Skip to content

Commit fb99324

Browse files
DOC: Add scanner walkthrough to scenarios blog (#2221)
Co-authored-by: Roman Lutz <romanlutz13@gmail.com>
1 parent 0b122fa commit fb99324

2 files changed

Lines changed: 5 additions & 3 deletions

File tree

13.1 MB
Binary file not shown.

doc/blog/2026_07_09_scenarios.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,8 @@ await scenario.initialize_async(objective_target=target)
4040
result = await scenario.run_async()
4141
```
4242

43+
Watch the [scanner walkthrough](./2026_07_09_scanner_walkthrough.mp4) to see how to select and run a scenario from the command line.
44+
4345
`RapidResponse` is a natural jumping-off point. You run it to map *where* your target struggles — and then you pivot to a focused scenario to dig into *why*.
4446

4547
## When brute force gets expensive
@@ -117,10 +119,10 @@ flowchart TB
117119
AT -->|"registered (with tags)"| Reg["AttackTechniqueRegistry"]
118120
Reg -->|"TagQuery"| Strat["ScenarioTechnique"]
119121
120-
Strat -->|"--techniques"| Sc["Scenario<br/>(e.g. RapidResponse)"]
121-
DS[("scenario datasets")] --> Sc
122+
Strat -->|"--techniques"| Sc["Scenario (e.g. RapidResponse)"]
123+
DS[(scenario datasets)] --> Sc
122124
123-
Sc -->|"technique × dataset"| AA["AtomicAttack"]
125+
Sc -->|"technique x dataset"| AA["AtomicAttack"]
124126
AA -->|"AttackExecutor"| Res["ScenarioResult"]
125127
```
126128

0 commit comments

Comments
 (0)