# Retest package, closure approval and next-year readiness backlog

Federal FISMA audit readiness | Worked example with fictional data

Step: Verify closure and keep the program audit-ready
Owner: CISO governance + POA&M manager + Independent validation owner
When: Monthly POA&M review; quarterly executive review; year-round operation

## Gather first
- Approved corrective action
- Updated control evidence
- Fresh population
- Independent validation plan
- POA&M status
- Executive review record

## How to prepare it
1. Verify implementation and collect evidence that the changed control operated over the agreed period. Use a fresh population rather than relying only on the sample that exposed the issue.
2. Reperform the original test, compare expected and observed results, investigate every exception and assess whether the same cause affects other systems.
3. Obtain closure approval from the authorized agency official, update POA&M and risk records, retain the rationale and carry remaining work into the next audit calendar.

## Example

### Fictional closure
The updated feed is live. An independent reviewer selects a new population after 30 operating days, traces terminations to disabled accounts and documents the one approved emergency-account exception separately.

## Review
Closure demonstrates sustained effectiveness and has an authorized decision, retest and record update.

## Handoff
Give executives a quarterly view of overdue actions, repeat findings, age and accepted residual risk.

Official reference: NARA OIG FY 2026 report example
https://www.oversight.gov/reports/audit/audit-naras-compliance-federal-information-security-modernization-act-fisma-fiscal-0

Use the current rules and any prescribed forms for your engagement.
