Risk Stratification Protocol¶
Protocol — instantiates Stratified Treatment
Implements the archetype by assigning cases to risk bands and linking each band to monitoring, protection, escalation, or support rules.
Risk Stratification Protocol is the standing operating rulebook that does the two things a bare score cannot: it assigns each case to a risk band by an auditable rule — one that says what to do with missing data, unclear evidence, and requested overrides — and it wires each band to a defined set of actions, with an appeal path when the assignment is wrong. Its defining idea is the governance of the mapping from band to action, not the computation of the score behind the band. A protocol earns its name only when the band changes what actually happens; if the band produces a number and nothing else, it is classification wearing a protocol's badge.
Example¶
A security team must protect thousands of assets — servers, databases, endpoints — with finite patching and monitoring capacity. The protocol assigns every asset a criticality band (crown-jewel, high, standard, low) using a rule that combines data sensitivity, internet exposure, and blast radius, with an explicit default for the messy cases: any asset that is unclassified or missing an owner is provisionally banded high until reviewed, so unknowns fail safe rather than slipping through. Each band is wired to concrete actions: crown-jewel assets require multi-factor access, a 24-hour patch window, continuous monitoring, and change-control sign-off; low-band assets get quarterly patching and basic logging. When a system owner believes their asset is mis-banded — over-controlled or under-controlled — they file an appeal that a review board adjudicates against the assignment rule.
The payoff is that patching effort concentrates on the assets whose compromise would hurt most, the assignment rule stops teams from quietly self-downgrading to dodge controls, and the appeal path corrects the genuine misclassifications instead of forcing everyone to live with the formula. The band is not the deliverable; the governed action is.
How it works¶
- Codify the assignment rule. Inputs, a fail-safe default for missing or ambiguous data, an override mechanism that demands a recorded reason, and a rule for evidence quality.
- Wire bands to actions. Each band maps to a specific bundle of monitoring, protection, escalation, or support obligations — the treatment, stated as rules an operator can follow.
- Open an appeal path. Owners can contest an assignment; an adjudicator applies the rule rather than negotiating case by case.
- Log everything. Assignments, overrides, and appeals are recorded so the mapping is auditable and drift is visible.
Tuning parameters¶
- Assignment strictness — tight rules produce consistent, defensible bands but handle genuine edge cases poorly; loose rules flex but invite inconsistency and gaming.
- Default for unknowns — defaulting to high fails safe but over-controls until review; defaulting low is efficient but leaves blind spots.
- Override latitude — generous overrides capture local knowledge but dilute the rule; stingy overrides are uniform but brittle.
- Appeal SLA — fast appeals build trust but consume adjudicator time; slow appeals are cheap but push owners toward silent workarounds.
- Treatment contrast — a steep gap between bands focuses protection hard but makes a misassignment costly; a shallow gap is forgiving but may not repay the overhead.
When it helps, and when it misleads¶
Its strength is making exceptions governable: the informal downgrade an operator would once have done quietly becomes an explicit, logged, appealable decision, and every band is tied to a real action rather than a dashboard color. That is the difference between a scoring exercise and an operating discipline.
Its failure mode is treating the score as the treatment — publishing bands that decorate an asset register but change no behavior, which the archetype rightly calls confident classification, not stratified treatment. The classic misuse is leaning on a raw vulnerability score such as CVSS as if the number itself were a remediation policy, when a high score with low exposure and a low score on a crown-jewel can demand opposite responses.[n1] The related risk is gaming the assignment inputs to land in a cheaper band. The discipline that guards against both is to require every band to name a concrete action and to audit overrides and appeals for patterns of convenient self-downgrading.
How it implements the components¶
assignment_rule— its governance core: how a case enters a band, how missing data and evidence quality are handled, and how overrides are recorded.treatment_policy— the band-to-action mapping that specifies the monitoring, protection, escalation, or support each band obligates.review_or_appeal_path— the owner-initiated appeal and its adjudication against the rule, protecting against assignment error.
It governs the mapping, not the measurement. It does not choose the classification_basis or set the resource_or_threshold_differentiation — the indicators and cut-points that generate the score — which is the work of Clinical Risk Banding; it does not run the monitoring_feedback or test the outcome_equivalence_standard that judge whether the bands stay fair over time — that is Fairness Audit by Stratum; and it does not own the scheduled reclassification_rule that re-tiers cases on a clock — that is Case Management Tiers.
Related¶
- Instantiates: Stratified Treatment — Risk Stratification Protocol is the operating rulebook that turns risk bands into governed, appealable action.
- Consumes: Clinical Risk Banding — a scoring or banding method supplies the risk estimate that this protocol assigns and acts on.
- Sibling mechanisms: Case Management Tiers · Fairness Audit by Stratum · Segmented Customer Treatment Rules · Stratum-Specific Threshold Schedule · Tiered Service Catalog · Vulnerability-Based Support Workflow
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Risk Stratification Protocol operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it implements the archetype by assigning cases to risk bands and linking each band to monitoring, protection, escalation, or support rules.
Independent corroboration: The frozen evidence defines Risk Stratification Protocol as 'Implements the archetype by assigning cases to risk bands and linking each band to monitoring, protection, escalation, or support rules', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Rule, Policy & Commitment — Risk Stratification Protocol includes features of a standing rule, threshold, contractual commitment, or policy constraint governing future conduct, but its defining operation is a case-specific gate, selection, routing, prioritization, or resource disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Medicine & Healthcare
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Assigning cases to risk bands linked to monitoring and care is canonical clinical risk stratification.
Related originating lineages:
- Psychology — Experimental, clinical, and behavioral psychology supplies a parallel or contributing lineage for the mechanism's defining operation: implements the archetype by assigning cases to risk bands and linking each band to monitoring, protection, escalation, or support rules.
- Public Administration & Policy — Public-service triage independently links bands to protection and escalation.
- Statistics & Experimental Design — Predictive classification materially supplies risk assignment.
Review resolution: Both blind reviewers agree that medicine_healthcare is the primary historical origin. Explicit reconciliation of alternate origin disagreement, origin mode disagreement, encyclopedia synthesis disagreement starts from reviewer_a’s mechanism-specific evidence: Assigning cases to risk bands linked to monitoring and care is canonical clinical risk stratification. Reviewer A proposed alternates=public_administration_policy, statistics_experimental_design, origin_mode=convergent, domain_reach=multi_domain, and encyclopedia_synthesis=true; reviewer B proposed alternates=psychology, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=false. The final record retains every independently supported alternate from either review (public_administration_policy, statistics_experimental_design, psychology) without an arbitrary cap, selects origin_mode=convergent to represent the combined lineage evidence, and keeps domain_reach=multi_domain and encyclopedia_synthesis=true from the more mechanism-specific assessment. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The Common Vulnerability Scoring System (CVSS) rates the technical severity of a vulnerability on a 0–10 scale. It is an input, not a treatment policy: severity must be combined with exposure and asset criticality before it implies an action, which is exactly the gap a stratification protocol fills. ↩