5 Biggest Mistakes In Patch Management
Patching is a major challenge for IT professionals everywhere. Find out how to avoid making the top mistakes that can significantly impact your environment.
1. Putting Off Patching
There is no question: you need to patch.
Every software product has bugs and many have security vulnerabilities. Unfortunately, people around the world, including security services are trying to find and exploit these holes. The vast majority of security events are attack vulnerabilities that have already been addressed.
For example, in the case of WannaCry, Microsoft released an update that addressed the vulnerability two months prior to the worldwide attack. By putting off patching, you leave your environment completely vulnerable to exploits and ransomware.
There is no excuse for not having a strong patch management strategy. This doesn’t mean worrying about it for a week every time something like WannaCry hits the press. When the next doomsday strikes, you should be completely bulletproof.
2. Giving Admin Rights to Everyone
One approach for patching is giving all users local administrator rights to let them take care of patching. What are the issues with this approach? Will all users install those patches?
We’ve seen Windows Update reporting 100+ patches waiting to be installed. By giving users administrator rights, you are creating a huge future attack surface. Typically end users are not as vigilant about clicking to links in emails and opening attachments that might now infect their PC utilizing their administrator rights.
Once infected, the local network can be leveraged to distribute the infection. Even in locked down environments, if an application is having trouble running, granting administrator rights will solve the problem but also create a new security gap.
It is worth the time to work out the specific permissions needed by an application rather than granting blanket administrator rights. There are simply too many risks involved.
3. Letting Vendors Auto-Update
Many operating systems and third-party applications have self-updating technology. This might seem like a great idea, however if devices are correctly locked down, the user may not have permissions to install the updates. By allowing the vendor to push out updates, there is a chance you will end-up breaking critical business applications.
One of the best examples of this is Java updates. Unfortunately, patches don’t go through the same level of software testing that a full software release typically might. This means patches can often have their own significant bugs. We have seen many examples of companies like Microsoft recalling patches because of major issues.
4. Relying on WSUS
Microsoft provides enterprises a popular tool to manage software updates: Windows Server Updates Services (WSUS). However, many organizations make the mistake of thinking they are protected because they use this program. WSUS does not provide sufficient reporting, so as an administrator there is no way to know if you are completely protected.
Questions you should be asking:
WSUS also focuses on distributing Microsoft’s own patches, but what about third-party software applications or non-Microsoft operating systems? It’s important to always reevaluate your approach.
5. Not Thinking Bigger
Even with a locked down security environment or running WSUS, you could still be at risk. What about your Linux and Mac devices? What about social engineering attacks that cause users to give up usernames and passwords? What about third-party applications, such as Adobe Flash and Java?
Patch management best practices are crucial. It’s important to select a solution that overcomes the key challenges in developing a patch management process.
How Patch Management with Syxsense Helps
Experience the Power of Syxsense
Syxsense has created innovative and intuitive technology that sees and knows everything. Manage and secure your environment with a simple and powerful solution.