VulnTrust
Request a demo
Inventory integrations

Bring technology context together without losing where it came from.

Register assets directly, stage governed CSV/XLSX and JSON SBOM imports, or push observations through a scoped Inventory API. Every path preserves review and provenance before correlation.

This page distinguishes capabilities available now from planned integrations.
Available in the current platform

Choose manual, file, SBOM, or API intake.

Every available path prioritizes trustworthy inventory records over an unreviewed volume of imported names.

Available

Guided inventory entry

Register technology, version, environment, and criticality against a reviewed catalog.

Available

CPE 2.3 identity

Attach an exact platform identity when a CPE is the strongest applicability signal.

Available

Package URL identity

Represent ecosystem-native packages with PURLs for OSV-aware version queries.

Available

CSV and XLSX intake

Stage macro-free files, validate every row, review matches and duplicates, then explicitly commit.

Available

CycloneDX and SPDX

Import JSON SBOM components and preserve row-level provenance without retaining the source file.

Available

Scoped Inventory API

Push up to 1,000 observations per request with a revocable, hash-only service token and replay protection.

Integration roadmap

Automation designed around safe reconciliation.

These connector categories are planned, not represented as currently available. Priorities will follow customer inventory systems and security requirements.

Planned
Cloud

Cloud inventories

Governed synchronization patterns for AWS, Azure, and Google Cloud inventories.

Planned
IT operations

Endpoint and asset tools

Connector patterns for device, software, and asset-management systems.

Planned
Engineering

Developer ecosystems

Repository and dependency signals from source-control and software-delivery tools.

Connector principles

Inventory automation should improve data quality—not silently rewrite it.

Every integration must establish who owns a record, how it is matched, when it was last observed, and what happens when the source changes or disappears.

Discuss your inventory sources
  1. Connect safely

    Least-privilege credentials, encrypted secrets, bounded requests.

  2. Normalize visibly

    Source values and canonical mappings remain inspectable.

  3. Reconcile deliberately

    Duplicates, stale records, and ambiguous matches require clear rules.

Shape the integration roadmap

Tell us where your technology inventory lives today.

We’ll review your source systems, data quality, synchronization needs, and a safe path to onboarding.

Request a demo Review our security approach