PROJECT 004 / REQ-010

Backup Restoration Testing

Follow a fictional marketing agency’s backup control from incomplete coverage to a recorded restore review. Each assessment uses October 28, 2026 as its reference date.

Three runs of the Python assessor
RunREQ-010 finding Supported draftsNeed work
Original assessmentNeeds work. CTL-010: status is partial; do not claim implementation.411
Action ready for reviewNeeds work. CTL-010: status is partial; do not claim implementation.411
Control and evidence updatedSupported draft510

What changed

  1. Original assessment. REQ-010 maps to CTL-010. The control already points to EV-010, with a recorded review dated October 20. Its implementation status is partial, so the assessor reports Needs work.
  2. Action ready for review. ACT-008 changes to ready_for_review. The implementation status and evidence record stay the same, so the finding stays open.
  3. Control and evidence updated. The sample records the protected scope and restore as implemented and updates EV-010 with the fictional review reference DEMO-RESTORE-REVIEW-010 dated October 27. The assessor can now produce a Supported draft for REQ-010.

The assessment reads the recorded review metadata. Its supported draft calls for a person to confirm the protected scope and inspect the restore record. REQ-015, the separate check for backup integrity before restoration, keeps its original finding.

Reproduce the three runs

From the Project 004 folder, run python demo_backup_reassessment.py --output my-backup-reassessment and open my-backup-reassessment/index.html. Each stage in the local output has its own input copy and report.

Inspect the comparison data