PIVOT Libraries
Three libraries feed the module, accessible from its menu.
| Library | Content |
|---|---|
| A — Vulnerability reference | Shared vulnerability reference |
| B — ABE Vulnerabilities | Vulnerabilities, actions and compromise states specific to the engine |
| C — Action sequences | Standard action sequences |
Reference library — ABE Vulnerabilities
This is the structuring library: it describes what the attacker can do and what they obtain.
| Tab | Content |
|---|---|
| Vulnerabilities | Sheets with scope (Specific / Generic), measures, concerned supporting assets, allowed actions |
| SA Coverage | Cross-reference of PIVOT rules × supporting assets |
| Coverage gaps | Supporting assets or rules without a link |
| Actions | Applicable actions and their state after execution |
| Compromise states | States reachable and actions they unlock |
Vulnerabilities, actions, states
The engine does not reason about isolated vulnerabilities but about a chain: a vulnerability enables actions, each action produces a compromise state, and each state unlocks new actions. This is the cycle that builds the attack graph.
Checking coverage
The SA Coverage and Coverage gaps tabs answer a precise question: is every supporting asset linked to at least one PIVOT rule?
Two link qualities are distinguished: ✓ Confirmed and ~ Suggested. The Gaps only filter isolates supporting assets with no link at all.
A coverage gap is a blind spot
A supporting asset with no rule attached will not appear in any generated attack path. The absence of a scenario on this component does not then mean it is safe, but that the engine had nothing to say about it.
Library family
PIVOT libraries form their own family, savable as a pack — see Library packs.