Asset Details

Clicking an asset name or the preview icon opens its detail page. The detail page is organized into seven tabs: Properties, Links, Context, Risks, Tools, Integrations, and Activity.

The header carries an Add context button (see Context) alongside Edit and Delete. Use Edit to enter edit mode — changes are not saved until you click Save.

If the asset is archived, a banner replaces the editing workflow: “This asset is archived. Editing actions are disabled.” The header shows a Restore button in place of Edit — restoring opens a cascade dialog previewing the impact before anything is brought back — and the Delete button remains for removing the asset permanently. See Archiving and restoring assets.

The Back button labels and returns to wherever you navigated from — e.g. Back to Risk Manager or Back to Dashboard — falling back to Back to all assets (Asset Manager) when opened directly.

Properties

The Properties tab shows the asset’s core metadata and all of its custom property values.

Always visible:

Asset ID
Asset Type
Created date
Last updated date

Below these, each property defined for the asset’s type is listed. In view mode, values are displayed as read-only. In edit mode, each property becomes an interactive input (see Property Data Types).

Editing Properties

Click Edit to enter edit mode. Property inputs appear inline — make your changes and click Save. To discard changes, click Cancel.

The asset name is also editable in edit mode by clicking on it in the page header.

File Attachments

The bottom of the Properties tab has a file attachments section. You can:

Drag and drop files onto the upload zone, or click to browse
View existing attachments with their file sizes
Download any attached file
Mark files for deletion (shown with a strikethrough) — deletions are committed when you save

PDFs imported via the PDF import workflow are automatically attached to the resulting Vehicle asset.

Links

The Links tab shows where this asset sits in the hierarchy, split into two sections:

Parent Assets

The Parent Assets section lists the assets above this one. In edit mode, add or remove parents using the multi-select dropdown. VSEC prevents you from selecting parents that would create circular references, and from selecting a parent whose type cannot contain this asset’s type under the asset-type hierarchy — for example, a Vehicle can never become the parent of another Vehicle. The same rule is enforced server-side, in two ways: manual links created via the links API are rejected with a 400 if they violate the type hierarchy, while parent/child edits saved through the asset update endpoint skip any invalid links instead of failing the save — the skipped link is logged, not returned as an error.

Child Assets

The Child Assets section lists the assets that have this asset as one of their parents. In edit mode, add or remove children with the Select child assets multi-select — the dropdown offers only eligible children (grouped by type), and child links are reconciled when you click Save, just like parents.

If the asset’s type cannot have children, the section shows a This asset type cannot have children. placeholder instead of the selector.

The full asset hierarchy is visualized across all assets in the Tree View.

Related Assets

Below Parent Assets and Child Assets, a Related Assets section lists lightweight, undirected connections to other assets — e.g. a CAN signal or a Bluetooth connection — each with an optional free-text explanation. Unlike the Parent/Child links above, related assets carry no containment semantics, aren’t restricted by the asset-type hierarchy, and never appear in the asset tree.

Select an asset from the dropdown, optionally add an explanation, and click Add. Each related asset shows its type, an Archived chip if it’s been archived, and buttons to open it or remove the relation. Removing a relation deletes it entirely — it disappears from both assets, and from any Item Definition canvas wire it was drawn as.

These same relations are what the Item Definition canvas draws as wires between asset nodes — drawing or deleting a wire there updates this section, and vice versa.

Risks

The Risks tab shows security risks linked to this asset in Risk Manager, split into risks on the asset itself and risks inherited from its descendants in the asset hierarchy. When either group has risks, the Risks tab label carries a count chip — a primary-colored chip for the asset’s own active risk count, and a +N warning-colored chip for the number of risks found on child assets.

Each risk card displays:

Risk heading
Origin (risk type)
Status (Triage, Open, WIP, In Review, Closed)
Priority (High, Medium, Low)

Click any risk card to navigate to its detail page in Risk Manager.

Active Risks

Risks linked directly to this asset, shown first.

Risks on Child Assets

Below the asset’s own risks, a Risks on child assets section lists active risks linked to any descendant of this asset in the hierarchy — for example, a risk on a Component surfaces here on its parent Feature and Vehicle too. Each card in this section additionally shows an On: row with a chip naming the child asset (or assets) the risk actually came from, so you can tell where it lives without leaving the parent.

This section only surfaces active child risks — an archived risk on a child asset does not roll up here, even though an archived risk on the asset itself still appears below.

Archived Risks

By default, only active risks are shown. Click the archived risk(s) link to also see risks that have been marked as archived.

Tools

The Tools tab gathers what VSEC’s tools — Design and Test — have on this asset. Each section only appears when the matching tool is enabled for your workspace; when neither is, the tab reads “No VSEC tools are enabled for this workspace.” (Risk Manager is part of VSEC Core, so risks stay on their own Risks tab rather than here.)

Design

The Design section lists the item definitions this asset takes part in. Each entry shows the definition’s name, its item and component count, and a chip naming this asset’s role in it:

Item — this asset is the item being analyzed.
Component — inside the item boundary.
Environment — outside the item boundary; the item interfaces with it.

Open in Design opens the Item Definition list scoped to this asset. When the asset isn’t in any item definition yet, the section says so.

Test

The Test section is a placeholder: test runs aren’t linked to assets yet, so nothing is listed here. Results from testing reach the asset as risks instead — see the Risks tab.

Integrations

The Integrations tab manages connections to external data sources for this asset. Currently, this includes firmware integrations via xZETA.

If the xZETA integration is enabled for your workspace, you can:

Link one or more firmware images to this asset — an asset is no longer limited to a single linked firmware
Unlink any linked firmware image
Click Fetch latest scan to retrieve the most recent SBOM (software bill of materials) results from xZETA for the linked firmware(s)
See the timestamp of the last completed scan

