Product Modules

Control Mapping

Review framework and control posture, generate reports, and send control-scoped requests to the Evidence Factory.

1 min read182 words

Control Mapping is the framework and control workspace at /compliance. Route access requires compliance:read unless a full-access role applies.

What it owns

  • Framework posture, tenant control overview, coverage, status, and evidence references.
  • Report generation and download.
  • Control and framework scope for contextual Evidence Factory Jobs.
  • Evidence artifact detail at /compliance/evidence/[artifactId].
  • Sealed assessment snapshots. A framework rollup backed by one shows the assessor, the assessed window, the second-person approver, a content-addressed Assessment ID, and the signing key identifier. A framework with no snapshot is marked provisional and recomputed live.

Control Mapping supplies the compliance question and selected controls. Evidence Room owns job execution, bundle inventory, sharing, and verification.

Record flow

flowchart LR
  P["Policy and runtime records"] --> C["Control Mapping"]
  C --> S["Framework and control scope"]
  S --> F["Evidence Factory Job"]
  F --> B["Control Pack / Sealed Evidence Bundle"]

Decision Request, execution, Lineage Record, policy, control, and source-entry identifiers preserve context between the source record and generated evidence.

Report and evidence actions apply resource authorization and tenant checks beyond the route-level read gate.

Control Mapping | Developer Docs | KLA Control Plane