Asset Context

Business context belongs beside the evidence.

Connect supported asset systems. Review identity, ownership and freshness. Preserve the exact context behind each security decision.

From source to evidence

Select context. Keep its history.

Connect ownership, criticality and provenance to the security decision.

Workflow diagram

Asset Context workflow

  1. Five asset sources
  2. Local revision
  3. Analyst selection
  4. Hunt / Blueprint
Read-only synchronization creates local revisions. Analysts choose the exact revision to retain with a hunt or Blueprint; source changes do not rewrite earlier decisions.

Asset Context

Business context, with its sources attached.

Review normalized asset identity, ownership, criticality, freshness and conflicting source assertions. Select the exact context to retain beside a hunt or Blueprint.

Read-only asset source

ServiceNow CMDB

Selected configuration items through the Table API.

Externally managed OAuth bearer.
Read-only asset source

Jira Service Management Assets Cloud

Selected workspace, schemas, types and attributes.

Externally managed OAuth bearer.
Read-only asset source

Lansweeper

Selected site through the Sites Data API.

Personal access token or OAuth bearer.
Read-only asset source

BMC Helix CMDB

Selected dataset, namespace and classes.

Externally managed AR-JWT.
Read-only asset source

Device42

Brief device inventory and approved field mappings.

API-client bearer or protected read account.
Connection and synchronization requirements

These adapters perform read-only, resumable full synchronization against supported public HTTPS endpoints. Configure approved fields, credentials and freshness before enabling a source. Private-network egress, incremental synchronization, relationship ingestion and automatic token renewal are not included. Missing source records do not prove deletion or retirement.

Vendor instance permissions, schemas and token lifecycle require qualification for your environment. Vendor names identify interoperability; they do not imply certification or partnership.

Connected architecture

Put the context beside the model.

Retain a selected asset revision with reviewed Blueprint components. Asset context is advisory and does not prove that a query evaluated an asset.

  • Explicit analyst selection
  • Pinned revision history
  • Source freshness and identity conflicts remain visible
Threat Blueprint canvas
Threat Blueprint canvasProduct workspace example; select to view in full resolution.

Start with the workflow

Bring asset context into your security workflow.

Bring your current intelligence, exposure, telemetry, architecture, detection content, and analyst or service process. We will map the fastest path to a useful outcome.