Huntress adds per-client RMM Guard exceptions and HaloPSA priority controls

← Security Watch

Huntress has added per-client RMM Guard decisions and configurable HaloPSA ticket priorities. These November 19–20 changes let MSPs narrow an RMM exception to the customer that needs it and align incoming security tickets with their service desk workflow.

RMM Guard: scope the exception to the client

The November 19 Managed ESPM release lets an organization override the account decision for an RMM tool. Other clients continue to inherit the account default. Administrators can inspect overrides in the inventory, review the organization dashboard and reset an exception to the default.

Suggested MSP action: review account-wide approvals created for a single customer and assess whether an organization override now fits better. Confirm the resulting decision on the intended client’s endpoints. The announcement does not give plan entitlements or establish that every RMM policy has changed automatically.

HaloPSA: choose how severity becomes ticket priority

The November 20 integration update lets administrators map each Huntress notification severity to a HaloPSA ticket priority. Review that mapping against your escalation and response procedures, then validate a test ticket. This is an available integration control, not a reported security incident.

RMM Guard release note · HaloPSA priority release note · Dated changelog. Verified November 21, 2026. The notices say the controls are available now; rollout completion and additional licensing limits are not specified.

Share this article