1. Take an inventory of your common office environment and determine which programs use auto update engines and more importantly, which do not. 2. If possible, disable each of the auto update engines to save system resources and potentially unwarranted outbound connections. 3. Perform a vulnerability assessment on a regular basis to determine which third-party patches need to be deployed to keep the endpoint secure. 4. Download and test each patch and determine if it is safe to deploy to the entire environment. 5. Use a mitigation procedure such as patch management and vulnerability assessment to verify patch deployment and remediation of vulnerabilities.Essentially, after this little exercise I have stopped all my auto update programs and rely exclusively on my vulnerability assessment solution to tell me when to patch on a routine and predictable basis. Then I can run the tools manually to retrieve the patches, conserve resources, prevent unwanted outbound connections, and mitigate the risk of malware taking control of my update engines. This practice is not necessarily viable for every home user, but strongly recommended for businesses where the end-user is not permitted to perform the updates themselves.
Morey J. Haber, Chief Technology Officer and Chief Information Security Officer at BeyondTrust
Morey J. Haber is Chief Technology Officer and Chief Information Security Officer at BeyondTrust. He has more than 25 years of IT industry experience and has authored four Apress books: Privileged Attack Vectors (2 Editions), Asset Attack Vectors, and Identity Attack Vectors. In 2018, Bomgar acquired BeyondTrust and retained the BeyondTrust name. He originally joined BeyondTrust in 2012 as a part of the eEye Digital Security acquisition. Morey currently oversees BeyondTrust strategy for privileged access management and remote access solutions. In 2004, he joined eEye as Director of Security Engineering and was responsible for strategic business discussions and vulnerability management architectures in Fortune 500 clients. Prior to eEye, he was Development Manager for Computer Associates, Inc. (CA), responsible for new product beta cycles and named customer accounts. He began his career as Reliability and Maintainability Engineer for a government contractor building flight and training simulators. He earned a Bachelor of Science degree in Electrical Engineering from the State University of New York at Stony Brook.