Skip to main content

April 28, 2026

GAO finds Treasury skipped security rules for DOGE payment access

Constitution Congress
Federal News Network
Fedscoop
Bureau of the Fiscal Service
Bureau of the Fiscal Service
+8

A DOGE worker bypassed security training before gaining access to systems processing 1.2 billion federal payments

The released report GAO-26-108131 on April 28, 2026, titled "Department of Government Efficiency: Treasury Needs to Fully Implement Data Protection Controls." The report found that Treasury's Bureau of Fiscal Service violated its own IT security rules when granting a DOGE team member access to the federal government's core payment infrastructure. GAO described the April 28 findings as "the preliminary results" of its ongoing review, stating that additional reports on DOGE's access to Treasury systems are coming.

Senators Elizabeth WarrenElizabeth Warren (D-MA) and Ron Wyden (D-OR) in February 2025, after news of DOGE's Treasury access became public. They asked GAO to identify which systems were accessed, who had access and whether those individuals held appropriate clearances, and what protections existed for national and economic security.

The Bureau of Fiscal Service gave the DOGE employee access to three payment systems: the , the Secure Payment System (SPS), and the Intra-Governmental Payment and Collection (IPAC) system. PAM processes approximately 1.2 billion domestic payments annually on behalf of federal agencies. It handles essentially all domestic U.S. government payments, including Social Security checks, federal employee salaries, and vendor contracts.

SPS allows agencies to securely certify and submit payments to the Fiscal Service, with a strictly enforced separation of duties requiring two separate authorized users for each transaction. IPAC manages fund transfers between federal agencies. Together, these three systems sit at the core of how the U.S. government moves money.

The DOGE employee at Treasury has been identified in court filings and as Marko Elez, a 25-year-old software engineer. Elez began working at the Treasury Department on January 21, 2025, as part of the DOGE effort to cut federal spending and identify fraud. He resigned on February 6, 2025, after the Wall Street Journal linked him to a deleted social media account that had posted racist content.

GAO's report referred to Elez only as a "DOGE associate" and did not name him directly. The access he received and the security failures surrounding it are the subject of the April 28 report and at least one forthcoming GAO follow-up.

The Bureau of Fiscal Service granted Elez access to view, copy, and print data from all three payment systems. It also let him see the systems' source code. However, BFS never required him to complete the security training mandated for anyone handling sensitive payment data, and he never signed Treasury's rules-of-behavior document that all users must acknowledge before receiving system access.

GAO said these omissions violated BFS's own IT security protocols. that BFS did not hold Elez accountable for any of these violations during his time at the department.

At one point during Elez's tenure at Treasury, BFS that would have allowed him to create, modify, and delete data in one of the three payment systems. This level of access went far beyond the read-only permission he was supposed to have. GAO found no evidence that Elez made any changes to that system's data before BFS caught the error and revoked the elevated access.

The mistake occurred partly because the access request was changed several times before BFS approved it. GAO said the repeated modifications reflected a lack of controls in BFS's access-granting process.

Despite having only read-level system access, Elez sent an unencrypted Excel file to two DOGE associates at the General Services Administration without obtaining agency approval. The file contained personally identifiable information, including the first and last names of 350 individuals listed to receive USAID payments. Sharing payment recipient data outside Treasury in unencrypted form violated federal data handling rules.

Treasury's โ€” systems designed specifically to detect and block unauthorized data transfers โ€” failed to flag or stop the transmission. GAO found that the tools didn't track the transfer at all. BFS also never held Elez accountable for the violation.

The legal fight over DOGE's Treasury access began within weeks of Elez's arrival. A coalition of labor unions sued to block the access, and issued a temporary restraining order barring DOGE personnel from accessing any BFS payment record or system. The Trump administration later agreed to restrict additional DOGE staff from the payment systems.

Elez had already resigned by the time the court order took effect. His departure preceded the most active phase of the legal battle, but the access he received during his three-week tenure at Treasury is what the April 28 GAO report examined.

Treasury Secretary Scott Bessent at Treasury in February 2025, telling Bloomberg Television that the unit consisted of trained professionals. The GAO report released more than a year later found those assurances were inaccurate for at least one DOGE member โ€” Elez completed no required training before receiving access.

