Write a classification table that actually drives configuration

applied · 65 min · Objective 1.6

Task

Apply objective 1.6: build a handling matrix in which each tier mandates different concrete controls, then apply it to your lab and find the systems whose configuration disagrees with the classification they carry.

Steps

  1. Write lab/classification.csv with header tier,storage,transmission,access,lower_environments,disposal and three or four tiers whose rows are genuinely DIFFERENT from each other.
  2. For each lab asset in lab/cmdb.csv, check the actual configuration against its tier's row and record the result in lab/classification-check.csv as asset,tier,requirement,actual,verdict.
  3. Fix at least one disagreement for real.
  4. Add a row to lab/risk-register.csv for one disagreement you did NOT fix, with an owner and a treatment.
  5. Write lab/classification-note.md explaining why the lowest tier's row must be genuinely weaker -- a scheme whose tiers all mandate the same controls is doing no work.

Verify

awk -F, 'NR>1 {n++} END {print n" tier(s)"}' lab/classification.csv
awk -F, 'NR>1 {print $2}' lab/classification.csv | sort -u | wc -l
awk -F, 'NR>1 && $5=="fail" {n++} END {print n+0" disagreement(s)"}' lab/classification-check.csv
awk -F, 'NR>1 {n++} END {print n" risk row(s)"}' lab/risk-register.csv

Three or more tiers with DISTINCT storage requirements, at least one disagreement found, and the risk register grown by one. If every tier's storage cell is identical, rewrite the table -- that is the failure the lesson names.

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