VETRA Act
- Sponsor
- Rep. Lawler, Michael [R-NY-17]
- Committees
- Veterans' Affairs Committee (primary)
- Last action
- Jun 12, 2026
Bottom line
The VETRA Act establishes a pilot program to enhance digital security and access for veterans interacting with VA online services by modernizing identity verification systems.
What it actually does
This bill directs the Secretary of Veterans Affairs to establish a two-year pilot program to modernize the Department's digital identity proofing and authentication systems. The program aims to replace outdated verification methods with multi-layered, high-assurance digital identity solutions, reduce fraud, improve secure access for veterans, and assess cost savings before potential full-scale deployment. It mandates the use of commercially available solutions certified to specific NIST cybersecurity standards.
Proponents argue
Supporters argue that modernizing digital identity systems is crucial for protecting veterans' data, preventing fraud, and ensuring secure, efficient access to vital VA services. They contend that moving to multi-factor authentication and higher assurance levels will safeguard benefits and personal information, ultimately improving the veteran experience and reducing improper payments.
Opponents contend
Critics might raise concerns about the potential for increased barriers to access for certain veteran populations, such as those in rural areas, with disabilities, or limited digital literacy, if new authentication methods are too complex or inaccessible. There could also be questions about the adequacy of the allocated funding and the feasibility of integrating new commercial solutions with existing VA infrastructure within the two-year pilot timeframe.
The bill is concise and straightforward, making it accessible for a quick read and understanding of its core purpose and mechanisms.
Section 2(a)
Establishment of Pilot Program for Digital Identity Modernization
This provision directs the Secretary of Veterans Affairs to create a pilot program to update the VA's digital identity verification and authentication systems. The program's goals include replacing old, single-factor verification with more secure, multi-layered digital solutions, reducing fraud, improving secure access for veterans to VA digital platforms, and evaluating cost savings and efficiency before any widespread implementation.
Supporters argue
Supporters argue this pilot is essential for bringing the VA's digital security up to modern standards, protecting veterans from identity theft and fraud, and streamlining access to benefits through reliable authentication. It represents a proactive step towards a more secure and efficient digital government.
Critics contend
No specific opposition is typically raised against the general concept of modernizing digital security. However, some might express concern that the implementation could inadvertently create new hurdles for veterans, particularly those less familiar with digital technologies or lacking consistent internet access, if not carefully managed.
Tradeoffs
The bill seeks to balance enhanced security with user accessibility. More rigorous authentication can deter fraud but might also increase complexity for some users. The pilot program aims to test this balance.
Section 2(d)
Standards for Digital Identity Solutions
This section mandates that any digital identity solution implemented under the pilot program must be commercially available, not custom-built for the VA, and independently certified to meet or exceed Identity Assurance Level 2 (IAL2) and Authentication Assurance Level 2 (AAL2) standards, as defined by the National Institute of Standards and Technology (NIST) Special Publication 800-63. It also requires compliance with federal cybersecurity and privacy laws.
Section 2(e)
Funding for the Pilot Program
This section specifies that the pilot program can obligate or expend a maximum of $25,000,000 in aggregate. Crucially, these funds must come from amounts already authorized to be appropriated for 'Information Technology Systems' under chapter 57 of title 38, United States Code. The bill explicitly states that no additional funds are authorized to be appropriated for this section, meaning it must operate within existing VA IT budgets.
Section 2(g)
GAO Evaluation and Report
This provision directs the Comptroller General of the United States (GAO) to conduct an independent evaluation of the pilot program within 18 months of the bill's enactment. The GAO report must assess various aspects, including compliance with NIST standards, fraud reduction, impact on veteran access (especially for rural, disabled, or digitally illiterate veterans), cost-benefit analysis, cybersecurity compliance, and the feasibility of scaling the program. The GAO will also provide recommendations on whether to expand, modify, or discontinue the pilot.
The Secretary shall select 'not more than three high-volume digital service platforms' for participation, which 'may consist of one or more underlying systems, applications, or services.' Examples include disability compensation, health care enrollment, educational benefits, or home loan benefits systems.
Section 2(b)
Why it matters:This is standard legislative practice to provide flexibility to the implementing agency while setting clear boundaries for the pilot's scale.
Case for: Supporters argue that limiting the pilot to a maximum of three high-volume platforms allows for focused testing and evaluation without overstretching resources, ensuring a manageable scope for a two-year program. The flexibility to choose which platforms are most critical or ready for modernization is also beneficial.
Case against: Critics might suggest that limiting the pilot to only three platforms, even high-volume ones, might not provide a comprehensive enough understanding of the challenges and benefits across the entire VA digital ecosystem. It could delay modernization for other critical services.
Estimated impact: The pilot will directly impact the digital experience for veterans using up to three of the VA's most frequently accessed online services, potentially affecting millions of users.
The Secretary may not expand the scope or funding cap beyond the levels described in this section unless expressly authorized by a subsequent Act of Congress.
Section 2(h)(2)
Why it matters:This is a common legislative mechanism to prevent executive agencies from unilaterally expanding pilot programs beyond their initial congressional authorization, ensuring legislative control over scope and funding.
Case for: Proponents argue this ensures congressional oversight and prevents mission creep or unauthorized spending increases. It reinforces the pilot nature of the program, requiring a deliberate legislative decision for any expansion.
Case against: Critics might contend that such a strict limitation could hinder agile development or rapid scaling if the pilot proves exceptionally successful and urgent expansion is warranted. It could introduce bureaucratic delays in responding to positive outcomes.
Estimated impact: This provision ensures that any future expansion of the digital identity modernization program beyond the initial pilot will require explicit legislative action, impacting the timeline and political feasibility of broader deployment.