Posts tagged Patch Management
Who knew golf and IT had something in common besides that proven vendor sales tactic?
Oct 5th
by Karen Armor, Fiberlink I woke up this morning thinking about golf. 60 (brisk!) degrees and clear sunshine marks the beginning of autumn here in Pennsylvania, and I opened my eyes obsessing over the loss of my 7 iron. No, I didn’t physically lose it (although I’ve been known to leave my wedge on a More >
Patching – A Key Component of Vulnerability Management
Jun 22nd
by Clint Adams, Fiberlink There has been much security industry angst lately over some of the serious vulnerabilities introduced to the threat landscape by our friends at Apple, Adobe and Google. In particular, Adobe Flash and Acrobat have caused great concern and have focused the spotlight on applications as being a source of vulnerabilities. This More >
How MaaS360 Provides Better Patching
Jun 11th
by John Nielsen, Fiberlink In the last two posts we looked at statistics about patch management processes and four patch management capabilities that are missing from most patch management systems. In this post I want to look at how MaaS360 provides four capabilities that overcome these shortcomings. 1. Detailed Patch Reporting The MaaS360 Platform provides More >
Four Patch Management Problems
Jun 8th
by John Nielsen, Fiberlink In our previous post we presented some statistics showing that most organizations are not happy with their current patch management processes and tools. Today I am going to highlight four patch management capabilities that are missing from most patch management systems, that I think are responsible for some of this dissatisfaction. More >
Adobe’s Critical “Flaw” in Flash and your 35 second analysis
Jun 8th
by Jonathan Dale, Fiberlink On Cnetnews.com I saw the following headline “Adobe reports ‘critical’ flaw in Flash, Acrobat.” Unlike the typical viewer comments, I immediately thought about IT workers reading this, and what their reactions would be. I thought about the person who actually has to do something about this rather than argue why some More >
