While the best of us remain pondering about a good new year's resolution, Small & Medium Business leadership seem to have theirs all figured out. Based on the NPD Group's latest report, businesses with 1,000 employees (or less) plan to invest in tablets in a big way over the next twelve months. And this isn't a trend among few; roughly three quarters (73%) of SMBs are on-board.

In recent months, I have heard and read the term Mobile Device Management many  times  whenever the topic of Smartphones (specifically iPhones and Androids in the corporate environment) is brought up.  Discussion drifts towards the ever increasing need to get a grip on the consumerization and proliferation of Smartphones. The goal today is to offer some perspective on the meaning of “Mobile Device Management” (MDM) and how MDM and security intersect.

The MaaSters Center is pleased to welcome Maribel Lopez from Lopez Research as a member and contributor. Maribel will provide her insights and commentary on the rapidly changing Mobile Landscape in a series focused on the challenges faced by IT departments, the importance of Enterprise Mobility Management (EMM), and which functions are important when choosing an EMM solution. 

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?

The financial industry is of course highly regulated. But what financial industry regulations and standards apply specifically to endpoints, and to data stored on mobile and distributed devices?

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.