Collectors

How many collectors a site needs, where to run them, and why one per routed security boundary is the default.

Install and operate the Windows collector service.

Unattended install of the Windows service build with an enrollment token and control plane URL.

Install the Linux collector as a systemd service on Ubuntu, Debian or RHEL.

Run the collector as a container with host networking.

Install the systemd-managed collector service and enroll it from the command line.

Compose or run the collector container with host networking and a secret-backed enrollment token.

Deploy the hardened OVA on VMware or Hyper-V.

Agentless collection for Microsoft 365, Azure, AWS and Google Workspace.

The collector is outbound-only. What to allow, on which ports, and why no inbound rules are ever needed.

Create, scope, expire and revoke enrollment tokens.

Route collector traffic through an explicit or PAC-defined proxy without breaking mTLS.

Symptom-first guide for AIQ-ENR-001 through AIQ-ENR-004: token, expiry, revocation and connectivity failures during enrollment.

Outbound-only mutual TLS, endpoints to allow-list, certificate rotation.

CIDRs, exclusions, blocked targets, concurrency and maintenance windows: how scan scope is defined and enforced server-side.

Route collector traffic through an explicit or PAC-defined proxy.

What access a collector actually needs for discovery, SNMP, and credentialed checks — and what to avoid granting.

Auto-upgrade rings and manual upgrade steps.

Symptom-first guide for AIQ-UPD-001 through AIQ-UPD-003: verification failures, maintenance-window blocks and rollbacks.

Symptom-first guide for AIQ-COL-001 with exact checks in order.

How to retire a collector cleanly: uninstall the host software and revoke its credential so it cannot re-authenticate.

How the deployed collector evolves into the AssurIQ Endpoint Agent, what each sensor reports today, and why native detection/response stays feature-gated.

Healthy, Degraded, Offline, Enrollment Pending, Update Required and Revoked — what each state means and what to check.

Why the collector is built in Go, the outbound mTLS trust model, its module system, and the phased roadmap.

A plain list of what the native v0.1 collector supports right now versus what is designed but not yet active, and what the DEV build badge means.

Request/response shapes for the collector-facing API v1 endpoints: enroll, heartbeat and observations, plus tenant/site binding rules and error codes.

The exact topology data the in-development 0.2 collector emits, and what is intentionally not collected yet.