No self-service signup. ThreatAware Protect is provisioned by the ThreatAware team. The quickest path to a hands-on demo is to request access through your account contact or the ThreatAware website.
What you’ll have in five minutes
By the end of this page you’ll know:- What problem Protect solves and how it solves it
- What’s in front of you the moment you log in
- The single integration to connect first
- Where to look to see results
- Where to go next
1. Understand the model (60 seconds)
Protect is an agentless cyber asset management platform. It pulls device data from the security and IT tools you already run — EDR, MDM, identity, RMM, vulnerability scanners, network scanners — and answers “is every device protected, and how do we know?” Three ideas underpin everything else:
For the deeper conceptual map see Platform Overview.
2. Log in (60 seconds)
1
Open your Cloud ID
Browse to
https://<your-cloud-id>.threataware.com. Your Cloud ID is the unique subdomain provided when your tenant was provisioned.2
Sign in
Use the credentials from your welcome email, or SSO if it’s been pre-configured.
3
Land on Device Explorer
New tenants land on Device Explorer by default. You’ll see a globe of devices and a row of integration cards across the top.
3. Connect the first integration (90 seconds)
The fastest path to seeing real data is connecting Azure AD (the live UI’s label for Microsoft Entra ID) — it’s OAuth, no firewall work, and gives you cloud-device discovery plus identity in one step.1
Open Settings → Integrations
Cog icon (bottom-left) → Integrations (routes to
/settings/connections).2
Search for Azure AD
Type “Azure” into the Search systems… box and click the Azure AD card.
3
Connect with Global Admin consent
OAuth flow. A Global Admin needs to grant consent once — see Onboarding for the exact scopes.
4. See it work (60 seconds)
While the first sync runs:- Device Explorer (
/device-explorer) — the globe populates and the integration sync row shows “Last sync N minutes ago” per source - Devices (
/devices) — the unified grid; one row per physical device, regardless of how many tools see it - X-Ray (
/x-ray) — click any device, then the X-Ray tab, to see the raw payloads from each connected integration side-by-side
5. Where to go next
Platform Overview
The five-minute conceptual map — dashboard panels, data flow, three-stage Vitals model
Onboarding
Full first-day walkthrough — every priority integration with setup details
Getting Started
Your first 24 hours — explore data, configure Vitals, wire your first Action
Tour
The in-product nine-step dashboard tour
Common evaluator questions
How long until I see meaningful data?
How long until I see meaningful data?
Single-integration data appears within the first hour. A useful estate-wide view typically takes 24-48 hours once 3-5 priority integrations are connected and the matching engine has had a cycle or two to deduplicate devices.
Do I need to install anything?
Do I need to install anything?
No endpoint agents. The only optional install is the PowerShell Relay — a small Windows service that lets Protect query on-premises tools (AD, SCCM, etc.) without inbound firewall rules.
What if my tool isn't in the catalogue?
What if my tool isn't in the catalogue?
Check the Connection Guides tab for the current list. New integrations are added regularly — speak to your account team with the vendor name and API documentation.
Is Protect read-only?
Is Protect read-only?
Protect itself reads from your tools through API integrations. Actions can write to downstream systems (e.g. open a ServiceNow ticket, post to Teams, call a custom webhook), but those are explicit outbound automations you configure — not silent writes back to the source tools. See Trust & Security for detail.
What if I have five minutes more?
What if I have five minutes more?
Read Platform Overview. It’s the densest conceptual page in the docs and it’ll answer most follow-up questions.