What This Bill Does
The VETRA Act would direct the Department of Veterans Affairs to run a pilot program to modernize digital identity proofing and authentication on up to three high-volume VA service platforms. It would replace legacy knowledge-based or single-factor logins with multi-layered, high-assurance digital identity tools, with a focus on reducing fraud, improper payments, and account access problems for veterans and other eligible users. The bill caps spending at $25 million from existing VA information technology funds and requires the VA to report back on implementation and results. It also sets a two-year limit on the pilot unless Congress later extends it.
- Creates a VA pilot program for digital identity proofing and authentication.
- Limits the pilot to not more than three high-volume digital service platforms.
- Allows up to $25 million in existing VA IT funds; no new appropriations are authorized.
- Requires commercially available identity solutions certified to at least IAL2 and AAL2.
- Ends the pilot authority two years after enactment unless Congress extends it.
Who This Bill Affects
For veterans and other eligible VA users, this bill could change how they prove who they are when using VA websites and portals. If the pilot works as intended, it could reduce fraud and account access problems, but some users may face new authentication steps, especially for sensitive transactions or account recovery. The bill also limits the pilot to up to three VA platforms and caps spending at $25 million from existing VA IT funds, so its effects would be concentrated in selected services rather than across the whole VA system.
See how this bill affects you — sign in for a personalized analysisWho Supports & Opposes This
- Veterans who use VA online services Supporters would say stronger identity checks can protect benefits accounts from fraud, unauthorized access, and improper payments. If the pilot improves account recovery and reduces failed logins, it could make VA services more reliable for legitimate users.
- VA administrators and cybersecurity professionals They may argue that a risk-tiered, standards-based pilot is a practical way to modernize outdated systems without forcing a full-scale rollout immediately. The reporting requirements also let the department measure whether the new tools actually save money and improve security.
- Taxpayers concerned about improper payments Supporters can point to the bill’s explicit goal of reducing fraud and improper payments, along with its requirement to assess cost savings and operational efficiencies. If the pilot prevents even a modest amount of fraud, it could offset some of the implementation cost.
- Veterans with limited digital access or low digital literacy Opponents may worry that stronger authentication will create more barriers for people who already struggle with online systems, especially during proofing, login, or account recovery. The bill itself anticipates this risk by requiring GAO to examine barriers for rural users, people with disabilities, and those with limited digital literacy.
- Privacy advocates They may be concerned about expanded use of multi-layered identity systems and adaptive authentication, which can involve more data collection and more complex tracking of user behavior. Even with Privacy Act and FISMA compliance, critics may question whether the security gains justify the added data handling.
- Budget hawks or agencies competing for IT funds Because the bill allows up to $25 million from VA information technology funds, some may object that the pilot diverts money from other technology priorities. They may also argue that a two-year pilot could produce limited results if the department cannot scale the system quickly.
Key Implications
-
““replace legacy knowledge-based or single-factor identity verification mechanisms””
This means the VA would move away from older login and proofing methods that rely on passwords, personal questions, or a single authentication step. For users, that could improve security, but it may also change familiar account access routines.
-
““not more than three high-volume digital service platforms””
The pilot is limited to a small number of major VA systems rather than the entire department. That keeps the test focused, but it also means most VA digital services would not change immediately.
-
““may obligate or expend not more than $25,000,000””
The program has a hard spending cap and must come from amounts already authorized for VA information technology systems. That limits the fiscal footprint and signals that Congress wants a controlled test before any broader rollout.
-
““Not later than 120 days after the date of enactment””
The VA would have to submit an implementation plan relatively quickly after the bill becomes law. That creates an early oversight checkpoint for Congress before the pilot is fully underway.
-
““terminate on the date that is two years after the date of enactment””
The authority to run the pilot is temporary. Any expansion beyond the pilot’s scope or funding cap would require a later act of Congress.
Latest Status
June 4, 2026
Referred to the House Committee on Veterans' Affairs.
Take Action
Get more from BillBoard
Free tools to understand, respond to, and track this bill.
Ask AI about this billData sourced from api.congress.gov.