Microsoft released this week information about an issue in their OS that has made hundreds of applications that run on Windows vulnerable to attack.
Remember the days of investment bankers and investors carrying around the Blackberry 850 that looked more pager than the start of today’s smart phone craze?
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 is in opposition to the old school thinking that the operating system is the culprit and that all things bad come from Microsoft.
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.
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.
Everyone agrees that patch management is core process for information technology groups. But they also agree that most organizations don’t do it very well.
How healthy are your laptops? It’s not a question people regularly ask themselves. They assume that as long as the end user isn’t calling the Help Desk, everything is fine. But this is rarely the case.