Filters
How to search
  • Plain words find names, texts and examples.
  • "two words" finds the exact phrase.
  • --name or -x finds an option.
  • #word looks only inside commands.
  • @grep finds lessons and labs that use grep.
  • Filters: cat:network · in:labs · in:notes · level:rhcsa · ch:8 · root:yes. Put ! before a word to leave it out. OR between words means one of them.
  • ↑ ↓ to move · Enter to open · Esc to close · / to search

DevSecOps & cloud securityDevSecOps series

Compliance posture at a glance

The auditor asked for three things and the team produced a spreadsheet, a screenshot and an apology. Compliance is a maintenance programme, and these six tiles are what maintenance looks like.

Quick reference

Status: Q4

MetricValueNote
Controls passing92%%of 148 controls
Evidence current88%%refreshed this quarter
Open exceptions42 expire this month
Last audit12 daysexternal, ISO 27001 scope
Findings closed37of 41 from the audit
Owner coverage96%of assets with a named owner

Explained

The register

Controls passing: ninety-two percent of 148, so 136 controls have evidence behind them this quarter. The twelve that do not are the agenda: a control that passes on paper is worse than a red one.

Evidence current: eighty-eight percent refreshed this quarter. Evidence has a shelf life: a screenshot from February proves February, and an auditor will ask for the date on the file.

Open exceptions: four, two expiring this month. An exception is a decision with a date on it; one without an expiry is a permanent hole with a ticket number.

The audit

Last audit: twelve days ago, external, ISO 27001 scope. The date matters less than the findings list it produced, because the list is the work plan for the next quarter.

Findings closed: thirty-seven of forty-one. Closure rate is the honest measure of a compliance programme, and the four that remain are the ones to talk about first.

The owners

Owner coverage: ninety-six percent of assets have a named owner. The last four percent are the assets nobody will claim, and those are the ones an attacker finds.

The honest caveat: a passing control is a snapshot of the day it was tested. Drift between audits is normal, which is why the exceptions register, not the pass rate, is where the truth lives.

The lesson: compliance is maintained between audits, not demonstrated during them.

In one line

Evidence first, opinions later. A control is a claim until the evidence is in the folder.

Check the register

grep -c 'open' register.csv

More notes: DevSecOps & cloud security

Open in the notes app: search, filters, copy This note on GitHub