Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
An optional name of the advisory.
Location where the advisory can be obtained.
Used in:
The relationship completeness is not specified.
The relationship is complete. No further relationships including constituent components, services, or dependencies are known to exist.
The relationship is incomplete. Additional relationships exist and may include constituent components, services, or dependencies.
The relationship is incomplete. Only relationships for first-party components, services, or their dependencies are represented.
The relationship is incomplete. Only relationships for third-party components, services, or their dependencies are represented.
The relationship may be complete or incomplete. This usually signifies a 'best-effort' to obtain constituent components, services, or dependencies but the completeness is inconclusive.
The relationship is incomplete. Only relationships for first-party components, services, or their dependencies are represented, limited specifically to those that are proprietary.
The relationship is incomplete. Only relationships for first-party components, services, or their dependencies are represented, limited specifically to those that are opensource.
The relationship is incomplete. Only relationships for third-party components, services, or their dependencies are represented, limited specifically to those that are proprietary.
The relationship is incomplete. Only relationships for third-party components, services, or their dependencies are represented, limited specifically to those that are opensource.
Used in:
An optional identifier which can be used to reference the annotation elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
The object in the BOM identified by its bom-ref. This is often a component or service, but may be any object type supporting bom-refs.
The organization, person, component, or service which created the textual content of the annotation.
The date and time (timestamp) when the annotation was created.
The textual content of the annotation.
Used in:
The organization that created the annotation
The person that created the annotation
The tool or component that created the annotation
The service that created the annotation
Specifies attributes of the text
Used in:
, , , , , , , , ,Specifies the content type of the text. Defaults to 'text/plain' if not specified.
Specifies the optional encoding the text is represented in
SimpleContent value of element. Proactive controls such as input validation and sanitization should be employed to prevent misuse of attachment text.
The version of the CycloneDX specification a BOM is written to (starting at version 1.3)
The version allows component publishers/authors to make changes to existing BOMs to update various aspects of the document such as description or licenses. When a system is presented with multiple BOMs for the same component, the system should use the most recent version of the BOM. The default version is '1' and should be incremented for each version of the BOM that is published. Each version of a component should have a unique BOM and if no changes are made to the BOMs, then each BOM will have a version of '1'.
Every BOM generated should have a unique serial number, even if the contents of the BOM being generated have not changed over time. The process or tool responsible for creating the BOM should create random UUID's for every BOM generated.
Provides additional information about a BOM.
Provides the ability to document a list of components.
Provides the ability to document a list of external services.
Provides the ability to document external references related to the BOM or to the project the BOM describes.
Provides the ability to document dependency relationships.
Compositions describe constituent parts (including components, services, and dependency relationships) and their completeness. The completeness of vulnerabilities expressed in a BOM may also be described.
Vulnerabilities identified in components or services.
Comments made by people, organizations, or tools about any object with a bom-ref, such as components, services, vulnerabilities, or the BOM itself. Unlike inventory information, annotations may contain opinion or commentary from various stakeholders.
Specifies optional, custom, properties
Describes how a component or service was manufactured or deployed. This is achieved through the use of formulas, workflows, tasks, and steps, which declare the precise steps to reproduce along with the observed formulas describing the steps which transpired in the manufacturing process.
Evidence of the components use through the callstack.
Used in:
Used in:
A package organizes modules into namespaces, providing a unique namespace for each type it contains.
A module or class that encloses functions/methods and other code.
A block of code designed to perform a particular task.
Optional arguments that are passed to the module or function.
The line number the code that is called resides on.
The column the code that is called resides.
The full path and filename of the module.
Used in:
A software application. Refer to https://en.wikipedia.org/wiki/Application_software for information about applications.
A software framework. Refer to https://en.wikipedia.org/wiki/Software_framework for information on how frameworks vary slightly from libraries.
A software library. Refer to https://en.wikipedia.org/wiki/Library_(computing) for information about libraries. All third-party and open source reusable components will likely be a library. If the library also has key features of a framework, then it should be classified as a framework. If not, or is unknown, then specifying library is recommended.
A software operating system without regard to deployment model (i.e. installed on physical hardware, virtual machine, image, etc) Refer to https://en.wikipedia.org/wiki/Operating_system
A hardware device such as a processor, or chip-set. A hardware device containing firmware should include a component for the physical hardware itself, and another component of type 'firmware' or 'operating-system' (whichever is relevant), describing information about the software running on the device. See also the list of known device properties: https://github.com/CycloneDX/cyclonedx-property-taxonomy/blob/main/cdx/device.md
A computer file. Refer to https://en.wikipedia.org/wiki/Computer_file for information about files.
A packaging and/or runtime format, not specific to any particular technology, which isolates software inside the container from software outside of a container through virtualization technology. Refer to https://en.wikipedia.org/wiki/OS-level_virtualization
A special type of software that provides low-level control over a devices hardware. Refer to https://en.wikipedia.org/wiki/Firmware
A special type of software that operates or controls a particular type of device. Refer to https://en.wikipedia.org/wiki/Device_driver
A runtime environment which interprets or executes software. This may include runtimes such as those that execute bytecode or low-code/no-code application platforms.
A model based on training data that can make predictions or decisions without being explicitly programmed to do so.
A collection of discrete values that convey information.
Used in:
A text representation of the executed command.
Domain-specific command properties.
Used in:
A unique identifier of the commit. This may be version control specific. For example, Subversion uses revision numbers whereas git uses commit hashes.
The URL to the commit. This URL will typically point to a commit in a version control system.
The author who created the changes in the commit
The person who committed or pushed the commit
The text description of the contents of the commit
Used in:
, , , , ,Specifies the type of component. For software components, classify as application if no more specific appropriate classification is available or cannot be determined for the component.
The optional mime-type of the component. When used on file components, the mime-type can provide additional context about the kind of file being represented such as an image, font, or executable. Some library or framework components may also have an associated mime-type.
An optional identifier which can be used to reference the component elsewhere in the BOM. Uniqueness is enforced within all elements and children of the root-level bom element.
The organization that supplied the component. The supplier may often be the manufacture, but may also be a distributor or repackager.
The person(s) or organization(s) that authored the component
The person(s) or organization(s) that published the component
The grouping name or identifier. This will often be a shortened, single name of the company or project that produced the component, or the source package or domain name. Whitespace and special characters should be avoided. Examples include: apache, org.apache.commons, and apache.org.
The name of the component. This will often be a shortened, single name of the component. Examples: commons-lang3 and jquery
The component version. The version should ideally comply with semantic versioning but is not enforced. Version was made optional in v1.4 of the spec. For backward compatibility, it is RECOMMENDED to use an empty string to represent components without version information.
Specifies a description for the component
Specifies the scope of the component. If scope is not specified, SCOPE_REQUIRED scope should be assumed by the consumer of the BOM
EITHER (list of SPDX licenses and/or named licenses) OR (tuple of one SPDX License Expression)
An optional copyright notice informing users of the underlying claims to copyright ownership in a published work.
DEPRECATED - DO NOT USE. This will be removed in a future version. Specifies a well-formed CPE name. See https://nvd.nist.gov/products/cpe
Specifies the package-url (PURL). The purl, if specified, must be valid and conform to the specification defined at: https://github.com/package-url/purl-spec
Specifies metadata and content for ISO-IEC 19770-2 Software Identification (SWID) Tags.
DEPRECATED - DO NOT USE. This will be removed in a future version. Use the pedigree element instead to supply information on exactly how the component was modified. A boolean value indicating is the component has been modified from the original. A value of true indicates the component is a derivative of the original. A value of false indicates the component has not been modified from the original.
Component pedigree is a way to document complex supply chain scenarios where components are created, distributed, modified, redistributed, combined with other components, etc.
Provides the ability to document external references related to the component or to the project the component describes.
Specifies optional sub-components. This is not a dependency tree. It provides a way to specify a hierarchical representation of component assemblies, similar to system -> subsystem -> parts assembly in physical supply chains.
Specifies optional, custom, properties
Specifies optional license and copyright evidence
Specifies optional release notes.
A model card describes the intended uses of a machine learning model, potential limitations, biases, ethical considerations, training parameters, datasets used to train the model, performance metrics, and other relevant data useful for ML transparency.
This object SHOULD be specified for any component of type `data` and MUST NOT be specified for other component types.
Used in:
,An optional identifier which can be used to reference the dataset elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
The general theme or subject matter of the data being specified.
The name of the dataset.
The contents or references to the contents of the data being described.
Data classification tags data according to its type, sensitivity, and value if altered, stolen, or destroyed.
A description of any sensitive data in a dataset.
A collection of graphics that represent various measurements.
A description of the dataset. Can describe size of dataset, whether it's used for source code, training, testing, or validation, etc.
Data Governance
Used in:
An optional way to include textual or encoded data.
The URL to where the data can be retrieved.
Provides the ability to document name-value parameters used for configuration.
Used in:
Any type of code, code snippet, or data-as-code
Parameters or settings that may be used by other components.
A collection of data.
Data that can be used to create new instances of what the definition defines.
Any other type of data that does not fit into existing definitions.
Used in:
Indicates the aggregate completeness
The assemblies the aggregate completeness applies to
The dependencies the aggregate completeness applies to
The bom-ref identifiers of the vulnerabilities being described.
An optional identifier which can be used to reference the composition elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
A condition that was used to determine a trigger should be activated.
Used in:
Describes the set of conditions which cause the trigger to activate.
The logical expression that was evaluated that determined the trigger should be fired.
Domain-specific condition instance properties.
Specifies the data flow.
Used in:
Specifies the flow direction of the data.
Data classification tags data according to its type, sensitivity, and value if altered, stolen, or destroyed.
Name for the defined data
Short description of the data content and usage
The URI, URL, or BOM-Link of the components or services the data came in from
The URI, URL, or BOM-Link of the components or services the data is sent to
Data Governance
Specifies the flow direction of the data. Valid values are: inbound, outbound, bi-directional, and unknown. Direction is relative to the service. Inbound flow states that data enters the service. Outbound flow states that data leaves the service. Bi-directional states that data flows both ways, and unknown states that the direction is not known.
Used in:
Used in:
,Data custodians are responsible for the safe custody, transport, and storage of data.
Data stewards are responsible for data content, context, and associated business rules.
Data owners are concerned with risk and appropriate access to data.
Used in:
Used in:
, ,References a component or service by the its bom-ref attribute
Used in:
Specifies the optional text of the diff
Specifies the URL to the diff
Used in:
,Represents something that happened that may trigger a response.
Used in:
The unique identifier of the event.
A description of the event.
The date and time (timestamp) when the event was received.
Encoding of the raw event data.
References the component or service that was the source of the event
References the component or service that was the target of the event
Additional properties of the event.
Used in:
EITHER (list of SPDX licenses and/or named licenses) OR (tuple of one SPDX License Expression)
Used in:
Copyright text
Used in:
Used in:
The identity field of the component which the evidence describes.
The overall confidence of the evidence from 0 - 1, where 1 is 100% confidence.
The methods used to extract and/or analyze the evidence.
The object in the BOM identified by its bom-ref. This is often a component or service, but may be any object type supporting bom-refs. Tools used for analysis should already be defined in the BOM, either in the metadata/tools, components, or formulation.
Used in:
The technique used in this method of analysis.
The confidence of the evidence from 0 - 1, where 1 is 100% confidence. Confidence is specific to the technique used. Each technique of analysis can have independent confidence.
The value or contents of the evidence.
Used in:
An optional identifier which can be used to reference the occurrence elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
The location or path to where the component was found.
Used in:
Used in:
, , , ,Specifies the type of external reference. There are built-in types to describe common references. If a type does not exist for the reference being referred to, use the "other" type.
The URL to the external reference
An optional comment describing the external reference
Optional integrity hashes for the external resource content
Used in:
Use this if no other types accurately describe the purpose of the external reference
Version Control System
Issue or defect tracking system, or an Application Lifecycle Management (ALM) system
Website
Security advisories
Bill-of-material document (CycloneDX, SPDX, SWID, etc)
Mailing list or discussion group
Social media account
Real-time chat platform
Documentation, guides, or how-to instructions
Community or commercial support
Direct or repository download location
The URL to the license file. If a license URL has been defined in the license node, it should also be defined as an external reference for completeness
Build-system specific meta file (i.e. pom.xml, package.json, .nuspec, etc)
URL to an automated build system
Specifies a way to contact the maintainer, supplier, or provider in the event of a security incident. Common URIs include links to a disclosure procedure, a mailto (RFC-2368) that specifies an email address, a tel (RFC-3966) that specifies a phone number, or dns (RFC-4501]) that specifies the records containing DNS Security TXT.
Human or machine-readable statements containing facts, evidence, or testimony
An enumeration of identified weaknesses, threats, and countermeasures, dataflow diagram (DFD), attack tree, and other supporting documentation in human-readable or machine-readable format
The defined assumptions, goals, and capabilities of an adversary.
Identifies and analyzes the potential of future events that may negatively impact individuals, assets, and/or the environment. Risk assessments may also include judgments on the tolerability of each risk.
The location where a component was published to. This is often the same as "distribution" but may also include specialized publishing processes that act as an intermediary
A Vulnerability Disclosure Report (VDR) which asserts the known and previously unknown vulnerabilities that affect a component, service, or product including the analysis and findings describing the impact (or lack of impact) that the reported vulnerability has on a component, service, or product
A Vulnerability Exploitability eXchange (VEX) which asserts the known vulnerabilities that do not affect a product, product family, or organization, and optionally the ones that do. The VEX should include the analysis and findings describing the impact (or lack of impact) that the reported vulnerability has on the product, product family, or organization
Results from an authorized simulated cyberattack on a component or service, otherwise known as a penetration test
SARIF or proprietary machine or human-readable report for which static analysis has identified code quality, security, and other potential issues with the source code
Dynamic analysis report that has identified issues such as vulnerabilities and misconfigurations
Report generated by analyzing the call stack of a running application
Report generated by Software Composition Analysis (SCA), container analysis, or other forms of component analysis
Report containing a formal assessment of an organization, business unit, or team against a maturity model
Industry, regulatory, or other certification from an accredited (if applicable) certification body
Report or system in which quality metrics can be obtained
Code or configuration that defines and provisions virtualized infrastructure, commonly referred to as Infrastructure as Code (IaC)
A model card describes the intended uses of a machine learning model, potential limitations, biases, ethical considerations, training parameters, datasets used to train the model, performance metrics, and other relevant data useful for ML transparency.
Plans of Action and Milestones (POAM) compliment an "attestation" external reference. POAM is defined by NIST as a "document that identifies tasks needing to be accomplished. It details resources required to accomplish the elements of the plan, any milestones in meeting the tasks and scheduled completion dates for the milestones".
A record of events that occurred in a computer system or application, such as problems, errors, or information on current operations.
Parameters or settings that may be used by other components or services.
Information used to substantiate a claim.
Describes how a component or service was manufactured or deployed.
Describes workflows and resources that captures rules and other aspects of how the associated BOM component or service was formed.
Used in:
BOM unique reference to the resource.
Transient components that are used in tasks that constitute one or more of this formula's workflows
Transient services that are used in tasks that constitute one or more of this formula's workflows
List of workflows that can be declared to accomplish specific orchestrated goals and independently triggered.
Domain-specific formula properties.
Used in:
,A description of this collection of graphics.
A collection of graphics.
Used in:
The name of the graphic.
The graphic (vector or raster). Base64 encoding MUST be specified for binary images.
Specifies the file hash of the component
Used in:
, ,Specifies the algorithm used to create the hash
SimpleContent value of element
Used in:
Used in:
The timestamp in which the action occurred
The name of the individual who performed the action
The email address of the individual who performed the action
Used in:
An undefined impact analysis justification
The code has been removed or tree-shaked.
The vulnerable code is not invoked at runtime.
Exploitability requires a configurable option to be set/unset.
Exploitability requires a dependency that is not present.
Exploitability requires a certain environment which is not present.
Exploitability requires a compiler flag to be set/unset.
Exploits are prevented at runtime.
Attacks are blocked at physical, logical, or network perimeter.
Preventative measures have been implemented that reduce the likelihood and/or impact of the vulnerability.
Used in:
An undefined impact analysis state
The vulnerability has been remediated.
The vulnerability has been remediated and evidence of the changes are provided in the affected components pedigree containing verifiable commit history and/or diff(s).
The vulnerability may be directly or indirectly exploitable.
The vulnerability is being investigated.
The vulnerability is not specific to the component or service and was falsely identified or associated.
The component or service is not affected by the vulnerability. Justification should be specified for all not_affected cases.
Type that represents various input data types and formats.
Used in:
, ,A references to the component or service that provided the input to the task (e.g., reference to a service with data flow value of `inbound`)
A reference to the component or service that received or stored the input if not the task itself (e.g., a local, named storage workspace)
A reference to an independent resource provided as an input to a task by the workflow runtime.
Inputs that have the form of parameters with names and values.
Inputs that have the form of parameters with names and values.
Inputs that have the form of data.
Additional properties of the input data.
Used in:
,Specifies the type of issue
The identifier of the issue assigned by the source of the issue
The name of the issue
A description of the issue
Used in:
A fault, flaw, or bug in software
A new feature or behavior in software
A special type of defect which impacts security
Used in:
A valid SPDX license ID
If SPDX does not define the license used, this field may be used to provide the license name
Specifies the optional full text of the attachment
The URL to the attachment file. If the attachment is a license or BOM, an externalReference should also be specified for completeness.
An optional identifier which can be used to reference the license elsewhere in the BOM. Uniqueness is enforced within all elements and children of the root-level bom element.
Licensing details describing the licensor/licensee, license type, renewal and expiration dates, and other important metadata
Specifies optional, custom, properties
Used in:
, , ,Used in:
License identifiers that may be used to manage licenses and their lifecycle
The individual or organization that grants a license to another individual or organization
The individual or organization for which a license was granted to
The individual or organization that purchased the license
The purchase order identifier the purchaser sent to a supplier or vendor to authorize a purchase
The type of license(s) that was granted to the licensee
The timestamp indicating when the license was last renewed. For new purchases, this is often the purchase or acquisition date. For non-perpetual licenses or subscriptions, this is the timestamp of when the license was last renewed.
The timestamp indicating when the current license expires (if applicable).
Used in:
A license that grants use of software solely for the purpose of education or research.
A license covering use of software embedded in a specific piece of hardware.
A Client Access License (CAL) allows client computers to access services provided by server software.
A Concurrent User license (aka floating license) limits the number of licenses for a software application and licenses are shared among a larger number of users.
A license where the core of a computer's processor is assigned a specific number of points.
A license for which consumption is measured by non-standard metrics.
A license that covers a defined number of installations on computers and other types of devices.
A license that grants permission to install and use software for trial purposes.
A license that grants access to the software to one or more pre-defined users.
A license that grants access to the software on one or more pre-defined computers or devices.
An Original Equipment Manufacturer license that is delivered with hardware, cannot be transferred to other hardware, and is valid for the life of the hardware.
A license where the software is sold on a one-time basis and the licensee can use a copy of the software indefinitely.
A license where each installation consumes points per processor.
A license where the licensee pays a fee to use the software or service.
A license that grants access to the software or service by a specified number of users.
Another license type.
Used in:
BOM produced early in the development lifecycle containing inventory of components and services that are proposed or planned to be used. The inventory may need to be procured, retrieved, or resourced prior to use.
BOM consisting of information obtained prior to a build process and may contain source files and development artifacts and manifests. The inventory may need to be resolved and retrieved prior to use.
BOM consisting of information obtained during a build process where component inventory is available for use. The precise versions of resolved components are usually available at this time as well as the provenance of where the components were retrieved from.
BOM consisting of information obtained after a build process has completed and the resulting components(s) are available for further analysis. Built components may exist as the result of a CI/CD process, may have been installed or deployed to a system or device, and may need to be retrieved or extracted from the system or device.
BOM produced that represents inventory that is running and operational. This may include staging or production environments and will generally encompass multiple SBOMs describing the applications and operating system, along with HBOMs describing the hardware that makes up the system. Operations Bill of Materials (OBOM) can provide full-stack inventory of runtime environments, configurations, and additional dependencies.
BOM consisting of information observed through network discovery providing point-in-time enumeration of embedded, on-premise, and cloud-native services such as server applications, connected devices, microservices, and serverless functions.
BOM containing inventory that will be, or has been retired from operations.
Used in:
A pre-defined phase in the product lifecycle.
The name of the lifecycle phase
The description of the lifecycle phase
Used in:
The date and time (timestamp) when the document was created.
The tool(s) used in the creation of the BOM.
The person(s) who created the BOM. Authors are common in BOMs created through manual processes. BOMs created through automated means may not have authors.
The component that the BOM describes.
The organization that manufactured the component that the BOM describes.
The organization that supplied the component that the BOM describes. The supplier may often be the manufacture, but may also be a distributor or repackager.
The license information for the BOM document EITHER (list of SPDX licenses and/or named licenses) OR (tuple of one SPDX License Expression)
Specifies optional, custom, properties
The product lifecycle(s) that this BOM represents.
Used in:
An optional identifier which can be used to reference the model card elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Hyper-parameters for construction of the model.
A quantitative analysis of the model
What considerations should be taken into account regarding the model's construction, training, and application?
Used in:
Who are the intended users of the model?
What are the intended use cases of the model?
What are the known technical limitations of the model? E.g. What kind(s) of data should the model be expected not to perform well on? What are the factors that might degrade model performance?
What are the known tradeoffs in accuracy/performance of the model?
What are the ethical (or environmental) risks involved in the application of this model?
How does the model affect groups at risk of being systematically disadvantaged? What are the harms and benefits to the various affected groups?
Used in:
The name of the risk.
Strategy used to address this risk.
Used in:
The groups or individuals at risk of being systematically disadvantaged by the model.
Expected benefits to the identified groups.
Expected harms to the identified groups.
With respect to the benefits and harms outlined, please describe any mitigation strategy implemented.
Used in:
The overall approach to learning used by the model for problem solving.
Directly influences the input and/or output. Examples include classification, regression, clustering, etc.
The model architecture family such as transformer network, convolutional neural network, residual neural network, LSTM neural network, etc.
The specific architecture of the model such as GPT-1, ResNet-50, YOLOv3, etc.
The datasets used to train and evaluate the model.
The input format(s) of the model
The output format(s) from the model
Used in:
Used in:
References a data component by the components bom-ref attribute
Used in:
The data format for input/output to the model. Example formats include string, image, time-series
Used in:
The model performance metrics being reported. Examples may include accuracy, F1 score, precision, top-3 error rates, MSC, etc.
Used in:
The type of performance metric.
The value of the performance metric.
The name of the slice this metric was computed on. By default, assume this metric is not sliced.
The confidence interval of the metric.
Used in:
The lower bound of the confidence interval.
The upper bound of the confidence interval.
Used in:
Used in:
The ISO-639 (or higher) language code and optional ISO-3166 (or higher) country code. Examples include: "en", "en-US", "fr" and "fr-CA".
Specifies the full content of the release note.
Used in:
, , , , ,The name of the contact
The email address of the contact.
The phone number of the contact.
An optional identifier which can be used to reference the object elsewhere in the BOM. Uniqueness is enforced within all elements and children of the root-level bom element.
Used in:
, , , , , ,The name of the organization
The URL of the organization. Multiple URLs are allowed.
A contact person at the organization. Multiple contacts are allowed.
An optional identifier which can be used to reference the object elsewhere in the BOM. Uniqueness is enforced within all elements and children of the root-level bom element.
Used in:
Used in:
, ,Describes the type of data output.
Component or service that generated or provided the output from the task (e.g., a build tool)
Component or service that received the output from the task (e.g., reference to an artifactory service with data flow value of `outbound`)
A reference to an independent resource generated as output by the task.
Outputs that have the form of data.
Outputs that have the form of environment variables.
Additional properties of the output data.
Used in:
A representation of a functional parameter.
Used in:
The name of the parameter.
The value of the parameter.
The data type of the parameter.
Used in:
Specifies the purpose for the patch including the resolution of defects, security issues, or new behavior or functionality
The patch file (or diff) that show changes. Refer to https://en.wikipedia.org/wiki/Diff
Used in:
A patch which is not developed by the creators or maintainers of the software being patched. Refer to https://en.wikipedia.org/wiki/Unofficial_patch
A patch which dynamically modifies runtime behavior. Refer to https://en.wikipedia.org/wiki/Monkey_patch
A patch which takes code from a newer version of software and applies it to older versions of the same software. Refer to https://en.wikipedia.org/wiki/Backporting
A patch created by selectively applying commits from other versions or branches of the same software.
Component pedigree is a way to document complex supply chain scenarios where components are created, distributed, modified, redistributed, combined with other components, etc. Pedigree supports viewing this complex chain from the beginning, the end, or anywhere in the middle. It also provides a way to document variants where the exact relation may not be known.
Used in:
Describes zero or more components in which a component is derived from. This is commonly used to describe forks from existing projects where the forked version contains a ancestor node containing the original component it was forked from. For example, Component A is the original component. Component B is the component being used and documented in the BOM. However, Component B contains a pedigree node with a single ancestor documenting Component A - the original component from which Component B is derived from.
Descendants are the exact opposite of ancestors. This provides a way to document all forks (and their forks) of an original or root component.
Variants describe relations where the relationship between the components are not known. For example, if Component A contains nearly identical code to Component B. They are both related, but it is unclear if one is derived from the other, or if they share a common ancestor.
A list of zero or more commits which provide a trail describing how the component deviates from an ancestor, descendant, or variant.
A list of zero or more patches describing how the component deviates from an ancestor, descendant, or variant. Patches may be complimentary to commits or may be used in place of commits.
Notes, observations, and other non-structured commentary describing the components pedigree.
Used in:
Precise steps to reproduce the vulnerability.
A description of the environment in which reproduction was possible.
Supporting material that helps in reproducing or understanding how reproduction is possible. This may include screenshots, payloads, and PoC exploit code.
Specifies a property
Used in:
, , , , , , , , , , , , , , , , , , , ,Used in:
,The software versioning type. It is RECOMMENDED that the release type use one of 'major', 'minor', 'patch', 'pre-release', or 'internal'. Representing all possible software release types is not practical, so standardizing on the recommended values, whenever possible, is strongly encouraged.
The title of the release.
The URL to an image that may be prominently displayed with the release note.
The URL to an image that may be used in messaging on social media platforms.
A short description of the release.
The date and time (timestamp) when the release note was created.
Optional alternate names the release may be referred to. This may include unofficial terms used by development and marketing teams (e.g. code names).
Optional tags that may aid in search or retrieval of the release note.
A collection of issues that have been resolved.
Zero or more release notes containing the locale and content. Multiple note messages may be specified to support release notes in a wide variety of languages.
Specifies optional, custom, properties
Used in:
, , , , , ,Used in:
Default
The component is required for runtime
The component is optional at runtime. Optional components are components that are not capable of being called due to them not be installed or otherwise accessible by any means. Components that are installed but due to configuration or other restrictions are prohibited from being called must be scoped as 'required'.
Components that are excluded provide the ability to document component usage for test and other non-runtime purposes. Excluded components are not reachable within a call graph at runtime.
Used in:
An undefined score method
Common Vulnerability Scoring System v2 - https://www.first.org/cvss/v2/
Common Vulnerability Scoring System v3 - https://www.first.org/cvss/v3-0/
Common Vulnerability Scoring System v3.1 - https://www.first.org/cvss/v3-1/
OWASP Risk Rating Methodology - https://owasp.org/www-community/OWASP_Risk_Rating_Methodology
Other scoring method
Common Vulnerability Scoring System v3.1 - https://www.first.org/cvss/v4-0/
Stakeholder Specific Vulnerability Categorization (all versions) - https://github.com/CERTCC/SSVC
Used in:
, , ,An optional identifier which can be used to reference the service elsewhere in the BOM. Uniqueness is enforced within all elements and children of the root-level bom element.
The organization that provides the service.
The grouping name, namespace, or identifier. This will often be a shortened, single name of the company or project that produced the service or domain name. Whitespace and special characters should be avoided.
The name of the service. This will often be a shortened, single name of the service.
The service version.
Specifies a description for the service.
A boolean value indicating if the service requires authentication. A value of true indicates the service requires authentication prior to use. A value of false indicates the service does not require authentication.
A boolean value indicating if use of the service crosses a trust zone or boundary. A value of true indicates that by using the service, a trust boundary is crossed. A value of false indicates that by using the service, a trust boundary is not crossed.
EITHER (list of SPDX licenses and/or named licenses) OR (tuple of one SPDX License Expression)
Provides the ability to document external references related to the service.
Specifies optional sub-service. This is not a dependency tree. It provides a way to specify a hierarchical representation of service assemblies, similar to system -> subsystem -> parts assembly in physical supply chains.
Specifies optional, custom, properties
Specifies optional release notes.
The name of the trust zone the service resides in.
Used in:
The source of the issue where it is documented.
Used in:
, , ,The name of the source. For example "National Vulnerability Database", "NVD", and "Apache"
The url of the issue documentation as provided by the source
Executes specific commands or tools in order to accomplish its owning task as part of a sequence.
Used in:
,A name for the step.
A description of the step.
Ordered list of commands or directives for the step
Domain-specific step properties.
Used in:
Maps to the tagId of a SoftwareIdentity.
Maps to the name of a SoftwareIdentity.
Maps to the version of a SoftwareIdentity. Defaults to '0.0' if not specified.
Maps to the tagVersion of a SoftwareIdentity. Defaults to '0' if not specified.
Maps to the patch of a SoftwareIdentity. Defaults to 'false' if not specified.
Specifies the full content of the SWID tag.
The URL to the SWID file.
Describes the inputs, sequence of steps and resources used to accomplish a task and its output.
Used in:
BOM unique reference to the resource.
The unique identifier for the resource instance within its deployment context.
The name of the resource instance.
A description of the resource instance.
Domain-specific task instance properties.
References to component or service resources that are used to realize the resource instance.
Indicates the types of activities performed by the set of workflow tasks.
The trigger that initiated the task.
"The sequence of steps for the task.
Represents resources and data brought into a task at runtime by executor or task commands
Represents resources and data output from a task at runtime by executor or task commands
The date and time (timestamp) when the task started.
The date and time (timestamp) when the task ended.
A set of named filesystem or data resource shareable by workflow tasks.
A graph of the component runtime topology for task's instance.
Used in:
,Specifies a tool (manual or automated).
Used in:
,DEPRECATED - DO NOT USE - The vendor of the tool used to create the BOM.
DEPRECATED - DO NOT USE - The name of the tool used to create the BOM.
DEPRECATED - DO NOT USE - The version of the tool used to create the BOM.
DEPRECATED - DO NOT USE
DEPRECATED - DO NOT USE - Provides the ability to document external references related to the tool.
A list of software and hardware components used as tools
A list of services used as tools. This may include microservices, function-as-a-service, and other types of network or intra-process services.
Represents a resource that can conditionally activate (or fire) tasks based upon associated events and their data.
Used in:
,BOM unique reference to the resource.
The unique identifier for the resource instance within its deployment context.
The name of the resource instance.
A description of the resource instance.
Additional properties of the trigger.
References to component or service resources that are used to realize the resource instance.
The source type of event which caused the trigger to fire.
The event data that caused the associated trigger to activate.
Conditions
The date and time (timestamp) when the trigger was activated.
Represents resources and data brought into a task at runtime by executor or task commands
Represents resources and data output from a task at runtime by executor or task commands
Used in:
An identifiable, logical unit of data storage tied to a physical device.
Used in:
The unique identifier for the volume instance within its deployment context.
The name of the volume instance
The volume mode for the volume instance.
The underlying path created from the actual volume.
The allocated size of the volume accessible to the associated workspace. This should include the scalar size as well as IEC standard unit in either decimal or binary form.
Indicates if the volume persists beyond the life of the resource it is associated with.
Indicates if the volume is remotely (i.e., network) attached.
Domain-specific volume instance properties.
Used in:
Used in:
An optional identifier which can be used to reference the vulnerability elsewhere in the BOM. Uniqueness is enforced within all elements and children of the root-level bom element.
The identifier that uniquely identifies the vulnerability.
The source that published the vulnerability.
Zero or more pointers to vulnerabilities that are the equivalent of the vulnerability specified. Often times, the same vulnerability may exist in multiple sources of vulnerability intelligence, but have different identifiers. References provide a way to correlate vulnerabilities across multiple sources of vulnerability intelligence.
List of vulnerability ratings
List of Common Weaknesses Enumerations (CWEs) codes that describes this vulnerability. For example 399 (of https://cwe.mitre.org/data/definitions/399.html)
A description of the vulnerability as provided by the source.
If available, an in-depth description of the vulnerability as provided by the source organization. Details often include information useful in understanding root cause.
Recommendations of how the vulnerability can be remediated or mitigated.
Published advisories of the vulnerability if provided.
The date and time (timestamp) when the vulnerability record was created in the vulnerability database.
The date and time (timestamp) when the vulnerability record was first published.
The date and time (timestamp) when the vulnerability record was last updated.
Individuals or organizations credited with the discovery of the vulnerability.
The tool(s) used to identify, confirm, or score the vulnerability.
An assessment of the impact and exploitability of the vulnerability.
affects
Specifies optional, custom, properties
The date and time (timestamp) when the vulnerability record was rejected (if applicable).
Evidence used to reproduce the vulnerability.
A bypass, usually temporary, of the vulnerability that reduces its likelihood and/or impact. Workarounds often involve changes to configuration or deployments.
Used in:
The vulnerability status of a given version or range of versions of a product. The statuses 'affected' and 'unaffected' indicate that the version is affected or unaffected by the vulnerability. The status 'unknown' indicates that it is unknown or unspecified whether the given version is affected. There can be many reasons for an 'unknown' status, including that an investigation has not been undertaken or that a vendor has not disclosed the status.
Used in:
A single version of a component or service.
A version range specified in Package URL Version Range syntax (vers) which is defined at https://github.com/package-url/purl-spec/blob/master/VERSION-RANGE-SPEC.rst
The vulnerability status for the version or range of versions. Defaults to VULNERABILITY_AFFECTED_STATUS_AFFECTED if not specified.
Used in:
References a component or service by the objects bom-ref
Zero or more individual versions or range of versions.
Used in:
Declares the current state of an occurrence of a vulnerability, after automated or manual analysis.
The rationale of why the impact analysis state was asserted.
A response to the vulnerability by the manufacturer, supplier, or project responsible for the affected component or service. More than one response is allowed. Responses are strongly encouraged for vulnerabilities where the analysis state is exploitable.
Detailed description of the impact including methods used during assessment. If a vulnerability is not exploitable, this field should include specific details on why the component or service is not impacted by this vulnerability.
The date and time (timestamp) when the analysis was first issued.
The date and time (timestamp) when the analysis was last updated.
Used in:
The organizations credited with vulnerability discovery.
The individuals, not associated with organizations, that are credited with vulnerability discovery.
Used in:
The source that calculated the severity or risk rating of the vulnerability.
The numerical score of the rating.
Textual representation of the severity that corresponds to the numerical score of the rating.
Specifies the severity or risk scoring methodology or standard used.
Textual representation of the metric values used to score the vulnerability.
An optional reason for rating the vulnerability as it was.
Used in:
An identifier that uniquely identifies the vulnerability.
The source that published the vulnerability.
Used in:
A specialized orchestration task.
Used in:
BOM unique reference to the resource.
The unique identifier for the resource instance within its deployment context.
The name of the resource instance.
A description of the resource instance.
Domain-specific resource instance properties.
References to component or service resources that are used to realize the resource instance.
The tasks that comprise the workflow.
The graph of dependencies between tasks within the workflow.
Indicates the types of activities performed by the set of workflow tasks.
The trigger that initiated the task.
The sequence of steps for the task.
Represents resources and data brought into a task at runtime by executor or task commands
Represents resources and data output from a task at runtime by executor or task commands
The date and time (timestamp) when the task started.
The date and time (timestamp) when the task ended.
A set of named filesystem or data resource shareable by workflow tasks.
A graph of the component runtime topology for workflow's instance.
A named filesystem or data resource shareable by workflow tasks.
Used in:
,BOM unique reference to the resource.
The unique identifier for the resource instance within its deployment context.
The name of the resource instance.
The names for the workspace as referenced by other workflow tasks. Effectively, a name mapping so other tasks can use their own local name in their steps.
A description of the resource instance.
Domain-specific workspace instance properties.
References to component or service resources that are used to realize the resource instance.
Describes the read-write access control for the workspace relative to the owning resource instance.
A path to a location on disk where the workspace will be available to the associated task's steps.
The name of a domain-specific data type the workspace represents.
Identifies the reference to the request for a specific volume type and parameters.
Information about the actual volume instance allocated to the workspace.
Used in: