Software supply chain security: SBOMs, attestation and device rules, outlook to 2027

Washington has made secure-development attestation optional while SBOM guidance tightens, FDA already demands SBOMs for connected devices, and the EU's Cyber Resilience Act makes them law for products sold in Europe.

The question for 2027

What banks, health systems and public agencies demand of software suppliers is now shaped by three forces: federal guidance that has stepped back from a single mandatory form, a device statute that already requires a software bill of materials (SBOM), and an EU regulation that makes SBOMs and vulnerability reporting law for products sold in Europe. All statuses are as checked on November 16, 2026. This piece describes official texts; it is not legal advice.

Federal attestation: from one form to each agency's choice

CISA released the Secure Software Development Attestation Form on March 11, 2024, built on NIST's Secure Software Development Framework (SSDF), to carry out Executive Order 14028 and OMB memoranda M-22-18 and M-23-16, under which producers of software used by the federal government were to confirm specific security practices [2]. OMB Memorandum M-26-05, dated January 23, 2026, rescinded both memoranda, saying M-22-18 "imposed unproven and burdensome software accounting processes that prioritized compliance over genuine security investments" [1]. As checked on November 16, 2026, CISA's page for the form is marked as archived content [2].

The memo did not end the tools. Agencies must still keep a complete inventory of software and hardware and set assurance policies that match their risk and mission; in the memo's words, agencies "may choose to use the government-wide secure software development resources developed under M-22-18, such as the Secure Software Development Attestation Form," and "may also choose to adopt contractual terms that require a software producer to provide a current software bill of materials (SBOM) upon request" [1]. For a cloud platform, the memo says such a term should require an SBOM of the runtime production environment [1]. Our federal cloud and cyber procurement outlook covers the procurement side.

The executive orders moved in the same direction. Executive Order 14306 of June 6, 2025 struck subsections 2(a) and 2(b) of Executive Order 14144 and rewrote its software provisions as tasks for NIST: an industry consortium on implementing the SSDF by August 1, 2025, a preliminary SSDF update by December 1, 2025, and a final version within 120 days of that preliminary update [9].

Moraph's view

Moraph's view: proof of secure development has become a buying decision for each agency rather than a government-wide checkbox. Agencies with large security offices will keep asking for attestation evidence through solicitations. The SBOM-on-request term is the clause we expect to spread fastest, since OMB named it and it costs an agency nothing to add.

NIST's framework: version 1.2 is still a draft

SP 800-218, SSDF Version 1.1, published in February 2022, remains NIST's final version [7]. NIST published SP 800-218 Rev. 1, SSDF Version 1.2, as an initial public draft on December 17, 2025; comments closed on January 30, 2026, and as checked on November 16, 2026 the publication page still shows it as a draft [8]. The draft describes new and improved practices, tasks and examples for the secure and reliable development, delivery and improvement of software [8]. NIST has also finalized SP 800-218A, an SSDF community profile for generative AI and dual-use foundation models [17]. M-26-05 still names SP 800-218 and its appendices as a reference for agencies [1].

Moraph's view

Moraph's view: by our reading of the dates, the order's 120-day window for a final version closed in April 2026 without one. We expect version 1.2 to be final in 2027. It will then become the yardstick in agency, bank and insurer questionnaires.

SBOM minimum elements: the 2021 baseline is replaced

The National Telecommunications and Information Administration published the first minimum elements for an SBOM on July 12, 2021 [18] [5]. CISA published a draft update on August 22, 2025 and took comments until October 3, 2025 [3]. On July 29, 2026, CISA, the NSA, the FBI and 15 partner agencies from Australia, Canada, India, Japan, New Zealand, South Korea and seven European countries released the 2026 Minimum Elements, which update and replace the NTIA document [4] [5].

The new list adds an SBOM author signature, data format name and version, generation context, tool name and version, an SBOM version, a component hash value and algorithm, and component license [5]. "Supplier name" becomes "component producer", and the old "depth" element, which covered top-level dependencies only, becomes "coverage", which expects all components including transitive dependencies [5]. Software identification tags are dropped as a data format, leaving SPDX and CycloneDX as the formats the guidance calls widely used [5]. The document says the minimum elements do not create new requirements and instead refine how organizations should generate and request SBOMs [5]. It names software as a service and AI as areas that may need more elements [5], and CISA and G7 partners issued separate minimum elements for AI on May 12, 2026 [6].

