Policy violations
Fleet-wide view of failed device compliance checks, how violations open and resolve, and how to work the list.
Add-on required: Policy violations need the DIAM (Device Identity) add-on with the deviceTrust feature, available on the Advanced tier and above.
When a device fails a check of a device compliance policy, the failure is recorded as a violation. The Policy violations page is the fleet-wide view of those records: one place to see everything that is currently wrong across your devices, instead of opening machines one by one.
The list
Unresolved violations come first, newest first within each group.
| Column | Meaning |
|---|---|
| Violation | The failed check, by the label of the policy check. |
| Policy name | The compliance policy the check belongs to. A policy deleted after the fact is marked as such. |
| Hostname | The device that failed. |
| Operating system | The device's reported platform and version. |
| First seen | When the violation opened. |
| Status | Open or Resolved. |
Lifecycle
Compliance is evaluated continuously in the background, per device against the one policy in force on it:
- A check fails and no open violation exists for that device, policy and check. A new violation opens, and the event is written to the audit log.
- The check keeps failing. The existing violation stays open, no duplicate is created, so the list holds one entry per problem rather than one per evaluation.
- The check passes again. The violation is marked resolved with a timestamp, without anyone touching it.
- Thirty days after it resolved, the record is deleted automatically.
You do not close a violation by hand. A violation goes away by fixing the device, which is deliberate: the list always reflects measured device state, never someone's opinion of it.
Working the list
- A single device with many violations is usually one root cause. Open the device's Policies tab in the device inventory to see all check results together. A device's violations come from the one policy in force on it; when it moves to another policy or to none, its open violations of the previous policy are resolved automatically.
- One check failing across many devices points at the policy rather than the fleet. Verify the check is configured for the software and the operating systems you actually run.
- A violation for a deleted policy is a record from before the policy was removed. Deleting a policy resolves its open violations, so such a record is already resolved and ages out with the others.
Effect on sign-in
A violation alone does not block anyone. It makes the device non-compliant, and only an authentication policy with a device-compliance outcome turns that into a sign-in decision. In Inform mode the user is told about the risk, in Enforce mode the sign-in is gated. That separation lets you record posture across the fleet long before you enforce it.
Troubleshooting
- A device shows a violation for a check that should pass. A check whose evaluation errors is treated as failed. Confirm the device reports the data the check needs, for example that the product it names is actually in the software inventory.
- A fixed device stays in violation. The record clears on the next evaluation, not immediately. Check the device's last-seen time: an offline device cannot report the fix.
- Violations appear right after a policy change. A new or edited policy is evaluated against the current state of every device it applies to, so genuine pre-existing problems surface at once.
See also
- Device compliance policies for authoring the checks and assigning them.
- Device inventory for per-device policy results.
- Authentication policies for turning compliance into an access decision.