COPRSETR WORKSHEET
Signed system inventory reconciliation and system-to-control coverage matrix
Federal FISMA audit readiness · Step 2 · Reconcile the inventory before testing controls- Who prepares it
- Enterprise architecture + System owners + Asset management + Acquisition
- When to prepare it
- First month; refresh at least monthly through the audit
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Fictional exception
- A procurement catalog lists a cloud service absent from the authorization inventory. Mark it newly discovered, identify the agency data owner, determine data sensitivity and route it for a documented scope decision.
- Reconciliation measure
- Report match rate as matched in-scope records divided by all in-scope records, plus the raw unmatched count and unresolved age. Never hide unresolved items in the percentage.
Gather first
- Authoritative system inventory
- Cloud account exports
- Application catalog
- Data-flow register
- Authorization packages
- Contracts
- Control inheritance records
How to prepare it
- Take dated extracts from each source. Normalize system identifiers without deleting the original values. Join on stable IDs first, then document any name-based matches.
- Classify each source row as matched, unmatched, duplicate, retired, newly discovered or out of scope. Assign each exception an owner and evidence-supported disposition.
- Map every in-scope system to an owner, impact level, data types, hosting, authorization status, inherited controls, latest assessment and open POA&Ms. Obtain a second-person completeness attestation.
Review
A reviewer can reproduce the joins, see all unmatched assets and trace each system to owners and assessed controls.
Handoff
Send signed inventory and unresolved high-risk exceptions to the CISO and audit lead.
Use the issuer’s current instructions and any required forms when you submit.
GAO Cybersecurity Program Audit Guide (opens in a new tab)