retest
Checking a control again after a fix to confirm the problem is really gone before a finding is closed.
In more detail
An audit or test finding stays open until someone repeats the original test, against the same criteria, on the fixed control and records the evidence. Retesting catches fixes that were only partial or were applied to the wrong system. A retest must not be padded, for example by adding extra passing items to dilute a bad result.
Example
python3 jail_check.py jail-fixed.localRelated terms
- finding — A documented result of an audit or assessment that shows where something does not meet the requirement it was checked against.
- management response — Management's written answer to an audit finding, stating what will be fixed, by whom and by when.
- evidence — The records, files and outputs that show a control really exists and works, collected so that someone else can check it.
- audit sample — A subset of items picked from a complete population, such as change tickets, that an auditor tests to reach a conclusion about the whole population.
Taught in
- Defense-in-Depth & Security Control Categories — Cybersecurity Fundamentals, GRC & Cryptography
- Internal Audits, Sampling & Evidence Chains — Cybersecurity Fundamentals, GRC & Cryptography