SBOM minimum elements: the 2021 baseline is replaced
Source of the dutyWho it reachesWhat it says about SBOMsStatus as checked on November 16, 2026
OMB M-26-05Federal agencies buying softwareAgencies may require a current SBOM on request by contract [1]Issued January 23, 2026; rescinds M-22-18 and M-23-16 [1]
CISA 2026 Minimum ElementsOrganizations that produce, procure or operate softwareGuidance; creates no new requirements [5]Published July 29, 2026 [4]
FD&C Act section 524BSponsors of premarket submissions for cyber devicesSBOM provided to FDA [10]Effective 90 days after December 29, 2022 [10]
EU Cyber Resilience ActManufacturers of products with digital elements sold in the EUSBOM covering at least top-level dependencies, kept in technical documentation [13]Main obligations apply from December 11, 2027 [13] [14]
New York DFS cybersecurity regulationFinancial companies licensed by DFSNo SBOM named; secure development and evaluation of external applications [16]Second amendment effective November 1, 2023 [16]

Moraph's view

Moraph's view: the gap that matters is between the EU's legal floor and the US guidance. The Cyber Resilience Act requires top-level dependencies at least; the 2026 US guidance expects every component. A supplier that builds to the 2026 guidance clears the EU floor, but not the other way round. We expect hospital and bank contracts to cite the 2026 minimum elements in 2027, because they are the only common yardstick, though they bind no one by themselves.

Medical devices: section 524B is already the hard rule

Section 524B of the Food, Drug, and Cosmetic Act applies to premarket submissions for a "cyber device": one that includes software, can connect to the internet, and has characteristics that could be vulnerable to cybersecurity threats [10]. The sponsor must submit a plan to monitor and address postmarket vulnerabilities, including coordinated vulnerability disclosure; maintain processes that give reasonable assurance the device is cybersecure and make updates and patches available; and provide FDA a software bill of materials that includes commercial, open-source and off-the-shelf components [10]. The section took effect 90 days after its enactment on December 29, 2022, and FDA may exempt devices by publishing a list in the Federal Register [10].

FDA issued its current final premarket cybersecurity guidance on February 2, 2026, revised to align with the Quality Management System Regulation amendments to 21 CFR 820 [12]. It supersedes the version of June 27, 2025, which had added FDA's recommendations on section 524B [11] [12]. In Europe, the Cyber Resilience Act does not apply to products covered by the EU medical device and in vitro diagnostic regulations [13]. Our medical device cybersecurity comparison sets the rules side by side.

Moraph's view

Moraph's view: device makers have been handing SBOMs to FDA since 2023, so health systems are the buyers best placed to demand the same file in a purchase contract. We expect more hospital contracts to require the SBOM and the patching commitments already given to FDA, and we see no sign that FDA will narrow the statute's reach before 2028.

The EU Cyber Resilience Act reaches US vendors

Regulation (EU) 2024/2847 applies to products with digital elements made available on the EU market whose intended or foreseeable use includes a data connection to a device or network [13]. Its duties follow the product, not the manufacturer's home country: importers may place on the market only products whose manufacturer has carried out conformity assessment and drawn up technical documentation [13]. The regulation entered into force on December 10, 2024 [14]. Chapter IV, on the notification of conformity assessment bodies, applied from June 11, 2026; the reporting duties in Article 14 from September 11, 2026; and the rest from December 11, 2027 [13].

Reporting is already live. A manufacturer must send an early warning of an actively exploited vulnerability within 24 hours of becoming aware of it, a notification within 72 hours, and a final report no later than 14 days after a corrective or mitigating measure is available [13]. Severe incidents follow the same 24-hour and 72-hour steps, with a final report within a month of the notification [15]. The reporting duty also covers products placed on the market before December 11, 2027 [13], and ENISA's single reporting platform has operated since September 11, 2026 [15].

On SBOMs, Annex I requires manufacturers to draw one up "in a commonly used and machine-readable format covering at the very least the top-level dependencies" [13]. It sits in the technical documentation and goes to a market surveillance authority on a reasoned request; sharing it with users is the manufacturer's choice [13]. The support period must generally be at least five years [13]. The Commission may specify the SBOM's format and elements by implementing act [13], and it published practical guidance for manufacturers on July 27, 2026 [14].

Moraph's view

Moraph's view: for a US software company with any EU sales, the Cyber Resilience Act, not a US rule, is the first binding SBOM and vulnerability-reporting duty for general-purpose software, and its reporting clock is already running. US buyers gain second-hand: few vendors will run two SBOM pipelines, so files built for Europe will be offered to everyone.

