Public register
Federal cloud cybersecurity audit report

CISA SCuBA implementation audit · DHS OIG OIG-26-30

Department of Homeland Security Office of Inspector General · oig-26-30-cisa-scuba

Recorded status
Final report issued September 22, 2026; Oversight.gov lists no recommendations
Last verified
Listed organization
Cybersecurity and Infrastructure Security Agency
Organization location
United States
Source data refreshed
Report number
OIG-26-30
Report date
September 22, 2026
FCEB agencies missing the June 2025 implementation deadline
86 percent, as reported by DHS OIG
Recommendations listed
0
Questioned costs
$0

What this record covers

DHS OIG report OIG-26-30 reviewed CISA’s Secure Cloud Business Applications project and the Federal Civilian Executive Branch’s implementation of BOD 25-01. The report states 86 percent of FCEB agencies did not meet the June 2025 deadline for implementing SCuBA policies. It also says CISA can provide policies, assistance and reporting but lacks authority to require full and timely implementation. This is a finding about that federal deadline, not a current tenant score, private-sector failure rate, CISA certification result or evidence that every affected agency was compromised.

How to verify it for your work

  1. Reconcile each production tenant to the current directive and baseline list

    Agency CIO or CISO, cloud service owner, agency counsel and CISA reporting liaison · At first-quarter tenant inventory refresh, after a new cloud tenant is created, and when CISA changes a required configuration

    List the agency, tenant identifier, environment, workload, responsible owner and current BOD applicability decision. Compare the row with CISA’s current required configurations and the agency’s CISA submission records. If a tenant, assessment or mandatory setting is missing or late, record the actual state, risk, interim control, accountable executive, funded next step and approved reporting path. Do not recreate evidence with a past date or report an assessment as complete when policy checks were not collected.

    Evidence to keep A dated tenant reconciliation, source exports, policy and tool versions, approval record, current status and any submitted correction receipt.

  2. Separate CISA policy issuance from agency implementation ownership

    CIO, CISO, authorizing official, cloud product owners and executive risk committee · Before approving the recovery plan and at each executive risk review

    Give each mandatory policy one accountable agency owner, a setting-level test, a change date, a retest result and an evidence link. Escalate accepted risk and resource barriers to the official who can fund work or accept agency risk. CISA’s published guidance and support do not substitute for the agency’s own implementation, monitoring or authorization decisions.

    Evidence to keep A policy-level owner register, funded corrective actions, approved risk decisions and a management report that distinguishes mandatory-policy coverage from recommendations.

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