Technical corrections only. The diff between v2 and v3 reflects minor procedural updates related to the bill's passage through Congress, including the clerk's name and referral to a Senate committee. There are no substantive policy changes to the bill text itself.
Strengthening Agency Management and Oversight of Software Assets Act
- Sponsor
- Rep. Brown, Shontel M. [D-OH-11]
- Committees
- Homeland Security and Governmental Affairs Committee (primary)
- Last action
- Dec 16, 2025
Bottom line
This bill aims to improve federal government efficiency and reduce wasteful spending on software by requiring better inventory, planning, and management of software assets across agencies.
What it actually does
This bill mandates federal agencies to conduct comprehensive assessments of their software assets, including entitlements, usage, costs, and interoperability. It requires agencies to develop detailed plans for modernizing software management, consolidating licenses, and improving acquisition strategies to reduce costs and enhance performance. The bill also establishes specific reporting requirements for these assessments and plans to Congress and relevant federal offices.
Proponents argue
Supporters argue that the bill will lead to significant cost savings for taxpayers by eliminating redundant software licenses, improving negotiation power with vendors, and ensuring agencies only pay for software they actually use. They contend it will enhance cybersecurity by providing better visibility into software deployed across the government and improve operational efficiency through increased interoperability and standardized practices.
Opponents contend
Critics might argue that the comprehensive assessment and planning requirements impose a significant administrative burden on agencies, potentially diverting resources from core missions. They might also raise concerns about the feasibility of achieving interoperability across diverse legacy systems and the potential for increased costs in the short term due to the initial investment required for these assessments and new management systems.
The bill is relatively short and clearly structured, making it accessible for a reader to understand its core provisions and implications within a reasonable timeframe.
Section 3(a)
Mandated Comprehensive Software Assessment
This provision requires each agency's Chief Information Officer (CIO), in consultation with other key officials, to conduct a thorough review of all software paid for, in use, or deployed by the agency within 18 months of the bill's enactment. The assessment must detail current software inventory, including entitlements and contracts, identify unused or duplicated software, categorize software by cost and type, list usage restrictions, and analyze management accuracy and compliance.
Supporters argue
Supporters argue this assessment is crucial for establishing a baseline understanding of agency software landscapes, identifying inefficiencies, and laying the groundwork for significant cost reductions and improved operational effectiveness across the federal government.
Critics contend
Critics might argue that conducting such a comprehensive assessment is a massive undertaking, potentially requiring substantial upfront investment in personnel or external contractors, which could strain agency budgets and divert resources from other critical IT initiatives.
Tradeoffs
The tradeoff is between the immediate administrative cost and effort of conducting a detailed assessment versus the long-term benefits of improved software management and potential cost savings from identifying and eliminating redundancies.
Section 4(a), (b)
Agency Software Modernization Planning
This section mandates that agencies use the information gathered from their comprehensive software assessments to develop a modernization plan within one year. These plans must outline strategies for consolidating software entitlements, adopting cost-effective acquisition methods like enterprise licensing, and restricting unauthorized software acquisition. Key elements include remediation of deficiencies, ongoing maintenance, automation of license management, staff training on software acquisition, and maximizing software effectiveness and interoperability.
The bill defines 'agency' to exclude elements of the intelligence community. For these excluded entities, comprehensive assessments are conducted separately by designated internal entities, ensuring national security protection, and are submitted in summary form to specific intelligence committees of Congress, rather than the broader oversight committees.
Section 2(2) and Section 3(f)
Why it matters:This is standard legislative practice for national security carve-outs, designed to protect classified information and sensitive operations while still ensuring a form of specialized oversight by relevant intelligence committees.
Case for: Proponents argue this carve-out is essential for protecting classified information and national security operations, ensuring that sensitive intelligence activities are not inadvertently exposed through public reporting requirements or general oversight channels.
Case against: Critics might argue that while necessary for national security, such exclusions can reduce overall transparency and accountability for a significant portion of federal IT spending, potentially allowing for less rigorous oversight in areas that could still benefit from efficiency improvements.
Estimated impact: This provision affects the scope of public transparency and general congressional oversight for a substantial segment of federal IT spending and operations, directing it instead to specialized intelligence committees.