Financial regulators: software duties without the word SBOM

New York's cybersecurity regulation requires written procedures for secure development of in-house applications and for evaluating, assessing or testing the security of externally developed applications, reviewed at least annually by the CISO or a qualified designee [16]. Section 500.11 requires third-party service provider policies covering minimum cybersecurity practices, due diligence, periodic assessment, and contract guidelines that include representations and warranties on the provider's cybersecurity [16]. Neither section mentions SBOMs or attestation forms [16]. As checked on November 16, 2026 we found no official statement by a federal banking agency that requires SBOMs; federal third-party risk guidance for banks is covered in our third-party risk outlook.

What to watch in 2027

  • A final SSDF version 1.2 from NIST [8] [9].
  • December 11, 2027, when the Cyber Resilience Act's main obligations apply, and any Commission implementing act on SBOM format [13].
  • Agency solicitations that adopt the SBOM-on-request term named in M-26-05 [1].
  • Further CISA work on SBOM elements for software as a service and cloud software [5].
  • Cryptographic inventories, the next bill of materials buyers will ask for, tracked in our post-quantum migration outlook.

Moraph's view

Moraph's view: by the end of 2027 an SBOM will be a legal requirement for US medical devices and for connected products and software sold in the EU, and a common contract term almost everywhere else. Secure development attestation, by contrast, becomes something each buyer negotiates. We see no US statute making SBOMs mandatory for commercial software before 2028.

What this means for you

  • Software vendors: Keep SSDF-based attestation evidence even where no form is required, since agencies may still use the form [1]. If any product reaches the EU, the Article 14 reporting duty already applies to it [13] [15]; building SBOMs to the 2026 minimum elements, which expect all components, also covers the EU's top-level-dependency floor [5] [13].
  • Health systems: Ask device makers for the SBOM and postmarket vulnerability plan they already give FDA under section 524B [10], and write update and patch commitments into purchase contracts.
  • Banks, credit unions and insurers: New York-licensed firms must already evaluate the security of externally developed applications and set minimum practices and contract terms for providers [16]; an SBOM request is one way to evidence that work, not a named requirement.
  • Public agencies: Decide, application by application, whether to keep using the attestation form and whether to add the SBOM-on-request term; for cloud services, M-26-05 says the term should cover the runtime production environment [1].

Moraph predictions

Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.

  1. P1 By Confidence 70% Open

    NIST publishes SP 800-218 Rev. 1 (SSDF Version 1.2) as a final publication.

    How we will check: The CSRC page for SP 800-218 Rev. 1 shows a final publication (not a draft) with a date on or before December 31, 2027.

    Basis: The initial public draft was published December 17, 2025 and its comments closed January 30, 2026 [8]; Executive Order 14306 called for a final version within 120 days of the preliminary update [9].

  2. P2 By Confidence 70% Open

    The EU Cyber Resilience Act's main obligations apply on December 11, 2027, without a postponement.

    How we will check: No regulation amending the December 11, 2027 application date in Article 71(2) of Regulation (EU) 2024/2847 is published in the Official Journal on or before December 11, 2027.

    Basis: The regulation sets December 11, 2027 for its main obligations [13], and the Commission's page, last updated September 7, 2026, still gives that date [14].

  3. P3 By Confidence 85% Open

    OMB does not issue a new government-wide memorandum that requires software producers to submit a secure software development attestation to agencies.

    How we will check: No OMB memorandum issued on or before December 31, 2027 requires agencies to obtain a secure software development attestation from software producers.

    Basis: M-26-05 rescinded M-22-18 and M-23-16 and left use of the attestation form to each agency [1]; CISA's form page is marked archived [2].

  4. P4 By Confidence 50% Open

    CISA, alone or with partner agencies, publishes guidance setting SBOM elements specific to software as a service or cloud software.

    How we will check: A CISA publication dated on or before June 30, 2028 sets out SBOM minimum or additional elements specifically for SaaS or cloud software.

    Basis: The 2026 Minimum Elements name SaaS in cloud environments as an area that may need additional elements [5], and CISA issued separate AI elements with G7 partners in May 2026 [6].

Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.

Spotted an error? Tell us and we will check it and correct the piece where needed.

  • software bill of materials
  • SBOM
  • secure software development
  • SSDF
  • attestation
  • OMB M-26-05
  • FDA section 524B
  • Cyber Resilience Act
  • NYDFS Part 500