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

Vulnerability

PreviousSupportNextPolicy

Last updated 7 months ago

A Vulnerability represents a known and published security issue associated with the version or any of its components.

The platform maps components to vulnerabilities using their identifiers (CPE, PURL) and various vulnerability databases.

The platform further enhances the vulnerabilities by identifying its Exploit Prediction Scoring System (EPSS) and CISA's (KEV).

Vulnerability Disposition

As vulnerabilities are matched to a version, the organization may attempt to understand the implications for the product - vulnerability disposition - and may wish to record these findings with the vulnerabilities.

The platform supports adding vulnerability status using .

Known Exploitability Vulnerability Catalog
Vulnerability Exploitability eXchange