Core workflows

Populating your asset inventory

An asset inventory is the foundation of every other workflow in Radius360 — risks attach to assets, controls are scoped to assets, evidence is collected per asset. The fastest way to populate yours depends on what you already have.

Three paths to populate your inventory

The Assets page offers three onboarding paths because operators land here from three different starting points. Pick the one that matches what you already track today — you can mix any of them later.

Path	Best when	Time to first asset
Upload a CSV	You have a list in a spreadsheet, ticketing tool, or someone's head. Most common starting point.	Under 2 minutes
Connect a scanner	You already run Tenable, CrowdStrike, AWS Inspector, or Wiz. The scanner has already discovered your hosts.	~10 minutes (per scanner)
Federate from a CMDB	You operate a maintained CMDB (ServiceNow, Lansweeper, Device42). Roadmap.	Coming soon

You can use more than one

Most tenants end up with a CSV-seeded baseline plus scanner-discovered cloud hosts. Each row carries a source tag so you can always tell which path it came from and prioritize enrichment accordingly.

Path 1 — Upload a CSV

The fastest path. Required column: name. Optional columns: asset_type, owner, criticality (low/medium/high/critical), data_classification, location, external_id, description.

1
On Assets, click Upload CSV.
2
Drop a .csv file or click to browse. The dialog shows a 5-row preview and a count of valid rows before you commit.
3
Review warnings. Rows with no name are skipped. Off-listcriticality values are kept verbatim and surfaced as warnings — you can fix them in the list afterward.
4
Click Import. Inserts are batched (500 rows per chunk) so a 5,000-row CSV doesn't blow request limits. Each imported row is tagged with metadata.import_source = "csv".

Sample CSV:

name,asset_type,owner,criticality,data_classification,location
web-prod-01,server,jane@example.com,high,confidential,us-east-1
db-prod-01,database,ops@example.com,critical,restricted,us-east-1

Path 2 — Connect a scanner

Scanners discover hosts as a side effect of vuln scanning. If you already run Tenable, CrowdStrike, AWS Inspector, or Wiz, that discovery is your CMDB seed. Connect from Integrations — the scanner runs on its scheduled cadence and surfaces discovered hosts on the Vulnerability Management page.

Scanner-discovered hosts need an owner

A scanner finds hosts but knows nothing about who owns them. Discovered assets are flagged so you can assign team and owner before they count as authoritative. Without an owner, an asset is visible but not actionable — risks against it have no one to route to.

Scanner coverage is not complete coverage. On-prem hosts behind segmentation, BYOD, IoT/OT, and unmanaged cloud accounts are scanner-invisible. Pair scanner onboarding with a CSV import for the assets your scanner can't see.

Path 3 — Federate from your CMDB

For mature organizations that already operate a maintained CMDB, federation pulls authoritative records (with owner, team, criticality already populated) and keeps them in sync. Target sources on the roadmap: ServiceNow CMDB, Lansweeper, Device42.

Federation is on the roadmap and ships when a deal asks for it. Today, the equivalent path is to export from your CMDB and use the CSV uploader.

What makes an asset audit-ready

An auditor doesn't care that you have an assets table. They care whether the assets in the table tie back to risk, controls, and evidence. Four fields move an asset from "discovered" to "audit-ready":

Owner. An accountable email on file. Without this, mitigation tasks have no assignee and risk acceptance has no signer.
Criticality. Drives which SLAs apply, which controls are required, and which incidents escalate. Use the four-tier scale (low/medium/high/critical) — auditors recognize it.
Data classification. Determines which frameworks the asset is in scope for (HIPAA only matters if PHI lives there).
Linked business process. Lets the platform compute revenue-at-stake for prioritization. Configurable from the asset detail page.

The Assets page surfaces a "needs enrichment" filter so you can find rows missing any of the four. Working through that list is one of the highest-leverage tasks in your first week with Radius360.

PreviousOnboarding a client Next Managing risks