Skip to content

Mapping Index

Informative interoperability mappings for readers evaluating the UHBS framework against familiar security frameworks. These pages explain how UHBS concepts relate to external taxonomies — they are not certifications, compliance attestations, or claims that UHBS implements those standards.

Use these mappings when:

  • A blue-team or GRC stakeholder asks how UHQS modules relate to NIST CSF / SP 800-53 control families
  • A CTI analyst wants ATT&CK-oriented language for discussing decoy telemetry (without inventing ATT&CK coverage claims)
  • An OT/ICS reader needs IEC 62443-oriented vocabulary for containment and safety-gate thinking around industrial decoys
  • A deception engineer wants D3FEND Deceive labels for the kind of decoy graded, or Engage goals for why it was deployed

Available mappings

For controlled comparative experiments that stay outside UHQS, see the optional Advanced Evidence Profile (AEP).

Scorecard framework_refs (optional)

Sanitized fixtures MAY include a display-only framework_refs object:

"framework_refs": {
  "attack": ["T1595", "T1041"],
  "d3fend": ["D3-DNR", "D3-SHN"],
  "engage_goals": ["Expose", "Elicit"]
}

These tags do not affect UHQS, δ_C, or letter grade. See the scorecard schema.

Trust limits

Mappings are informative. They do not replace the verbatim SCORECARD / report.json proof for any graded product under docs/conformance/. Prefer absolute URLs on the published docs site when sharing externally. UHBS remains an open-source evaluation framework (Apache-2.0, v4.5.1) — not an adopted industry or academic standard.