The Wrong Way to Pick a Security Vendor
Credit to Author: Ryan Delany| Date: Mon, 14 Aug 2017 12:00:34 +0000
For a number of years, we’ve worked with and supported our Managed Service Provider (MSP) partners at Trend Micro and I’ve seen and heard a lot in that time.
Over time, we’ve noticed a few trends when it comes to MSPs choosing a security vendor to partner with, and in an effort to save you some trouble and heartache, have decided to share some insights below.
Coincidentally, it is interesting to note that there is a strong correlation between business maturity and the likelihood of choosing a particular option in this list. For example, we tend to see that less experienced MSPs usually follow the first few options, whereas more mature MSPs take on the last few approaches. In other words, MSPs tend to progress through these options during the life of their business.
The “I just let my customers handle it” approach
This is usually the first tactic when beginning the new MSP security journey. Starting an MSP business can be overwhelming. With several factors to consider, such as choosing Professional Service Automation (PSA) and Remote Management and Monitoring (RMM) tools, defining your offerings, researching and validating technical solutions, creating marketing plans and finding customers. Security is just one small, albeit important, part of an MSP offering. For that reason, many MSPs will simply leave sleeping dogs lie when it comes to security, which ultimately means leaving existing solutions and licenses in place, to deal with them at a later point in time.
Why I think this is a bad option:
| |
The “I’ll just manage whatever the customer has” approach
This tends to be the second evolution an MSP goes through as they are growing their business. At this point, business has settled down, processes have been implemented and the machine is humming along nicely. Similar to how lightning finds the shortest path to ground when it strikes, this is the shortest path for an MSP to “offer” security without going through the effort of testing, vetting, choosing, training and implementing a consistent security solution.
Why I think this is a bad option:
| |
The “I don’t want to put all my eggs in one basket” approach
This one is a bit of a variation on the previous method. Essentially this is when MSPs intentionally choose to manage multiple security solutions across their customer base in the event that one solution fails, the MSP can reduce the potential impact to all its customers.
Why I think this is a bad option:
| |
Picking the cheapest option
In our experience in talking to partners throughout the years, this is generally one of the most common paths chosen by MSPs for obvious reasons. While it could be argued that the whole premise behind the MSP business model is to blame here, that still doesn’t make it a good choice.
Why I think this is a bad option:
| |
Picking the integrated option
This is probably the most common approach we see these days as RMM vendors have partnered up with one or more of the lower cost and reduced functionality security products. On paper, this sounds like a great idea but is actually fraught with many issues.
However, the main takeaways and why I think this is a bad option include:
| |
Having a security solution deployed across your entire customer base that is independent of the RMM vendor insulates you from changes outside of your control and protects your bottom line.