Endpoint Threat Signals Directly in Your Zero Trust Policies
Timus SASE now integrates with Huntress, bringing real-time device signals — from incident severity to firewall status — into your Adaptive ZTNA policies. Policy decisions now reflect the actual security state of each device, without switching between consoles.
Policy Decisions That Reflect Real Device Security State
When Huntress flags a device — whether for an open incident, a stopped agent, or a non-compliant firewall — that information is now available directly inside Timus. You can use those signals as conditions in your Adaptive ZTNA policies, so access decisions reflect what’s actually happening on the endpoint, in real time.
No console switching. No manual step between detection and enforcement.
Timus supports partner–customer operations, so the Huntress integration can be enabled at two scopes depending on how your team manages credentials.
Your team creates and manages the API credential centrally, then activates Huntress across multiple customer environments. Ideal for MSPs who manage Huntress at the partner level and want consistent policy enforcement across all clients from a single credential.
Each customer creates and manages their own API credential within their Huntress organization. The integration is scoped only to that customer’s tenant. Best suited for customers who self-manage their Huntress environment independently.
→ Timus Connect 5.0.0 or higher on end-user devices
→ Adaptive ZTNA enabled in your Timus tenant
→ An active Huntress account with admin access
→ Available in: Timus Cloud 2.0.3 and later
→ Supported OS: Windows and macOS
Sign in to your Huntress admin account, navigate to API Credentials, and generate a new User API Credential. Copy the API Key and API Secret before closing the modal — the Secret is displayed only once.
Go to Settings → Integrations, find Huntress EPP Integration, click Manage, enter your API Key and Secret, and save.
Huntress signals are now available as conditions across all Adaptive ZTNA policy types — Access Policies, Detectors, and Device Posture Checks.
Important: If you rotate or recreate credentials in Huntress, update Timus with the new API Key and Secret. Stale credentials will cause Huntress signals to stop updating in your policies.
© Timus Networks, Inc. 2026.
All Rights Reserved.
