Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
security:ratings [2018-07-02 12:18]
Martin Berg
security:ratings [2018-12-02 22:09] (current)
Line 7: Line 7:
 ^ Priority ​ ^ Definition ​ ^ ^ Priority ​ ^ Definition ​ ^
 |  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). ​ | |  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). ​ |
-|  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). ​ |+|  2  | This update resolves vulnerabilities in a product that could be 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). ​ |
 |  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. ​ | |  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. ​ |
  
  • Last modified: 20 months ago
  • (external edit)