Components
Build reusable model pieces once and link them into many scenarios.
Last updated
Build reusable model pieces once and link them into many scenarios.
A component is a reusable piece of a FAIR model: a threat event frequency you have researched, a standard loss table, a vulnerability estimate for a shared control environment. Define it once, link it into any number of scenarios, and update it in one place.
A component can stand in for any slot in the taxonomy:
Loss Event Frequency
Threat Event Frequency
Vulnerability
Loss Magnitude
Loss Amount
Secondary Risk
Leaf estimates: Frequency, Probability, Magnitude, Capability
Workspace
Available only inside the current workspace.
Global
Shared across all workspaces on this machine.
Both are managed on the Components page, with folders, search, tags, and the same organize/duplicate/rename/delete actions as scenarios.
In the scenario editor, a factor slot can reference a component instead of holding inline values. The link is live: when you edit the component, every scenario using it picks up the change on its next simulation.
Because links are live, editing a widely used component changes the results of every scenario that references it. Check where a component is used before making material changes, or duplicate it and edit the copy.
Individual components, component folders, or the whole library can be exported to a .cqx bundle and imported elsewhere, for example to share a calibrated threat library with a colleague. See Import, export and backup.
Last updated