HIGHLIGHTS OF THE NEW GSA AI CLAUSE
Written by Hollie Kapos, Vertosoft, VP Legal & Contracts
On September 28, while we were all focused on federal fiscal year end, GSA dropped a new AI clause that will become effective on October 19, 2026 for GSA procurements by any entity authorized under 40 U.S.C. §§ 501, 502. This includes eligible state and local government entities.
552.239-7001 Basic Safeguarding of Data within Large Language Model Artificial Intelligence Systems is the result of significant industry feedback on the initial and revised drafts released in March and June 2026, respectively.
This is a lengthy clause and, of course, the devil is in the details, so contractors and suppliers should ensure their appropriate stakeholders review in full. In the meantime, I’ve summarized the highlights below.
Product/Service Applicability:
The clause only applies if: (1) LLM functionality is a material feature of the product or service procured, and (2) Government Data (defined in the clause through several definitions) will be submitted directly to or produced by the LLM, either by the Government or on its behalf.
Regarding materiality, the clause provides two conditions under which the clause is inapplicable and self-deleting:
- The LLM is used for “internal business, back-office, operational, or performance-support systems” and not delivered to or accessed by the Government; or
- Functionality is “incidental or ancillary,” meaning AI/LLM functionality is NOT:
(a) the primary purpose of the product,
(b) required by the contract or as part of the product description,
(c) accessed by the Government (covered in the first condition), or
(d) used to process Government Data.
Key Requirements:
The Contractor, and subcontractors as applicable based on the flow down requirements, are required to:
- Disclose LLMs used in contract performance;
- Flow down the clause as applicable;
- Use “best efforts” in conducting diligence when selecting and overseeing Subcontractors performing AI Design, AI Development, AI Deployment, or Operation and Monitoring tasks, as described in NIST AI RMF 1.0 Appendix A;
- Provide a license grant to the Government for use of the LLM (also see Government Rights section below);
- Implement data handling procedures to protect Government Data and restrict access to it, such measures to include:
- Automated data ingestion, processing, and response generation,
- Technical access controls,
- Encryption, and
- Audit logging systems
- Ensure Government Data is stored or processed only as necessary for contract performance;
- Provide tools to enable the Government to maintain processing records;
- Secure and permanently delete Government Data from the LLM upon completion, termination, or expiration of the contract;
- Maximize use of US-controlled LLMs and protect Government Data from foreign compulsion;
- Provide for a means to implement human oversight;
- Provide for portability of Government Data and interoperability with other government systems;
- Logically segregate Government Data from other customer data.
- Notify the CO of discovered security incidents, material changes to the LLM or how it handles Government Data, model deprecation, safety and performance degradation, or emergency or unplanned changes, with varying notification deadlines; and
- Use reasonable efforts to cause the LLM to respond to user prompts with objectivity and prioritizing accuracy, and to acknowledge uncertainty.
There are additional requirements related to Custom Developments, including Government exclusivity.
Prohibitions:
Contractors and Subcontractors (as applicable) are prohibited from any use of Government Data except:
- As needed for performing the contract requirements;
- For purposes of cybersecurity, cyber-defense related fraud prevention, and threat detection, using de-identified, aggregated telemetry that cannot be used to identify the Government or reconstruct Government Data;
- Providing required technical support and maintenance; and
- Other uses expressly authorized in writing by the CO.
Notably, Government Data cannot be used to train, fine-tune, or improve the LLM for other customers or purposes without express CO approval. Additionally, Government Data may not be removed from or transmitted, stored, or accessed by any means other than, the agreed-upon premises or FedRAMP authorized services without CO authorization.
Government Rights
Unsurprisingly, the Government retains full ownership of all Government Data and Custom Developments, while the Contractor’s rights to the LLM, pre-existing IP, and other background information are retained by the Contractor. However, the Government also retains ownership of all feedback it provides to the Contractor regardless of how the feedback is generated, including generation by the Contractor. Furthermore, the Government has the right to conduct automated assessments of the LLM using its own benchmarks, which, along with test data and underlying methodologies, are considered Government Data that the Government is under no obligation to disclose.
Effect of Non-Compliance
A breach of this clause can result in decommissioning costs if not cured after notice. Decommissioning costs must be reasonable, exclude costs for re-procurement and replacement system development, and are capped at 25% of the value of the affected order.
What’s Next
Given the start date of October 19, 2026, we expect contractors will soon see the clause in new contracts and modifications, and suppliers and subcontractors will receive resulting flow downs and reps and certs requests from primes and higher tier subcontractors. So now would be a great time to assess your product offerings for applicability and whether you can meet the requirements.