Identity for every enrolled device
Token-based enrollment establishes the device identity and provisions certificates for the telemetry path.
Connected visibility.
Deliberate access.
Device enrollment, tenant-scoped access and signed agent updates support the monitoring workflow. Understand the mechanisms behind Pulse.
Enrollment & access
01Device identity
02Signed update
03Tenant workspace
Authenticated telemetry
Tenant-scoped access
Console services scope devices, sites, alerts and queries to the authenticated tenant. Auris provides the identity integration.
Signed agent updates
The agent verifies update signatures with Ed25519 and checks integrity before replacing its binary.
A controlled local relay
The optional NODE relay uses an authenticated API and a local buffer to support collection at the site.
Clear mechanisms. Clear scope.
Security depends on deployment configuration, credentials and network access. Pulse supports monitoring operations; this page makes no certification, compliance or service-level guarantee.
- Review enrollment-token scope and lifecycle.
- Use the TLS and identity settings required by your deployment.
- Limit collector credentials to the necessary device permissions.
- Confirm log retention and AI-provider configuration for your environment.