Skip to content →
Log in

Device posture

Evaluate endpoint health and enforce failures deliberately.

Use Security → Device Posture to define the checks a device must pass and what happens when it fails. Device posture checks health evidence reported by the agent. Device policies configure agent behaviour; access policies grant services.

Device Posture overview cards for Fleet compliance, Non-compliant, Avg trust score and Posture policies above the Default baseline card

The four overview cards summarise the fleet; here 10 of 11 evaluated devices are compliant, one device is unknown, and the baseline enforces four checks.

Before you start#

  • Viewing needs policies:view. Creating a policy needs policies:create. Editing, enabling or disabling needs policies:update. Deleting needs policies:delete. On tenants without a permission list, owners and admins hold all four; the user role can view and create; readonly can only view.
  • Agents must be enrolled and reporting. The page states that compliance metrics appear “after agents connect and report posture on heartbeat.”
  • A default baseline must exist before you can add scoped overrides. The control plane rejects an override otherwise with “create the tenant baseline before adding overrides”.
  • Scope cannot be changed after a policy is created.

Create the baseline#

  1. Open Security → Device Posture and click Create Baseline. (Once a baseline exists the button reads Add Override.)
  2. Under Quick Start, pick a preset or skip it: Essential, Standard or High Security. Essential starts in monitor mode with disk encryption and firewall; High Security enforces all six checks.
  3. Under Scope & Targeting, choose Entire Tenant. The other scopes are Role, Group and Device.
  4. Under Enforcement Mode, choose Monitor, Warn or Enforce. Start with Monitor.
  5. Under Required Security Checks, select at least one check. The counter reads “N of 6 selected”.
  6. If you chose Enforce, pick an Enforcement Action: Block Access, Quarantine or Warn User.
  7. Optionally open Advanced Options to set Min Trust Score (0 to 100), Grace Period (min) and Priority.
  8. Wait for the Impact Preview. It reads “{f} of {e} evaluated devices would fail this policy right now.” The Create Policy button stays disabled until the preview succeeds.
  9. If the preview shows devices that will lose access, tick “I understand {n} devices will lose network access when this policy is saved.”
  10. Click Create Policy.

You should see the policy in the Default baseline card with “Effective on N devices · N would fail”.

Default baseline card followed by the Scoped overrides table with Applies to, Precedence, Mode, Requirements, Effective on, Status and Updated columns

The baseline card sits above the Scoped overrides table; the Precedence column shows the scope rank and Order, and a row flags how many devices would fail.

Add a scoped override#

  1. Click Add Override.
  2. Choose Role, Group or Device and pick a target. If a catalog is down you see “Temporarily unavailable” and must choose another scope.
  3. Complete the mode, checks and action as above, then click Create Policy.

The override appears under Scoped overrides. Its Precedence column shows “1 · Device”, “2 · Group” or “3 · Role” and “Order {priority}”.

New Posture Policy form with the Standard preset selected, Group scope targeting Engineering, Warn enforcement mode and the Required Security Checks counter reading 4 of 6 selected

The Standard preset fills the form: Group scope with a target picked, Warn mode, and four of six checks ticked, with the Policy Summary tracking every change.

Lower part of the posture policy form showing Enforcement Action, Advanced Options and the Impact Preview stating 1 of 5 evaluated devices would fail this policy right now with an acknowledgement checkbox

In Enforce mode the Impact Preview counts the devices that would fail today, names the failing check, and asks you to acknowledge the loss of access before Create Policy enables.

Enable or tighten a policy#

  1. Open the row menu and choose Enable policy.
  2. If the policy is in Enforce mode with a blocking action and some devices would fail or have no data, the dialog is titled Acknowledge and Enable Policy and warns “{n} devices may lose network access when this enforce policy is enabled.”
  3. Click Acknowledge and enable.

Move from Monitor to Warn to Enforce only after you have fixed the expected failures.

Reference#

Checks#

CheckWhat it verifies
Disk EncryptionBitLocker, FileVault, or LUKS/dm-crypt
FirewallWindows Firewall, macOS Application Firewall, or ufw, firewalld or iptables
OS VersionMinimum version per platform. Leave a platform blank to accept any version.
Screen LockMax timeout (minutes), 1 to 60. Devices must report an inactivity duration.
Antivirus / EDRAny AV/EDR or Specific Products Only from a list of named products
Agent Always ConnectedStrict Mode fails on any disconnection. Grace Mode fails after a grace period of 30 to 3600 seconds (default 300).

Modes and actions#

SettingEffect
MonitorLogs compliance status. No user notification, no block.
WarnDevices connect. Non-compliance is recorded in Devices and Audit.
EnforceApplies the chosen action to non-compliant devices.
Block AccessTerminates the device’s WireGuard tunnel. The agent cannot reconnect until compliant.
QuarantineCurrently equivalent to Block Access. Remediation-only access is planned but not available.
Warn UserDevice keeps access; non-compliance is recorded.

Precedence#

Device overrides win first, then group, then role, then the baseline. Within one scope, lower Order wins. Equal order is broken by stricter mode (enforce over warn over monitor), then lowest policy ID. Disabled policies are skipped. Devices matching several overrides at one scope appear under Overlapping overrides.

Overview cards#

Fleet compliance (compliant devices as a percentage of evaluated devices), Non-compliant, Avg trust score and Posture policies (enabled count, with how many are enforcing). A device with no posture report counts as unknown. A device with no effective policy is not covered.

Posture reports older than five minutes are treated as stale by default and add a stale-report violation. In enforce mode, devices with no posture data are blocked until they report. Never treat unknown or stale evidence as compliant.

Troubleshooting#

  • “Device posture data could not be loaded” with Retry. The overview endpoint failed. Retry, then check control plane health.
  • “Some posture targets are temporarily unavailable”. A role, group or device catalog did not load. Those scopes cannot be selected until it does.
  • “Saving is disabled until the preview succeeds.” The impact preview failed. Fix the form error it reports or retry.
  • “enable the tenant baseline before enabling posture overrides” or “disable posture overrides before disabling the tenant baseline”. The baseline must be enabled while any override is enabled.
  • “a posture policy already exists for this subject”. Only one policy per scope target is allowed. Edit the existing one.
  • Banner “N devices have no effective posture policy”. Add or enable the baseline.