Compliance Report

The Compliance Report provides a comprehensive, data-driven view of update compliance for a single resource. Unlike the Last Update Status, which only reflects the result of the most recent action, this report aggregates data from all successful PATCH and SCAN actions that occurred within the current calendar month to build a complete picture of the resource's state.

Accessing the Report

You can access the full Compliance Report from two locations in the UI. In both cases, clicking the Compliance Status button opens the report modal:

• Resources List: Look for the Compliance column in the main resources table.
• Resource Details View: Located in the Compliance section of the details view.

The Updates Table

The core of the report is the Updates Table, which lists every unique package or update detected on the resource during the reporting period.

Package Status Meanings

Each row in the table represents a specific update and its latest known status.

Status	Meaning	Compliance Impact
Installed	Update was confirmed as installed.	Compliant
Updated	Update was successfully applied during a patch action.	Compliant
Removed	Update was confirmed as removed/uninstalled.	Compliant
Available	Update is available but has not been installed yet.	Non-compliant
Failed	An attempt to install the update failed.	Non-compliant
Pending Reboot	Update requires a reboot to finish.	Non-compliant

Calculation Logic

To generate this report, Fleet Control performs a logic-based aggregation of historical data:

1. Data Scope: The system collects all package results from every qualifying event action (Scans, Patches, and OS-specific equivalents) within the current calendar month.
2. Deduplication: If the same package appears in multiple actions (e.g., it was "Available" in a scan on the 1st, but "Installed" in a patch on the 5th), the system uses the status from the most recent action.
3. Aggregation: This results in a single, deduplicated list representing the final state of every update seen during the period.

info

A resource is also marked as Non-compliant if any qualifying action in the period is missing its execution logs (internal status "Logs Not Available"), as the system cannot guarantee that all updates were addressed.

Overall Compliance Status

Based on the aggregated data in the report, Fleet Control assigns a high-level Compliance Status to the resource. This is the status shown on the button used to open the report.

Status	Definition
Compliant	All updates in the report are in a satisfied state (Installed, Updated, or Removed). The resource is fully up-to-date according to the actions performed this month and no user intervention is needed.
Non-compliant	At least one update remains in an unsatisfied state (Available, Failed, or Pending Reboot), OR a qualifying action in the period failed to return logs (marked as "Logs Not Available").
N/A	No successful PATCH or SCAN actions were detected during the reporting period, so compliance cannot be determined.

CSV Export

You can download the raw data used to build the report by clicking Get CSV Report. This export includes the calculated status for every package, along with the specific Event and Action IDs that provided the data.