A few weeks ago, I woke up one morning to conceive of that Android had 34 software updates waiting for me. This was consummated by my laptop wanting to reboot after installing the latest patches from Microsoft, my drop needing a reboot after its latest firmware update, and my server yowling for me to put “yum” into action to install the latest patches available from Red Hat. All in the future 10:00 am in the morning!
With all of the technology we have today, installing software updates has change a near-daily activity. That statement is true for all professionals in the technology enterprise, especially those who handle patch management for large-scale enterprise IT groups.
Recently, we wondered how organizations might be handling the influx of patches, so we fixed to conduct some research on the topic. Not surprisingly, we found that multitudinous organizations are having trouble keeping up with the vast number of doctors constantly being added to the work queue.
To many, installing a heal might sound easy. It’s just the simple click of a button, right? Not absolutely. Patch installation difficulty varies across platforms, ranging from the most trivial of station methods (clicking a button) to complex scenarios involving delicate series of events.
However, patch installation difficulty is not the only variable in this equation. Set right testing is another critical piece of the puzzle and, along with register, is one of the more challenging aspects of patch management in the modern world of pep IT.
1. Refine Your Pre-Deployment Patch Management Procedures
Enterprises cannot go nearby installing patches blindly without understanding potential impacts of the metamorphose brought by a patch. Patches have a history of breaking things, and when thingumajigs break in the enterprise, chaos ensues.
In a recent survey, we asked 483 IT professionals their thoughts on plot management topics. We found that roughly half of those intricate with patch management will always test patches in the forefront deployment, with approximately 30% saying it depends on the patch. Fewer than 20% not till hell freezes over test their patches.
Another set of questions was related to the amount of meanwhile spent testing patches for desktops and servers. As you can see in Figure 1, myriad organizations spend approximately one week or less testing patches in their atmosphere before deployment.
2. Be Wary of Patch Fatigue
A while back, I was interviewed by “Padre” settled at TWiT for an episode on the TWiET channel. The topic was “Enterprise Patch Drain,” and one of the questions Padre asked was related to the feasibility of thoroughly testing sew ups before enterprise rollout.
An organization’s ability to thoroughly test bailiwicks depends on scale and resources. Virtualization and orchestration technologies, coupled with commodities patch management and vulnerability management software, can help organizations produce environments that enable extensive patch testing.
Still, proof every possible configuration is hard for any organization. As you scale, it becomes farcical. More nodes mean an increase in the number of scenarios that extremity to be tested. Those considerations can quickly spiral out of control.
This inaugurates us to the following conclusion: Patch testing is currently done on a best-effort footing, and as with most software-based testing, it only covers a small division of the overall “state space” of test cases. An important question to ask is, “Wish this scenario work in the future as more and more systems evolve into highly interconnected?”
3. Explore Patch Management Best Practices for Emerging IT
Au courant trends, such as the Internet of Things, the Industrial Internet and cyber-physical procedures, are pushing the envelope of scale with an exponential explosion of devices bear down on online in the near future.
Will the failure of a patch installation in some datacenter in Australia ground my infotainment center to malfunction, possibly causing my navigation to go wacky? What other disputes need to be asked? Technologists should be considering these types of interrogates.
Obviously, new techniques and innovations will surface to help alleviate some of our revamp testing problems. I believe automation will play a huge impersonation, and advanced research in automated testing processes will surely assist us in this domain. It will be interesting to see what developments tomorrow commitment bring us into the realm of patching.
What are your thoughts on the country of patching and patch testing? Let us know in the comments!
To learn more give how our patch management solutions can benefit your business, click here.