Skip to content
Documentation

Compliance

The compliance suite has five pages: Compliance Overview, Benchmarks, Scan Runs, Exceptions and Content Sources.

The compliance suite has five pages: Compliance Overview, Benchmarks, Scan Runs, Exceptions and Content Sources. Together they import benchmark content, tailor it, target groups, run assessments, report pass rates and govern accepted failures.

Compliance Overview in light mode Compliance Overview in dark mode

Overview

Section titled “Overview”

The overview filters by benchmark, device group, OS and risk severity, and can run a scan or export devices. Its pass-rate explanation states exactly how the number is calculated; a device that did not report is not silently counted as passing.

Typical tiles and filters include Windows/Linux/macOS/Other and Low/Medium/High/Critical findings.

Benchmarks

Section titled “Benchmarks”

Benchmarks are versioned, tailored benchmark documents.

Benchmarks in light mode Benchmarks in dark mode

The list shows:

Column Meaning
Benchmark Benchmark/title/source
Platform Target OS
Published Current version and publish state
Targets Reporting devices and assigned groups
Pass rate Assessment pass and rule-coverage rates

Tiles separate assigned/not assigned, draft state and platform.

Tailor a benchmark

Section titled “Tailor a benchmark”
  1. Open or create a benchmark from a content source.
  2. Enable/disable rules.
  3. Change variables.
  4. Choose target groups.
  5. Review the impact preview.
  6. Publish the tailored version.

The impact preview estimates how many devices change before publication.

Scan Runs

Section titled “Scan Runs”

Scan Runs records each assessment campaign.

Scan Runs in light mode Scan Runs in dark mode

Column Meaning
Run Run id and benchmark
Trigger Manual, scheduled or system
State Queued, running, completed, partial, failed, cancelled
Targeted / Reported / Errored Coverage accounting
Duration Execution time

Open a run to see every device reached and why any errored. A device that never reported is a coverage gap, not a compliance pass or fail.

Exceptions

Section titled “Exceptions”

Exceptions record why a rule deliberately remains failed.

Exceptions in light mode Exceptions in dark mode

A governed exception has:

  • affected rule/device scope;
  • business reason;
  • compensating control;
  • requester;
  • separate approver;
  • expiry date.

Expired exceptions lapse on their own. Do not use exceptions as a permanent dump for rules nobody wants to fix.

Content Sources

Section titled “Content Sources”

Content Sources imports and indexes benchmark content.

Content Sources in light mode Content Sources in dark mode

States include Indexing, Ready and Failed. Upload an audits.tar.gz archive or another supported audit bundle; UEC lists licence/provenance information and which checks imported. Failed or partial imports are visible rather than treated as complete coverage.