BLACKSHIELD

Public Guide

How BlackShield Shows Control Coverage, Gaps, and Evidence

BlackShield turns mapped findings into a benchmark heatmap, service rollups, control drill-down, and a CSV export so customers can prove where coverage exists and where gaps still need work. Audience: Security leads, auditors, tenant admins, service owners, and buyers validating control visibility. Typical setup time: 10-15 minutes.

reference

Use this if

BlackShield turns mapped findings into a benchmark heatmap, service rollups, control drill-down, and a CSV export so customers can prove where coverage exists and where gaps still need work.

Audience
Security leads, auditors, tenant admins, service owners, and buyers validating control visibility
Typical time
10-15 minutes

Before You Begin

  • Pick the framework, benchmark, or service review you are trying to satisfy.
  • Set a fixed reporting window before comparing pass rate or coverage movement.
  • Have `/compliance` and `/reports` available so the reviewer sees both the live view and the export path.

Guide walkthrough

Step 1

Filter the exact benchmark view you need

The compliance console is useful because it filters down to the specific slice your reviewer asked for.

  • In `/compliance`, filter by framework, benchmark, service name, status, and reporting window.
  • BlackShield supports 30, 60, 90, and 180 day windows for trend and coverage views.
  • Set the same filters before you export so the CSV matches the screen you reviewed.

What success looks like

Set the same filters before you export so the CSV matches the screen you reviewed.

Step 2

Drill from the heatmap into the exact controls and findings

The heatmap is only useful if it leads to the controls and findings behind the color.

  • Use the benchmark heatmap to select a benchmark, then switch into control view.
  • Open a control row to inspect the mapped findings behind that control signal.
  • Use service rollups to see which workloads or repositories are driving failures.

What success looks like

Use service rollups to see which workloads or repositories are driving failures.

Step 3

Export a coverage file that matches the live view

The CSV should not be a separate reporting world; it should match what the user just filtered in the product.

  • Use the built-in export action to download the control-coverage CSV from the current filter set.
  • Pair the export with the on-screen heatmap and drill-down when answering an auditor or buyer.
  • Use `/reports` if you need to combine control coverage with broader executive or findings exports.

What success looks like

Use `/reports` if you need to combine control coverage with broader executive or findings exports.

What success looks like

  • The heatmap can be traced down to the underlying controls and findings without ambiguity.
  • The exported coverage report ties posture claims back to mapped findings and owners.
How BlackShield Shows Control Coverage, Gaps, and Evidence | BlackShield Docs