Asset Properties
Properties are the fields that store information on an asset. Each property has a name, a data type, and an optional description. Properties are defined globally and then assigned to one or more asset types.
Navigate to Asset Manager → Settings → Properties to manage your properties.
Default Properties
VSEC includes six properties out of the box:
| Property | Data Type | Description |
|---|---|---|
| Product Owner | Person | Responsible person for the product. Used by VSEC Risk Manager for default risk assignment. |
| Keywords | Tags | Attribute tags used to match threat intelligence and relevant test cases to this asset. |
| Interfaces | Multi-select | External interfaces that can be used as an attack surface. Options: Wi-Fi, Bluetooth, Cellular, CAN, GPS, USB, JTAG, LIN, RF, Automotive Ethernet, FlexRay. |
| Product ID | Person | Correlates parent and child assets. Populated automatically during PDF import. |
| Vehicle Line | Person | Vehicle line / platform identifier. Populated automatically during PDF import. |
| Model Year | Person | Model year. Populated automatically during PDF import. |
Property Data Types
When creating a custom property, choose one of the following data types:
| Data Type | UI Input | Notes |
|---|---|---|
| Short Text | Single-line text field | Max 255 characters; best for short identifiers, names, or codes |
| Long Text | Multi-line text field | Max 5000 characters; for longer free-form text |
| Tags | Tag input with autocomplete | Values are stored as an array; autocompletes from the property’s own configured options, and free entry is allowed (see note below on the Keywords property) |
| Multi-select | Multi-option dropdown | Requires predefined options in the property’s metadata |
| Select | Single-option dropdown | Requires predefined options in the property’s metadata |
| Custom Select | Single-option dropdown with free entry | Pick one predefined option or type your own answer |
| Person | User picker | Selects from users in your workspace |
| Number | Numeric field | Stores a numeric value |
| Date | Date picker | Stores an ISO date |
| SBOM | File upload, parsed package list | Declares that the asset type carries a software bill of materials — see SBOM & HBOM Properties |
| HBOM | File upload, parsed package list | Declares that the asset type carries a hardware bill of materials — see SBOM & HBOM Properties |
| Record | Configurable multi-field form, reusable instances | Holds structured, reusable data instead of one flat value — see Record Properties |
Creating a Custom Property
Click New Property to define a new property. You will need to provide:
- Name — required; must be unique within your workspace
- Data Type — required; determines how the value is stored and edited
- Description — optional; shown as helper text in the UI
- Options (for Select, Custom Select, and Multi-select types) — define the list of valid values
After creating a property, assign it to one or more types from the Types settings page or from the property’s own settings.
SBOM & HBOM Properties
Assigning an SBOM or HBOM property to an asset type is the declaration that assets of that type carry that kind of bill of materials. This single assignment gates everything BOM-related for the type:
- Whether assets of that type can have a BOM uploaded to them at all
- Whether xZETA firmware can be linked to link assets of that type (SBOM only — HBOM assets can’t link firmware)
- Whether the periodic xZETA sync writes a BOM to assets of that type
A type with no SBOM or HBOM property — for example a Vehicle — can’t have a BOM uploaded or firmware linked to it; only lower layers such as a Software Component or Hardware Component would typically carry one.
On the asset detail page, an SBOM or HBOM property renders as an upload control. Upload a CycloneDX or SPDX JSON file; VSEC parses it into a package list (name, version, path, link, and origin country when the vendor included it) and stores it alongside the asset for review. When you’ve uploaded a BOM file yourself, a Download file button on the property retrieves the original uploaded file; a BOM synced from linked xZETA firmware has no stored file, so no download appears for it.
For an SBOM property, if the asset also has xZETA firmware linked, the property shows a Firmware linked chip — xZETA reverse-engineers the linked firmware’s SBOM and syncs it here automatically. You can still upload your own SBOM as well; downstream monitoring watches both sources.
Record Properties
A Record property holds structured, reusable data rather than a single value. Instead of typing the same information into every asset that needs it, you define the record’s shape once and create named instances that any number of assets can reference — edit the instance once and the change appears everywhere it’s used.
When creating or editing a Record property, define its schema: a list of fields, each with a label and a type:
| Field Type | Input |
|---|---|
| Short Text | Single-line text field |
| Long Text | Multi-line text field |
| Number | Numeric field |
| Date | Date picker |
| Select | Single-option dropdown (define the options) |
| File Upload | Attaches a file to that specific named slot on the record |
For example, a “Vendor” Record property might define fields for Supplier Name, Tier, and a Contract file upload. Once the schema exists, users create instances against it — “Bosch,” “Lear,” and so on — each filling in its own field values. An asset with the Vendor property then attaches one or more of those instances (the input is a multi-select) rather than re-entering the vendor’s details.
You don’t have to create the instance first. From the asset’s record multi-select, typing a name that doesn’t already exist offers an Add new record option (shown as Add “<name>” as you type) that opens the record form inline — fill in its fields, including any file-upload slots such as a supplier letter, and the new instance is created and attached in one step. This inline option is only available to users who can create records; if a matching instance already exists, VSEC has you attach it rather than create a duplicate.
Files attached to an attached record (for example a supplier letter) also show as download links on the asset’s Properties view, so the evidence can be pulled straight from the asset without opening the record configuration.
Assigning Properties to Types
A property is only visible on assets of a type it has been assigned to. Assignment is many-to-many — the same property can be on multiple types, and a type can have many properties.
To assign:
- Go to Settings → Types and open the type you want to edit
- Use the property assignment UI to add the property
- Optionally set a default value for the property on that type — this value will be pre-filled when a new asset of that type is created
To remove a property from a type, go to the type’s settings and remove it from the list. Existing property values on assets are not deleted.