Interlynk
Platform Docs
Platform Docs
  • 👋Getting Started
  • Overview
    • ✨Interlynk Features
    • 🧭Navigating Dashboard
  • Product Guides
    • Interlynk Basics
      • Product
      • Version
      • SBOM
        • General
        • Parts
        • Component
        • License
        • Support
      • Vulnerability
      • Policy
      • Compliance
    • Managing Product
    • Importing SBOM
      • SBOM Checks
      • Automation Rules
      • Internal Components
      • Vulnerability Scan
    • Building SBOM
    • Managing SBOM
      • Editing General
      • Updating Components
      • Disposing Vulnerabilities
      • Evaluating Compliance
    • Distributing SBOM
    • Requesting SBOM
    • Monitoring Risks
    • Managing Policy
    • Inventorying Licenses
    • Auditing Changes
    • Managing Notifications
  • Administration
    • Getting Set Up
    • Inviting Users
    • Managing Roles
    • Setting Integrations
  • Use Cases
    • For Management
    • For Security Engineers
    • For OSPO Engineers
  • SUPPORT
    • Technical Support
    • Release Notes
Powered by GitBook
On this page
  1. Product Guides
  2. Interlynk Basics

SBOM

PreviousVersionNextGeneral

Last updated 8 months ago

SBOM

An SBOM provides details of a version by encapsulating its -

  • Metadata such as time of creation and tool used to create SBOM

  • List of components included in the version

  • Relationship among components

  • Licenses associated with components

  • Optional Vulnerabilities associated with components

  • Optional State of vulnerability exploitability associated with vulnerabilities

A may have multiple SBOMs associated with it.

This happens when the first SBOM associated with the version is modified to add details or fix errors, resulting in an updated SBOM.

However, only one of those SBOMs is always considered to represent the version (the "active SBOM").

The platform shows each Version represented by the active SBOM as a list of:

As the version makes the foundation for managing vulnerability, meeting compliance, or enforcing security policies, the platform also surfaces results of vulnerability scanning, policy evaluation, status of component support, and compliance associated with each version

Version
General
Parts
Component
License
Vulnerability
Policy
Compliance
Support