Control Mappings#

Mappings connect controls from a source document to controls in one or more target documents. This helps you understand coverage and identify gaps.

Creating a Mapping#

  1. Navigate to Mappings → New Mapping
  2. Enter a name for your mapping
  3. Select the source document (e.g., your internal policies)
  4. Select one or more target documents (e.g., ISO 27001, NIST)
  5. Adjust the coverage slider:
    • High Coverage — More suggested matches, may include lower-similarity results
    • Balanced — Default setting, good trade-off
    • High Accuracy — Fewer but more precise matches
  6. Click Create
Mapping creation uses AI to find semantically similar controls. This process may take a few minutes for large control sets.

Understanding Mappings#

Coverage#

The coverage indicator shows what percentage of source controls have at least one mapped target:

  • Mapped controls — Have one or more included target mappings
  • Unmapped controls (gaps) — No target mappings found or included

Mapping View#

Each source control shows:

  • The control ID and text
  • Suggested target controls with similarity scores
  • Whether each target is included (counts toward coverage) or excluded

Working with Mappings#

Reviewing Suggestions#

Qudit suggests target controls based on semantic similarity. Review each suggestion and:

  • Include — The target adequately addresses the source control
  • Exclude — The suggestion isn’t a good match

Adding Manual Mappings#

If a relevant target wasn’t suggested:

  1. Click Add Target on the source control
  2. Search for controls across target documents
  3. Select and add the appropriate control

Identifying Gaps#

Controls without any included targets are considered gaps. These indicate:

  • Areas where your policies aren’t covered by existing frameworks
  • Controls that need custom implementation

Gap Assessments#

When you identify gaps in a mapping, you can create a gap assessment to:

  1. Track implementation of unmapped controls
  2. Assign controls to team members
  3. Collect implementation evidence
  4. Fill the gaps back into the mapping

See Assessments for the full workflow.

Analytics#

The mapping view includes analytics:

  • Topic breakdown — Mapped vs unmapped controls by topic
  • Control frequency — Which target controls are most commonly mapped

Use these insights to understand coverage patterns and prioritize gap remediation.

Backward Control Sets Assessments Forward