Overview
On the Dashboard screen, the Patches Compliance tab provides an overview of your environment’s patching status, broken down by compliance metrics and operating system.
All Operating Systems Summary
Total Compliance
The percentage (rounded up) of endpoints that completed all required actions based on the associated remediation plans.
| Note: Endpoints that were not part of any remediation plan in the past are considered compliant and do not affect the Total Compliance calculation. |
| Metric | Calculation | Example (174 endpoints) |
| Total Compliance % | (total − pending − failed − exempted) / total | (174 − 0 − 7 − 39) / 174 = 74% |
| Applicable Endpoints | Endpoints JetPatch can theoretically patch. | 174 |
| Compliant Endpoints | total − in-progress − pending − failed − exempted | (174 − 0 − 0 − 7 − 39) = 128 |
| In-Progress Endpoints | Endpoints running a remediation action now (not exempted). | 0 |
| Pending Endpoints | Endpoints with a future maintenance schedule (not exempted). | 0 |
| Failed Endpoints | Endpoints that failed to execute a patch process or patch action. | 7 |
| Exempted Endpoints | Endpoints blocked from being patched (now and in future). Can be compliant. | 39 |
Applicable Endpoints — Detail
Non-applicable endpoints fall into two cases:
- Patching Inapplicable: Endpoints with an unsupported OS or not present in WSUS (Windows only).
- Unknown Endpoint: Endpoints discovered by Vulnerability Scanner integration.
How to calculate:
- Go to Endpoints → Management. Filter all Exemptions minus Unknown (number 1).
- Then filter only on Patching Inapplicable (number 2). Result: number 1 − number 2.
Exempted Endpoints - Exemption Types
Go to Endpoints → Management and filter with the following exemptions:
- Maintenance Window Required (when needed)
- Suspended By User
- Powered Off
- Power Suspended
- Power Unknown
- Untested Endpoint
- Invalid Credentials
- Unsupported PowerShell Execution Policy (from EP Readiness)
- Unsupported PowerShell Version (from EP Readiness)
- Advisories Not Exist (from EP Readiness)
- Packages Not Exist (from EP Readiness)
- Subscription Missing (from EP Readiness)
For more information, see Endpoint Exemptions and Warnings
Effective Compliance
The percentage (rounded up) of endpoints that completed all required actions based on the associated remediation plans, excluding exempted endpoints.
| Note: Endpoints that were not part of any remediation plan in the past are considered compliant and do not affect the Effective Compliance calculation. |
| Metric | Calculation | Example (174 endpoints) |
| Effective Compliance % | (total − pending − failed) / total | (174 − 0 − 7) / 189 = 96% |
| Applicable Endpoints | total − exempted | (174 − 37) = 135 |
| Compliant Endpoints | total − in-progress − pending − failed − exempted | (174 − 0 − 0 − 7 − 39) = 128 |
| In-Progress, Pending, Failed | Same as Total Compliance, excluding exempted endpoints. | — |
Detailed Data By Operating System
This section provides a breakdown of endpoint compliance by operating system.
| Column | Description |
| Total Endpoints | Total patch applicable endpoints in your environment (per OS). |
| In Progress | Same as Effective Compliance, per OS. |
| Exempted | Same as Effective Compliance, per OS. |
| Pending | Same as Effective Compliance, per OS. |
| Failed | Same as Effective Compliance, per OS. |
| Compliance | Same as Effective Compliance, per OS. |
Download Reports
There are two optional reports available for download:
| Report | Contents |
| Compliance Summary | Provides data detailed by operating system: Total Servers, Failed Servers, In-Progress Servers, Pending Servers, Exempted Servers, Compliant Servers. |
| SLA Summary | Provides the status of remediation plans according to their SLA time. |
Learn more about SLA Reports
Comments
0 comments
Please sign in to leave a comment.