Working with Service Level Agreements
While configuring SLAs, you specify a deadline (period in days before which the missing patches or vulnerabilities must be remediated) and a warning threshold (period in days after which the missing patches or vulnerabilities run into the risk of missing the deadline). SLAs for all risk scores (severity levels) are preconfigured with default values.
By default, warning thresholds are set to 80% of the deadline period. For example, for a risk score (severity level) of 5 - Critical, if the Deadline is set as 30 days, the Warning Threshold is at 24 days.
On the Automation Console Dashboard, the total number of assets in your environment and the number of assets according to their Service Level Agreement (SLA) levels appears. For more information, see Using-dashboards.
To update Service Level Agreements
On the Configuration > Manage SLA page, update the values in the Deadline and Warning Threshold fields for the Patch and Vulnerability Risk Scores (Severity Levels) and save the changes.
The following figure shows the out-of-the-box SLAs defined in the product.
The following table describes the mapping between the vendor severity levels and the patch risk scores (severity levels) in Automation Console.
Risk Score (Severity) | Windows | Red Hat Enterprise Linux (Errata Severity) |
|---|---|---|
5 - Critical | Critical | Critical |
4 - High | Important | Important |
3 - Medium | Moderate | Moderate |
2 - Low | Low | Low |
1 - Information | - | - |
0 - Unknown | Unknown | No severity specified. |
Click Reset to restore the default values.