Methodology & source manifest
Everything on the CISA monitor derives from public records — the Department's own Budget-in-Brief, the enacted appropriations act, and the USAspending API. This page is the audit trail: method, sources, validation, and every flag.
Continuing resolution vs. enacted
The Budget-in-Brief's FY2024–FY2026 columns reflect continuing-resolution levels that hold prior-year amounts flat — which is why those years read identically. The figures actually appropriated in law are different: the DHS Appropriations Act, 2026 provides $2,218,634,000 for Operations and Support and $386,464,000 for Procurement, Construction, and Improvements. This monitor keeps the two distinct, reports the enacted amounts alongside the CR columns, and computes the FY2026→FY2027 change against both baselines — never collapsing them into one number.
Isolating CISA in USAspending
CISA does not appear as its own awarding sub-agency in USAspending — its contracts are awarded through the Department's shared-services Office of Procurement Operations, which also buys for headquarters and other components. Filtering by awarding sub-agency cannot isolate CISA. The monitor instead isolates CISA by its own Treasury appropriation accounts — 070-0566, 070-0412, and 070-0805— which map one-to-one to the budget spine's appropriations, so the live-money layer and the budget layer describe the same accounts.
Source documents & validation ledger
CISA budget spine — topline by appropriation, FY2024–FY2027
extract not present at build time
CISA spending — live obligations & contracts (USAspending)
extract not present at build time
The CISA budget spine is hand-keyed from scanned Budget-in-Brief PDF tables and the enacted bill text; figures are cited line by line and re-validated against their printed subtotals at build time.