> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threataware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Zero to first integration in five minutes — the evaluator's path through ThreatAware Protect

This page is for evaluators and prospective customers. If you already have a provisioned tenant and need a full setup walkthrough, jump to [Onboarding](/onboarding); for a guided product tour, see [Getting Started](/getting-started).

<Info>
  **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](https://threataware.com).
</Info>

## 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:

| Idea                       | What it means                                                                           |
| -------------------------- | --------------------------------------------------------------------------------------- |
| **No agents**              | API-based reads from your existing consoles. Nothing deploys to endpoints.              |
| **Cross-tool correlation** | The same laptop reported by five tools appears once, not five times.                    |
| **Functional Vitals**      | Not *"is the agent installed?"* but *"is the agent actually reporting and protecting?"* |

For the deeper conceptual map see [Platform Overview](/platform-overview).

## 2. Log in (60 seconds)

<Steps>
  <Step title="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.
  </Step>

  <Step title="Sign in">
    Use the credentials from your welcome email, or SSO if it's been pre-configured.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 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.

<Steps>
  <Step title="Open Settings → Integrations">
    Cog icon (bottom-left) → **Integrations** (routes to `/settings/connections`).
  </Step>

  <Step title="Search for Azure AD">
    Type "Azure" into the **Search systems...** box and click the **Azure AD** card.
  </Step>

  <Step title="Connect with Global Admin consent">
    OAuth flow. A Global Admin needs to grant consent once — see [Onboarding](/onboarding) for the exact scopes.
  </Step>
</Steps>

Within 15-60 minutes you'll have your first device data flowing. Other priority integrations to connect next: Microsoft Intune, your primary EDR (CrowdStrike, Microsoft Defender ATP, or SentinelOne), and on-prem Active Directory via the [PowerShell Relay](/powershell-relay).

## 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

If you don't see data yet, the integration is still on its first sync. Initial sync time after connecting depends on estate size.

## 5. Where to go next

<CardGroup cols={2}>
  <Card title="Platform Overview" icon="compass" href="/platform-overview">
    The five-minute conceptual map — dashboard panels, data flow, three-stage Vitals model
  </Card>

  <Card title="Onboarding" icon="rocket" href="/onboarding">
    Full first-day walkthrough — every priority integration with setup details
  </Card>

  <Card title="Getting Started" icon="play" href="/getting-started">
    Your first 24 hours — explore data, configure Vitals, wire your first Action
  </Card>

  <Card title="Tour" icon="circle-play" href="/tour">
    The in-product nine-step dashboard tour
  </Card>
</CardGroup>

## Common evaluator questions

<AccordionGroup>
  <Accordion title="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.
  </Accordion>

  <Accordion title="Do I need to install anything?">
    No endpoint agents. The only optional install is the [PowerShell Relay](/powershell-relay) — a small Windows service that lets Protect query on-premises tools (AD, SCCM, etc.) without inbound firewall rules.
  </Accordion>

  <Accordion title="What if my tool isn't in the catalogue?">
    Check the [Connection Guides](/connection-guides) tab for the current list. New integrations are added regularly — speak to your account team with the vendor name and API documentation.
  </Accordion>

  <Accordion title="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](/trust/security) for detail.
  </Accordion>

  <Accordion title="What if I have five minutes more?">
    Read [Platform Overview](/platform-overview). It's the densest conceptual page in the docs and it'll answer most follow-up questions.
  </Accordion>
</AccordionGroup>