Write the report the fixing team will act on

applied · 65 min · Objective 3.2

Task

Apply objective 3.2: turn a scan output into per-owner work with actions, dates and reasons, and prove every finding has an owner derived from the inventory.

Steps

  1. Join findings to owners from the CMDB and write lab/findings-owned.csv as finding,host,owner,action,priority,why_this_one,due_date.
  2. Any finding with no owner is a CMDB gap, not a reporting gap -- fix the CMDB and re-run until the unowned count is zero.
  3. Phrase every action as work to do, not as a finding observed: 'upgrade package X to version Y on these N hosts', never 'CVE-nnnn present'.
  4. Write one per-owner report to lab/reports/<owner>.md, scoped to that owner's hosts only, with the top five items and their dates.
  5. Write lab/findings-summary.md carrying open findings by priority band with ages, the coverage figure from the scanning lab, and the OLDEST open item in each band.

Verify

awk -F, 'NR>1 && $3=="" {n++} END {print n+0" unowned finding(s)"}' lab/findings-owned.csv
awk -F, 'NR>1 && $6=="" {n++} END {print n+0" with no reason"}' lab/findings-owned.csv
ls lab/reports/ | wc -l
grep -Eci 'coverage|oldest' lab/findings-summary.md
grep -Ec '^[0-9]+ (remediated|closed|fixed)' lab/findings-summary.md

ZERO unowned findings, zero without a reason, one report per owner, and the summary carrying coverage and oldest-open but NO activity count. Unowned findings are the most reliable predictor of non-remediation in the whole programme.

This is an independent study companion for CompTIA SecurityX CAS-005 and is not produced by or endorsed by CompTIA.