FY 2026 FISMA performance audit · U.S. Nuclear Regulatory Commission
Nuclear Regulatory Commission Office of Inspector General · nrc-fy2026-fisma-roa-oig-nrc-26-a-04
- Recorded status
- Final report issued September 23, 2026; three recommendations listed open on Oversight.gov
- Last verified
- Listed organization
- U.S. Nuclear Regulatory Commission
- Organization location
- United States
- Source data refreshed
- Report number
- ROA-OIG-NRC-26-A-04
- Report date
- September 23, 2026
- Recommendations listed open
- 3
- Questioned costs
- $0
- Recurring evidence themes
- Data inventory and metadata; vulnerability remediation; POA&M or formally approved deviation evidence
What this record covers
The NRC OIG’s agency-wide fiscal year 2026 FISMA performance audit is report ROA-OIG-NRC-26-A-04. Oversight.gov lists three open recommendations: complete a comprehensive data inventory with metadata, remediate vulnerabilities within required timeframes, and document late remediation in POA&Ms or approved deviations with plans, milestones and risk decisions. These are audit recommendations, not a certification award or evidence of a security incident. Verify current recommendation status before relying on it.
How to verify it for your work
Make vulnerability closure independently testable
System owner, vulnerability management lead, ISSO and POA&M manager · At discovery, each remediation milestone and before closure approval
For each finding, preserve the scanner or assessment record, affected asset and system boundary, severity, applicable remediation deadline, assigned owner, change or patch record, and a post-remediation rescan. If the deadline cannot be met, document the approved deviation or POA&M before treating the risk as accepted, with rationale, interim controls, milestones, approver and review date. Do not mark a finding closed from a change ticket alone.
Evidence to keep A dated finding-to-asset record, approved milestone or deviation, remediation artifact and independent retest result linked by stable identifiers.
Reconcile the system data inventory to authoritative sources
Chief Data Officer, CIO data office, system owners and security architecture · During annual FISMA preparation and after material system or data changes
Define which systems and data assets are in scope, reconcile the inventory to CMDB, authorization and cloud inventories, assign accountable stewards, and record metadata fields and missing values. Sample records back to system owners and evidence the reason for each exclusion. Keep the approved inventory version and reconciliation decisions so reviewers can reproduce the population.
Evidence to keep A versioned inventory, source-to-inventory reconciliation, documented exclusions, named data stewards and dated review approvals.