> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/sbom360/generate-an-sbom/existing-sbom-as-source/eo-14028-checks.md). # EO 14028 checks ### Minimum fields EO 14028 checks correspond to the minimum elements in an SBOM as described by The table below lists the minimum elements. Some of these fields are at a SBOM level and the others are applicable for each component in the SBOM.
Data FieldDescription
SBOM TimestampRecord of the date and time of the SBOM data creation
SBOM AuthorThe name of the entity that creates the SBOM data for this component
SBOM dependenciesCharacterizing the relationship that a component X is included in software Y
Component NameDesignation assigned to a unit of software defined by the original supplier
Component VersionVersion assigned to a unit of software defined by the original supplier
Component Supplier NameThe name of an entity that creates, defines, and identifies components
Component Unique IdentifiersIdentifiers that are used to identify a component (like PURL, BomRefId etc)
### Mapping of minimum fields Below is a table mapping the NTIA minimum SBOM fields to SPDX and CycloneDX | | SPDX | CycloneDX | | ----------------------- | ------------------------------------------ | ---------------------------------------------------------------- | | SBOM Timestamp | (2.9) Created: | metadata/timestamp | | SBOM Author | (2.8) Creator: | metadata/authors/author | | SBOM dependencies | (7.1) Relationship: DESCRIBES CONTAINS | Inherent in nested assembly/subassembly and/or dependency graphs | | Component Name | (3.1) PackageName: | name | | Component Version | (3.3) PackageVersion: | version | | Component Supplier Name | (3.5) PackageSupplier: | Supplier publisher | | Component Unique Ids | (2.5)SPDX Document Namespace (3.2) SPDXID: | bom/serialNumber component/bom-ref | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.veedna.com/sbom360/generate-an-sbom/existing-sbom-as-source/eo-14028-checks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.