Calibration workshop
Turn benchmark magnitudes into this institution's own figures, and link certificates to the services they actually carry.
Purpose
A bootstrapped tenant carries a benchmark loss model: representative magnitudes from the sector pack, each labelled and each carrying its source. The workshop replaces them with the customer's own numbers, records why, and links certificates to business services so a certificate finding can read as business impact.
Steps
1. Read the board's view first. Board › Scenarios shows the pack state in its header, and every uncalibrated row carries the chip Benchmark template — calibrate to your estate.
2. Calibrate each scenario. On Console › Analyst Console, under Board Scenarios, each row is an editable card with its criticality badge. Change the magnitudes, the window, the technical-fix state, the criticality and the board narrative.
Why these figures is mandatory the moment a money figure moves. The card blocks with a board magnitude cannot change without its source, and if the note still explains the old figure it says so: The figure is changing — update the note to explain the new number. The note is stamped on the row and printed beside the figure wherever it is reported. Press Calibrate. The footer then reads Last calibrated by … at ….
3. Components. Architecture components on the same page takes the migration state per component: Status, PQC ready %, Owner, Milestones complete / Milestones total, Board narrative. Press Assess.
4. Data classes. Inventory › Data captures the records that make harvest-now-decrypt-later real: Record class, Sensitivity, Retention (years), Protecting algorithm, Residency, Owner. Retention is the Y term in Mosca's inequality, so a class with no retention produces no HNDL figure.
5. Service map. The sheet that says which business service each host belongs to — see the contract below.
6. Check the translation. Board › Quantified Impact states, while the pack is still uncalibrated: The loss basis is still the uncalibrated benchmark scenario pack — representative magnitudes, not measured from this organisation. Calibrate the scenarios on the Analyst Console before quoting any figure here. That note disappearing is the workshop's exit test.
The service map sheet
One row per system. Columns are resolved by alias against the normalised header, so Business_Unit, business unit and BUSINESS UNIT are one column:
| Field | Accepted headers |
|---|---|
| host | host, hostname, fqdn, cn, common name, certificate, subject, system |
| service | business service, service, application, system name |
| owner | owner, service owner |
| business unit | business unit, bu, department, division |
| business process | business process, process |
| criticality | criticality, tier (1–5) |
Matching is exact only, in strict order: exact host → exact SAN → one-label wildcard, and the wildcard applies only when the cell itself was written *.domain, only one label below it. There is no fuzzy, prefix or substring matching: vpn and vpn-gw are different machines.
On the Load service map card, press Preview matches first. The preview reports matched and unmatched counts, match rate n%, and what it would write — Nothing is written until you load it. Unmatched rows are listed with Row · Host · Why not matched. A business process that is not in this tenant's sector pack is listed and the service loads with no process attached, never a guessed one. Then press Load service map.
Loading requires owner, admin or analyst; an assessor sees the preview and a line saying why the load button is not theirs.
Provenance
| Figure | Tier |
|---|---|
| A seeded, untouched scenario magnitude | benchmark, chipped on every surface that shows it |
| A calibrated magnitude | typed, with the analyst, the timestamp and the note |
| Component PQC ready %, milestones, owner | typed |
| Data-class retention, sensitivity, residency | typed |
| Certificate-to-service links and the blast radius they produce | live — the certificates are measured; the sheet is the customer's own record |
| A certificate with no service | counted under Unmapped, never attributed |
Common failures
- A magnitude changed with no note. The button stays disabled. That is the design, not a bug.
- Currency mismatch. Seeded rows are not converted into the reporting currency. Calibrate them before board use; the onboarding form warns about this.
- Low match rate. Do not hand-map hosts during the meeting. Fix the host column in the sheet, or file the certificate first — import it, or run a real scan, which files its hosts in the estate on completion. A rehearsal scan never does.
- A process name the pack does not know. The preview names the ones the tenant accepts. If the sector was never set, no process cell can be accepted at all.
- Unmapped certificates on the trust graph. They are real certificates with no business service linked, so the graph cannot say what an outage would stop. That is stated on the node, not filled in.
Previous: Rubric · Next: Deliverables
All steps: Analyst method