90% patch success rate in 30 days is too slow!
7.72 Days is the average delay between a vulnerability disclosure and attacks exploiting that vulnerability.
The importance of patching cannot be over stated.
As a mission critical process, do you monitor patch success on each endpoint? Do you have any backups in place when it fails?
According to the Ponemon Institute’s “State of Vulnerability Response Report”:
are lost coordinating activities across teams for every vulnerability patched.
A large US education establishment found
of their 40,000 endpoints were not rebooted after a patch update was deployed – that’s 1,000 potential entry points for bad actors.
Ponemon’s State of Vulnerability Response Report says that:
of breach victims said they were breached due to a known, unpatched vulnerability.
Most organizations face challenges with Microsoft SCCM due to huge infrastructure requirements and unmanaged clients. Customers also lack real-time and automation capabilities.
There are 5 key patching challenges with typical Enterprise patch management solutions like Microsoft SCCM:
- Endpoint Patch Readiness – If OS and services critical to patch success, like WMI and SCCM, are not working correctly, the patch won’t apply.
- Critical Asset Patching – Some endpoints are more critical to the business than others and cannot be given a standard maintenance window.
- Zero-Day Response – Patching tools are not designed to respond in real-time to zero-day vulnerabilities.
- The Dreaded Reboot – Users often put off rebooting as long as possible. Without a reboot the patch installed won’t take effect.
- Content Distribution – Distributing patch content simultaneously to all endpoints can cause business disruption. Companies often implement “Change Windows” to prevent this, which can lead to some endpoints not receiving the patch content when needed.
Each of these 5 issues create additional, repetitive manual tasks for IT, every patch deployment.
1E Patch Success provides automation to address these 5 issues.