Let's talk

FTA/FMEA Calibration Process

Calibration deep-dive: how evidence becomes defensible quantification Use this as a slide-in panel or a breakout section; it explains “what changes” and “why the math is credible.” Evidence layer Vulnerability CVSS + KEV + EPSS, patch state, compensating controls Monitoring OT network telemetry, EDR, auth events, config integrity signals Control assurance Control coverage + health (tests, audits, drift) mapped to vectors Engineering context System criticality, defensive level, mission phase / operational mode Calibration detects “dead branches” Suppressing gates, missing prerequisites, AND chains that force zero → fix logic or populate prerequisites with evidence-backed events Outputs become auditable Every Input1–3 value is traceable to source IDs and refresh rules Calibration transforms Input mapping (Relyence) Input1 = exposure (CVSS/10 or vector weight) Input2 = mitigation factor (patch + control coverage) Input3 = posture factor (defensive level / criticality) Structural fixes Correct OR/AND where justified; replace placeholders with basic events Model barriers explicitly (attack attempt AND control fails) Dependency & correlation CCF groups for shared services (IdP/jump host); disjoint sets for overlaps Correlated posture sweeps to show best/worst credible bounds Sensitivity outputs FV importance (drivers), dominant paths/cut sets, tornado deltas “What to fix first” mapped to owners + verification steps Supports INSPECT vs ENGINEERING narrative modes Quality gates Stop if: dead branches, untraceable inputs, or inconsistent refresh cadence Packages Engineering leads Top drivers + dominant paths Mitigation levers (segmentation, hardening) Verification plan & proof points Cyber program Patch/mitigation priorities tied to consequence Control coverage gaps + monitoring actions Refresh + governance cadence Operations Mode-specific risk (maintenance vs normal ops) Runbook linkages & exception handling Alarm/ESD integrity focus Exec / inspection One-page findings + tornado table Evidence binder summary Change log: what changed & why Recommended UX Main-page summary + slide-in deep dive Implementation note: keep SVG WordPress-safe (no <script>, no external images). Use data-* hooks for tooltips, sequencing, and mode toggles handled by your page JS.