KRACK Wi-Fi Vulnerability Puts Patch Management in the Spotlight
Teams across our company are hard at work testing, validating and implementing the many new patches being released from vendors, including Cisco and Microsoft, as a result of the KRACK (‘Key Reinstallation Attacks’) vulnerability.
Warnings around the new vulnerability, KRACK, made headlines earlier this week as its identification meant that virtually any Wi-Fi enabled device could be made vulnerable to exploit. This latest exploit also reinforces the importance of being prepared to execute both reactive and proactive patch management measures.
Yet when it comes to patch management, most firms do not have the internal resources necessary to effectively monitor, test and roll-out patches in a timely fashion. Remember the Equifax breach? It is widely reported the Equifax breach occurred because the company missed a patch to address an application vulnerability, which the criminals later exploited.
You Need a Patch Management Service
Outdated systems are dangerous yet all systems can become dangerous if left unpatched. That’s why we recommend looking at a patch management service. Companies – such as Eze Castle Integration! – can provide fully managed patch services to ensure software and firmware remain up-to-date and are proactively monitored to prevent security bugs and malicious exploits, reducing overall firm risk.
To give you more insight into how a centralized patch management service can benefit your firm, here’s a look at how our Eze Patch Management Service works, spear-headed by our Network Operations team.
Our NetOps team takes a three-phased approach to patch management, with the end goal of reducing as much overall risk to the client as possible. The three phases include:
Testing: Immediately after a patch is issued by the software provider (i.e. Microsoft), NetOps deploys the patch to a lab environment that simulates a client infrastructure. This testing phase allows our team to identify any unforeseen issues and make adjustments as necessary before issuing updates more broadly.
Piloting: Shortly after the testing phase, patches are deployed to ‘pilot’ clients and early adopters, providing NetOps with additional insight into the effectiveness of the patch.
Production: Finally, during the production phase, all subscribed clients are issued the necessary patches. Ongoing monitoring takes place to ensure patches are applied as intended.
Learn more about Eze Patch Management Service here, and contact us at firstname.lastname@example.org to speak with an expert.