Finite StateFinite State
Finite StateFinite State
SBOM is (still) coming: Examining the Proposed FAR Amendments
Compliance & Regulations

SBOM is (still) coming: Examining the Proposed FAR Amendments

The DoD, GSA, and NASA are proposing amendments to the Federal Acquisition Regulation. These proposed changes are open for public comment until December 4.

Finite State Team

Finite State Team

October 13, 2023

Last week, the Department of Defense (DoD), General Services Administration (GSA), and National Aeronautics and Space Administration (NASA) took a significant step forward when they issued proposed amendments to the Federal Acquisition Regulation (FAR). These proposed changes, grounded in Executive Order (E.O.) 14028 and open for comment until December 4, 2023, would impose SBOMs as an explicit requirement for software purchased through federal contracts.

While SBOMs do not represent a complete solution to the Government's ever-expanding cyber threatscape, the intent of the changes is to enhance the security of Government networks and promote cybersecurity collaboration between the Government and its contractors.

What's prompting the proposed FAR amendments? 

Recent major cybersecurity incidents, such as the data breaches involving SolarWinds, Microsoft Exchange, and Colonial Pipeline, make clear the pressing need for robust cybersecurity measures. These events underscore the necessity for modernizing and strengthening our cybersecurity framework in the face of threats from both cyber criminals and nation-state actors.

What the FAR amendments mean for SBOM

 A significant component of the proposed amendments would require government contractors to develop and maintain a Software Bill of Materials (SBOM) for software sold to the federal government. 

SBOMs, as formal records detailing the components used in software development, play a crucial role in incident response, enabling prompt identification of vulnerabilities. They can also evidence transparency within the software development process and a vendor's commitment to secure development practices.

However, the introduction of SBOMs raises several pertinent questions:

  • Protection & Collection: What safeguards should be in place to protect the data within SBOMs? Some software producers worry that SBOMs could provide a leg-up to malicious actors in selecting targets and shaping attacks.
  • Scope: To ensure appropriate security, we must determine the right balance in the depth and breadth of information within SBOMs. 
  • Challenges: As with any change, challenges exist, especially for software resellers and in relation to legacy software. For this initiative to succeed, we must address these challenges head-on.
  • Updates: Software is not static. SBOM Management becomes critical in order to get updates, particularly after major releases or new builds.

The DoD, GSA, and NASA, in acknowledging the potential effects of this new SBOM requirement, have put forth similar questions as part of the notice-and-comment process to collect input from interested parties through December 4, 2023. 

The FAR amendments - Beyond SBOM

The proposed rule isn't solely about SBOMs. It requires contractors to subscribe to the automated indicator sharing (AIS) capability and share cyber threat indicators. Such measures, although potentially demanding on contractors, reflect a holistic approach to cybersecurity, ensuring both proactive and reactive mechanisms are in place.

What could the FAR amendments mean for contractors?

These proposed changes underscore the significance the federal government places on cybersecurity. Compliance with the new requirements, once finalized, could determine eligibility (and be a requirement for payment) under Government contracts. This new regime signifies that cybersecurity is no longer just an IT concern — it's a business imperative.

For both government and private sector, the looming threat of cybersecurity incidents has become a fact of life and business. Though it hardly represents a complete solution, the SBOM has become something of a proxy for security - acting both as a measure of transparency and an indication of a commitment to secure software development practices.

For some, this may be an unwelcome and burdensome requirement, but there is no denying that developing and leveraging SBOMs is quickly becoming a common requirement, and government is leading the way

While we will have to wait for the final rule to see exactly how this particular requirement takes shape, the handwriting is very clearly on the wall (or at least in the Federal Register).

Tags

#regulation
Finite State Team

Finite State Team

The Finite State team brings together experts in cybersecurity, embedded systems, and software supply chain risk to help connected device manufacturers secure their products and comply with evolving global regulations.

Related Articles

Road to Compliance: First Steps OEMs and Suppliers Should Take Today

The Road to Compliance: First Steps OEMs and Suppliers Should Take Today

Learn how to achieve Connected Vehicle Rule compliance with six actionable steps — from SBOM & HBOM generation to supplier engagement and risk evaluat...

Oct 20, 2025
Legacy Software & CVR Compliance Carveouts Explained

Legacy Software & CVR Compliance Carveouts Explained

Learn how legacy carveouts and specific authorizations can help you comply with CVR—while time-limited, they demand proactive planning now.

Oct 16, 2025
Regulations Driving IoT Security Forward

Regulations Driving IoT Security Forward

From EU CRA to FDA 524B, IoT regulations are reshaping the market. Learn what manufacturers need for compliance—SBOMs, testing, and supply chain visib...

Sep 24, 2025

Ready to Level Up Your Security Knowledge?

Join thousands of security professionals learning from the best in the industry

Start Learning TodayStart Learning Today
Finite StateFinite State

Finite State is the Product Security Automation Platform that functions as an autonomous Product Security OS: design → verify → prove, grounded in what you ship.

Platform

Platform Overview
Ground Truth Inventory
Exploitability-Based Prioritization
Design-Time Architecture Security
Automated Evidence-Backed Compliance

Solutions

Device Manufacturers
Automotive
Medical Devices
Energy & Utilities
Government
Industrial

Resources

Blog
Resource Library
Webinars & Videos
Events
Documentation

Company

About Us
CareersHIRING
Press & Media
Contact Sales
X

Privacy PolicyTerms of UseCustomer Terms and Conditions