Three paths in — CSV, scanner, or your CMDB
Asset Inventory
Three paths in. Upload a CSV in under two minutes. Connect a scanner (Tenable, CrowdStrike, Wiz, AWS Inspector) and discovered hosts populate automatically. Or federate from your CMDB. Manual rows reconcile with scanner-discovered hosts on hostname or IP — no duplicates, your owner and criticality survive every re-sync.
Why it matters
Built for outcomes, not checkboxes
CSV Path
Drop a spreadsheet of hosts, owners, and types. Required column is just `name` — everything else is optional.
Scanner Auto-Discovery
Connect Tenable, CrowdStrike, Wiz, or AWS Inspector and discovered hosts populate automatically on every sync.
CMDB Federation
Federate from ServiceNow CMDB, Lansweeper, or Device42. Assets stay authoritative in your CMDB; we mirror.
No Duplicates
Manual rows reconcile with scanner-discovered hosts on hostname or IP. Operator-curated owner and criticality survive every re-sync.
How it works
Everything in one place, nothing to bolt on
Three Onboarding Paths
Most platforms force CSV-only or assume you operate a maintained CMDB. Radius360 supports all three so you start with whatever you have today.
- CSV import with header validation, per-row warnings, and a 5-row preview before commit
- Scanner auto-discovery from Tenable, CrowdStrike, Wiz, AWS Inspector — discovered hosts land in Assets every sync
- CMDB federation roadmap: ServiceNow CMDB, Lansweeper, Device42
- Manual Add Asset always available for one-off entries
Manual ↔ Scanner Reconciliation
Add an asset manually first, connect a scanner later — Radius360 attaches the scanner's ID to your existing row instead of creating a duplicate. Owner, criticality, and data classification you set are preserved across every re-sync.
- Match on hostname or IP — deterministic, no false-merge risk
- Operator-curated fields (owner, criticality, data_classification, status) never overwritten
- Scanner refreshes its own metadata fields (last-seen, cloud account) on each sync
- metadata.reconciled_with_scanner flag distinguishes reconciled rows
Risk Classification
Classify assets by criticality and data sensitivity. High-value, high-risk assets surface to the top so your team focuses protection where it matters most.
- Criticality levels: Critical, High, Medium, Low — feed into risk-prioritization scoring
- Data classification: Public, Internal, Confidential, Restricted
- Compliance scope tagging (in-scope for SOC 2, PCI DSS, etc.)
- Custom classification fields for your environment
Risk-to-Asset Linkage
Link risks directly to the assets they affect. When an auditor asks 'what assets does this risk impact?', the answer is already there.
- Risks linked to one or more assets
- Asset view shows all associated risks
- Risk score weighted by asset criticality and revenue-at-stake
- Evidence vault items linkable to assets
Get started today
Run your security program, not just your tools
Whether you're the security lead holding it together in-house without a CISO, or a vCISO, consultant, or MSSP running client programs, Radius360 turns your stack into decisions your board and auditors trust.
We use cookies
We use strictly necessary cookies to make Radius360 work. With your consent, we'd also like to use analytics cookies to understand how visitors use our site so we can improve it. You can change your choice anytime. See our Privacy Policy.