Skip to content

Periodic Review

This checklist covers recurring hygiene tasks for maintaining customer Enclave deployments. Run it monthly or quarterly per customer, depending on the size and complexity of the deployment.

Systems

Stale systems

Identify systems that have not connected recently:

  • In the Enclave Portal, review the Systems page and sort by last seen date.
  • For automated cleanup, use the Cleaning Up Inactive Systems script. Run in test mode first (-test) to review candidates before deleting.
  • Investigate any system that has not connected in the last 30 days. Common causes: device decommissioned without uninstalling Enclave, device offline for an extended period, or employee has left.

Disabled systems

Check for systems in a disabled state. Disabled systems remain enrolled and continue to consume a licence seat. For each disabled system, decide:

  • Re-enable if the reason for disabling no longer applies.
  • Delete if the system should be permanently removed. See System Decommission for the procedure.

Agent versions

Check the Enclave agent version across enrolled systems. Outdated agents may miss security patches or feature updates.

  • Review agent versions from the Systems page in the Enclave Portal.
  • If agents are deployed via RMM, confirm the deployment script targets the current release. See Automatic Updates for update strategies.
  • Check the Changelog for recent releases.

Enrolment keys

Review all enrolment keys in the customer's tenant. See Enrolment Key Management for the full key audit procedure.

Policies

Identify policies where one or both sides (sender or receiver) reference tags with zero members. These policies have no effect. Keep them if the tags will be populated again (e.g. seasonal contractors), otherwise delete.

Trust requirements

If trust requirements are configured, verify the identity provider integration is still working: a test user can authenticate and connectivity establishes.

Licence reconciliation

In the Partner Portal, compare each customer's Licensed and Enrolled counts:

  • Enrolled > Licensed. The customer is over their licence allocation. Automatic seat adjustment will increase the licensed count on the 14th or 28th. If this is unintended, investigate which systems are driving the overage.
  • Licensed > Enrolled. The customer is paying for more seats than they are using. Use Amend Licence Count to reduce to the enrolled count (or a planned headroom figure). See Billing - Amending seat counts.
  • If using Gradient MSP for billing reconciliation, confirm the integration is syncing correctly and customer names match between Enclave and your PSA.

Security Events

Review the Security Events log for each customer tenant. Look for:

  • Unexpected system deletions or revocations
  • Policy changes not associated with a known change request
  • Failed login attempts or 2FA failures

Gateway health

For customers with deployed gateways:

  • Confirm the gateway system appears as connected in the Enclave Portal.
  • Run enclave self-test to check OS-level configuration (network interfaces, packet filtering, fabric status).
  • For gateways with failover configurations, verify that backup gateways are online and reachable.

Last updated July 26, 2026