# Signed system inventory reconciliation and system-to-control coverage matrix

Federal FISMA audit readiness | Worked example with fictional data

Step: Reconcile the inventory before testing controls
Owner: Enterprise architecture + System owners + Asset management + Acquisition
When: First month; refresh at least monthly through the audit

## Gather first
- Authoritative system inventory
- Cloud account exports
- Application catalog
- Data-flow register
- Authorization packages
- Contracts
- Control inheritance records

## How to prepare it
1. 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.
2. Classify each source row as matched, unmatched, duplicate, retired, newly discovered or out of scope. Assign each exception an owner and evidence-supported disposition.
3. 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.

## Example

### 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.

## 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.

Official reference: GAO Cybersecurity Program Audit Guide
https://www.gao.gov/products/gao-23-104705

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