The scan itself runs on the xZETA side; Fetch latest scan pulls the latest results into VSEC for review.

Firmware linking is only available for assets whose type carries an SBOM property — typically lower-level layers like a Software Component, not a Vehicle. See SBOM & HBOM Properties.

The SBOM retrieved from linked firmware syncs automatically into the asset’s SBOM property, where it shows a Firmware linked chip. You can still upload your own SBOM directly on that property as well — downstream monitoring watches both sources. Country-of-origin monitoring of BOM contents is no longer configured here; it is now a Beacon rule — see Beacon → BOM Country of Origin.

Multiple Firmwares and Package Attribution

When more than one firmware image is linked to an asset, each package and vulnerability in the SBOM list is attributed back to the firmware(s) it came from:

Each package row shows a chip naming its source firmware. A package present in more than one linked firmware carries a chip for each.
A Firmware filter appears above the package list (alongside the existing origin-country filter) once a second firmware is linked, letting you narrow the list down to packages from a single firmware or view All firmwares together.
If you just linked a firmware and its packages don’t show up yet, click Fetch latest scan — attribution is populated by the scan, not by the link action itself.

Cryptographic Materials (CBOM)

Below the SBOM package list, a Cryptographic Materials (CBOM) section shows the cryptographic bill of materials xZETA reverse-engineers from the linked firmware — keys, certificates, and other credential material. It syncs automatically the same way the SBOM does, and Fetch latest scan refreshes both. Materials flagged with a country of origin also feed the Beacon → BOM Country of Origin rule.

Each material row shows:

Type — Private key, Public key, Certificate, or Crypto material
Algorithm and key size, plus format
Origin countries, if any
A password-protected chip, if the material is password protected
The source file path
For certificates: Subject, Issuer, and Valid to date
A chip per source firmware, once more than one firmware is linked to the asset

Unlike the SBOM package list, CBOM has no firmware or origin-country filter — all materials from every linked firmware are shown together.

If no scan has run yet, the section reads “No CBOM data for this asset yet. Run a scan to populate.”

Context

The Context tab is the AI enrichment workspace for the asset — the read/manage view of everything VSEC knows about it. Adding to that context (a note, a file, or a request to someone outside your workspace) happens in the Add context dialog, opened from the Add context button in the header or Add context… in the right-click menu. The dialog has two tabs — Add context (a note and/or files, submitted together) and Request from someone (see Context Requests).

The tab itself is organized into three panels:

What VSEC Knows About This Asset

A markdown understanding document the AI writes from the asset’s context, with a Last curated timestamp and a Re-curate button to force a manual refresh. If the context exceeded its size limits, a warning explains the understanding was built from partial context and lists the files that weren’t fully read.

Context Notes

The notes and documents that feed curation:

Context notes — a list of the free-text notes added via the Add context dialog. Each shows its author (or an External badge with the outside contributor’s name/email if it came in via a context request) and a delete icon.
Requested from others — a read-only list of outstanding context requests for this asset, each with a status chip (Awaiting response, Responded, Expired, Cancelled) and response count. Managing requests (sending, revoking) happens in the Add context dialog.
Documents in context — every file attached to the asset, as a chip with a per-file ingestion status from the last curation (hover for details).

If the asset has a Record property (e.g. an attached vendor), the AI’s context includes that record’s full data — name, field values, and attachment filenames — not just a reference. Record attachments are never changed by AI curation; only you can add or remove them.

Suggested Updates

After the AI processes the asset’s context, it surfaces suggestions in up to four areas:

Properties — property values to add or update
Suggested links — new asset relationships to create
Suggested removals — existing asset links to consider detaching, each rated High or Medium confidence
New assets detected — components found in the context that aren’t assets yet; creating one adds it as a child asset with properties filled from this asset’s context

Additions are pre-selected for review when the AI rates them high confidence; medium-confidence suggestions (including new-asset detections) appear unchecked for you to opt into. Removals are opt-in only and require explicit confirmation before any link is detached — nothing is selected by default. Click Apply selected (N) to commit the checked property/link/removal rows, or Create selected (N) to create the checked new assets.

Suggested links are restricted to valid parent/child pairs under the asset-type hierarchy — the AI is never offered another Vehicle, or any same-type asset, as a link candidate. If you confirm a suggestion from an older run that predates this restriction and it would still violate the hierarchy, applying it is skipped rather than silently dropped: a warning toast names the asset(s) that were skipped so you know why the link didn’t appear.

Activity

The Activity tab is a chronological log of every change made to this asset. Each entry shows:

The user who made the change (with avatar)
The action type — one of: Created, Updated, Deleted, File uploaded, Generated, Enriched, Risk created / accepted / discarded / resurfaced, Firmware linked / unlinked, or Automated assessment
A summary of what changed (e.g. which fields were updated, the file name, or the risk heading)
A relative timestamp (e.g. “3 days ago”)

The activity log uses point-in-time snapshots — click any entry that carries one to open a revision preview showing what the asset looked like at that moment in its history, even if properties or types have changed since.

Filtering

The filter bar above the log lets you narrow history by any combination of:

Filter	Description
From / To	Show only entries within a date range. Use the preset chips (Last 7 days, Last 30 days) for quick ranges.
User	Show only entries made by a specific user (or System for automated actions). The dropdown is populated from the users present in the currently loaded entries.
Action	Show only entries of a specific action type. The dropdown is populated from the action types present in the currently loaded entries.

All filters are applied client-side and can be combined. Click Clear to reset the date range, user, and action filters all at once.

If the filtered result is empty, the log displays “No activity matches your filter.” When no filter is active and there are no entries for the selected date range, it displays “No activity in this date range.”

Last updated on September 18, 2026

Creating Assets Import & Export