In comments on GAO's draft report, Treasury agreed with three of the four recommendations. The department did not formally agree or disagree with the fourth, which asked BFS to conduct exit interviews and collect signed post-employment documentation from staff who leave without completing standard departure procedures.

GAO issued four formal recommendations to Treasury. The first asks BFS to define minimum screening requirements before granting any user access to payment data. The second requires BFS to strengthen mandatory training so no user can access sensitive systems before completing it. The third directs BFS to update its process for reviewing outgoing emails that contain unencrypted payment information so monitoring tools actually flag them.

The fourth recommendation asks Treasury to conduct exit interviews and collect signed post-employment documentation from departing staff who had payment system access but left without completing standard procedures. Treasury's partial non-response on this point means the accountability gap created by Elez's abrupt departure remains unaddressed. that sources called the April 28 report just the tip of the iceberg given how many DOGE associates accessed federal agencies.

GAO's ongoing review extends beyond the access Elez received. The April 28 report examined only one DOGE employee's access to one set of Treasury systems during a three-week window in early 2025. GAO stated it is still examining broader patterns of DOGE access across the department and will issue additional reports. Congressional oversight advocates argue the security failures GAO documented at Treasury likely replicate patterns at other agencies where DOGE teams operated.

The Bureau of Fiscal Service doesn't decide what gets paid or to whom โ€” it executes payments as directed by other agencies. But the access Elez received gave him visibility into payment records across the entire federal government, including sensitive foreign aid disbursements through USAID, making BFS one of the highest-risk entry points in the entire federal data infrastructure.

๐Ÿ›๏ธGovernment๐Ÿ›ก๏ธNational Security๐Ÿ”Ethics๐Ÿ”’Digital Rights

People, bills, and sources

Marko Elez

DOGE software engineer, Treasury Department (January 21 โ€“ February 6, 2025)

Scott Bessent

U.S. Treasury Secretary

Elizabeth Warren

Elizabeth Warren

U.S. Senator (D-MA), Ranking Member, Senate Banking Committee

Ron Wyden

U.S. Senator (D-OR)

Colleen Kollar-Kotelly

U.S. District Judge, District of Columbia

What you can do

1

civic action

Contact your senators to push Treasury to implement all four GAO recommendations

Treasury agreed with three of GAO's four recommendations but did not formally commit to the fourth, which requires exit interviews and post-employment documentation from departing staff with payment system access. Your senators sit on committees that oversee Treasury and can request a written compliance timeline from the department.

Hi, I'm a constituent calling about the GAO report on DOGE's access to Treasury payment systems, report GAO-26-108131, released April 28. I want Senator [Name] to push Treasury to comply with all four GAO recommendations, especially the one about exit interviews for departing staff with payment system access. Treasury didn't formally agree to that one. Can you tell me if the Senator plans to request a compliance timeline from Treasury?

2

civic action

Contact your House representative to request an oversight hearing on DOGE's federal data access

The House Oversight Committee has jurisdiction over federal agency cybersecurity and operations. GAO said the April 28 report is only the beginning of a broader review of DOGE's access across Treasury. Your representative can request or support a formal oversight hearing to examine the full scope of that access.

Hi, I'm a constituent calling about the GAO report on DOGE's access to Treasury payment systems. GAO said this is only preliminary โ€” more reports are coming. I want Rep. [Name] to request or support a House Oversight Committee hearing on DOGE's federal data access before those follow-up reports are released. Has the representative taken any position on oversight of DOGE's agency access?

3

monitor

Track GAO's ongoing DOGE-Treasury investigation through public reports on gao.gov

GAO publishes all its reports publicly and for free. Because the April 28 report is only the first installment of a broader review of DOGE's Treasury access, checking gao.gov lets you track findings as they are released. GAO also offers email alerts by agency and topic area.

Visit gao.gov and search for GAO-26-108131 to read the full report. Sign up for GAO email alerts under Treasury and government operations topics. Follow-up reports on DOGE's Treasury access will appear in the same product series.