Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
security:ratings [2018-07-02 11:57] Martin Berg |
security:ratings [2018-07-02 11:58] Martin Berg |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Priority and Severity | + | ====== Priority and severity |
This is a guideline to help our customers prioritize updates and to assess the security impact of known software vulnerabilities. | This is a guideline to help our customers prioritize updates and to assess the security impact of known software vulnerabilities. | ||
Line 5: | Line 5: | ||
The definitions of the priority ratings are: | The definitions of the priority ratings are: | ||
- | ^ Rating | + | ^ Priority |
- | | Priority | + | | 1 | This update resolves vulnerabilities being targeted, or which have a higher risk of being targeted, by exploit(s) in the wild for a given product version and platform. Lime recommends administrators install the update as soon as possible. (for example, within 72 hours). |
- | | Priority | + | | 2 | This update resolves vulnerabilities in a product that has historically been at elevated risk. There are currently no known exploits. Based on previous experience, we do not anticipate exploits are imminent. As a best practice, Lime recommends administrators install the update soon (for example, within 30 days). |
- | | Priority | + | | 3 | This update resolves vulnerabilities in a product that has historically not been a target for attackers. Lime recommends administrators install the update at their discretion. |
===== Severity ratings ===== | ===== Severity ratings ===== | ||
The definitions of the severity ratings are: | The definitions of the severity ratings are: | ||
- | ^ Rating | + | ^ Severity |
| Critical | | Critical | ||
| Important | | Important | ||
| Moderate | | Moderate | ||