Connect with us

Hi, what are you looking for?

SecurityWeekSecurityWeek

Artificial Intelligence

G7 Countries Release AI SBOM Guidance

The goal of the guidance, which outlines minimum elements, is to help organizations enhance transparency in AI systems and supply chains. 

Are SBOMs Failing?

Government agencies from Group of Seven (G7) countries this week published joint guidance to help organizations create a software bill of materials (SBOM) for AI.

An SBOM is a detailed, machine-readable manifest that catalogs every component, library, dependency, and module incorporated into a software product to provide full transparency into its composition.

Government agencies have been working on updated SBOM guidance and they have been pushing for the widespread adoption of SBOMs to bolster cybersecurity.

Agencies in the United States, Canada, Japan, Germany, France, Italy, the United Kingdom, and the European Union have now published SBOM guidance focusing on AI.

The newly released document, named ‘Software Bill of Materials for AI – Minimum Elements’, aims to help public and private sector organizations enhance transparency in their AI systems and supply chains.

According to its authors, it provides actionable guidelines for AI developers and deployers, making it easier to track vulnerabilities and reduce risks. 

Advertisement. Scroll to continue reading.

The document outlines seven main clusters that should be present in an SBOM for AI: metadata, models, key performance indicators (KPI), infrastructure, security properties (SP), system level properties (SLP), and dataset properties (DP).

The metadata cluster should include elements about the SBOM itself, including its author, version, data format, author signature, tool name and version, generation context, timestamp, and dependency relationship.

The SLP cluster should contain information about the AI system, including name, producer, version, components, timestamp, data flow and usage, input/output properties, and intended application area.

The guidance recommends creating a models cluster that contains information about the models used by the AI, including name, identifier, version, producer, description, timestamp, hash value and algorithm, properties, license, and external references.

The DP cluster should include information about the datasets used by the model. The infrastructure cluster contains information about the software and hardware used to operate and support the AI system.

SP should cover security controls, security compliance, cybersecurity policy information, and vulnerability referencing, while the KPI cluster should contain information on security metrics and operational performance.

[ Read: Are SBOMs Failing? Security Teams Struggling With SBOM Data ]

The authoring agencies noted, “These minimum elements are not mandatory; do not create requirements, standards, or legislation; and are open to further refinements to keep pace with technological development and evolution of legal or policy frameworks within G7 members.”

Nigel Douglas, head of developer relations at artifact management and software supply chain security firm Cloudsmith, commented on the new AI SBOM guidance, noting that “The G7 framework raises the right requirements, but organizations trying to implement them will find that documentation applied retrospectively doesn’t reconstruct origin.”

“Continuous, automated SBOM generation is already a baseline requirement for organizations serious about software supply chain security, and the G7’s new AI SBOM framework extends that logic into territory where the tooling and governance haven’t caught up yet. To its credit, the guidance is being candid about its own limits, acknowledging that most of its seven data clusters are difficult to measure consistently across organizations,” Douglas said.

“Where it runs into difficulty is structural, rooted in how systems are being built. GenAI tools have made it routine for developers to create applications or pull in software dependencies outside any formal review pipeline. 

“Meanwhile, traditional SBOMs were designed for supply chains with relatively traceable edges but AI-assisted development is producing code, workflows, and dependencies that may enter production without ever passing through established inventory or assurance processes – a dynamic that attacks like s1ngularity have already begun to exploit directly,” he added.

Related: SBOM Pioneer Allan Friedman Joins NetRise to Advance Supply Chain Visibility

Related: Global Cyber Agencies Issue AI Security Guidance for Critical Infrastructure OT

Written By

Eduard Kovacs (@EduardKovacs) is senior managing editor at SecurityWeek. He worked as a high school IT teacher before starting a career in journalism in 2011. Eduard holds a bachelor’s degree in industrial informatics and a master’s degree in computer techniques applied in electrical engineering.

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing for the latest cybersecurity threats, trends, and expert insights.

Trending

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts.

Today’s attackers are no longer breaking in — they’re logging in. Join this live webinar as we break down the modern identity attack chain and examine how recent breaches exploited weaknesses in authentication, identity verification, and access management processes.

Register

AI has accelerated both sides of the fight. Adversaries are weaponizing vulnerabilities faster, while defenders are racing to ship detections and configurations. Join this live webinar as we explore how to prove your controls actually hold against new threats, map your security maturity, and unite breach simulation with automated pentesting into a single, coordinated program.

Register

People on the Move

Stephen Garcia has been named Chief Information Security Officer at BreachRx.

Kasper Lindgaard has been appointed Vice President of Security Strategy at CoreView.

Chaim Mazal has been named Chief Information Security Officer at GitLab.

More People On The Move

Expert Insights

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest cybersecurity news, threats, and expert insights. Unsubscribe at any time.