A prioritization of automated application patching to reduce the risk of data breaches
Firmware patching may be a newer priority for IT teams, but application patching has been a key focus for many years. Companies spend about 320 hours a week on vulnerability response — equivalent to eight workers devoting full-time focus to application patching. Still, about 60% of data breaches originate from a known, unpatched vulnerability.
Similarly, one-third of ransomware attacks originate with an unpatched vulnerability. In 2022, an estimated 55% of those incidents were caused by two vulnerabilities that had patches available — ProxyShell, a chain of exploits targeting three known vulnerabilities in Microsoft Exchange Servers, and Log4Shell, a vulnerability found in a common Java-based logging library used in a variety of applications.
Furthermore, there is evidence that ransomware breaches that start in this way are far more devastating for the victims than breaches that start with compromised credentials. Ransomware breaches that exploit unpatched vulnerabilities have four times higher overall attack recovery costs ($3M vs. $750k for compromised credentials) as well as a slower recovery time (45% took more than a month vs. 37% for compromised credentials).
There are a number of factors that can make patch management challenging for IT teams, including the vast number of patches released every day; the continued use of legacy and unsupported technology; a lack of visibility into vulnerabilities; and the ever-expanding number of software and systems many IT teams are managing.
More than half of organizations say they are at a disadvantage in responding to vulnerabilities because they use manual processes.
In addition, many teams follow risk-based prioritization of patches, where the vulnerabilities deemed most critical receive the swiftest attention. However, this can lead to presumably “lower- risk” vulnerabilities remaining unpatched and, sometimes, forgotten over time — until an attacker finds and exploits them.
What is changing: