Public register
Federal cybersecurity and privacy audit report

FY 2026 FISMA audit · National Credit Union Administration

National Credit Union Administration Office of Inspector General · ncua-fy2026-fisma-oig-26-09

Recorded status
Final report issued August 13, 2026; five recommendations listed open on Oversight.gov
Last verified
Listed organization
National Credit Union Administration
Organization location
United States
Source data refreshed
Report number
OIG-26-09
Report date
August 13, 2026
Recommendations listed open
5
Questioned costs
$0
Open recommendation themes
Asset-location detail, periodic inventory validation, device baseline monitoring and cybersecurity workforce planning

What this record covers

The NCUA OIG’s agency-wide FY 2026 FISMA evaluation is report OIG-26-09. Oversight.gov currently lists five open recommendations concerning more precise asset-location records, periodic asset-inventory review, baseline monitoring across all devices, and a documented and current cybersecurity workforce assessment. The report page describes the independent evaluation as containing ten new recommendations, while its open-recommendations tracker lists five open; this record reports the tracker count and preserves that distinction. This is an audit, not a certification or a security incident finding.

How to verify it for your work

  1. Build one device population that can be reconciled

    IT asset manager, endpoint engineering, CMDB owner, ISSO and internal audit liaison · Before baseline monitoring begins, then at each scheduled inventory review

    Agree on the device classes and environments in scope, merge authoritative endpoint, network, cloud and asset sources, assign a stable device identifier, and document duplicate, missing and out-of-scope records. Define how room or workspace details are captured where policy requires them. Have an owner who did not prepare the reconciliation sample records back to source and record exceptions with a correction date.

    Evidence to keep A dated population file, source mapping, duplicate and exclusion log, periodic review approval and sampled record-to-source checks.

  2. Turn configuration monitoring into an operating control

    Endpoint security lead, configuration management board, system owners and control assessor · At baseline approval, on each monitoring cycle and before audit evidence is submitted

    For each device class, identify the approved secure baseline and its version, define the measurable compliance threshold, identify the scanner or management data source and monitoring cadence, and establish what happens when a device fails or is not reporting. Route exceptions through an authorized risk process with an owner and expiry. Reconcile the monitored population to the approved device population instead of reporting only the devices that successfully checked in.

    Evidence to keep Approved baseline versions, population reconciliation, dated compliance results, exception approvals, remediation tickets and a retest sample.

Read the program guide

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes