One sensor. High-fidelity signal. Governance that works.

Step 1 — Deploy the browser sensor

Push through your existing browser management tooling. No new agents. No network changes. No modifications to your IAM or SSO configuration.

• Chrome Enterprise, Intune, or Jamf — same channel you already use for browser policy.
• Minimum permissions — the extension observes outgoing request URLs and HTTP methods. No content access. No cookies. No request or response body.
• Pilot first, then fleet-wide. Validate signal quality before enabling organization-wide.
• Data stays in your environment. Deployed inside AWS, GCP, or Azure. Nothing sent to Aurora infrastructure.

Step 2 — Resolve identity and ownership

Raw URL telemetry runs through the risk engine and Aurora DB — a curated map of AI tools, developer platforms, HR, and financial services. Every account gets a score. Every account gets a named business owner.

• No IDP or HR system required at launch. Masked UUIDs are sufficient to detect and map risk.
• Service accounts included. The engine resolves ownership even for service accounts.
• Account origin, not just technical metadata. Aurora surfaces who created it and captures further business context at that point — department, purpose, and whether it's still needed.
• Noise filtered. Not every URL is a governance signal — the engine surfaces what matters.

Step 3 — Surface the register and govern it

Every AI tool and service account observed in your environment — with ownership status, risk score, and usage data. This is a working register, not a report. Continuously updated. Filterable, exportable, auditable.

1. Discover — new accounts detected as usage happens. Not on a schedule.
2. Classify — risk engine scores by category and embedded risk.
3. Assign ownership — unresolved accounts flagged, ownership resolved to a named business owner.
4. Act — alerts via Slack, Teams, or email. The account, the owner, the action needed.
5. Review — closed-loop tracking. Every cycle. Auditable.