Against a backdrop of constantly evolving cybersecurity threats, it’s essential that MSPs understand how to own the risk conversation if they are to really help their customers effectively manage their security posture. In this blog, I want to look at what we mean by “owning the risk conversation”, and how MSPs can achieve this. For me, I look at it from the perspective of my own job.
One of the things that I regularly get questioned about in my Operational Efficiency Boot Camp is the reporting in N-sight RMM and what MSPs should be presenting to customers to show that they are properly performing their work. I am a huge fan of monthly or quarterly business reviews to showcase your MSP client reports. I feel that for MSPs they are one of our greatest retention tools, and clearly demonstrate the value we provide.
The IT security landscape has been fundamentally transformed with the advent of cryptocurrencies, which have enabled hackers to easily monetize their activities without being tracked. This is one of the key drivers behind ransomware attacks becoming more numerous and more frequent.
Welcome to March! It’s a new month with a new MSP growth habit to start focusing on. In January, I encouraged you to Never Stop Learning to kick off our list of 12 MSP growth habits. In February, I urged you to go out and Find Love in the form of updating your MSP’s social proof for your website and social media feeds. For March it’s all about stepping out of your comfort zone and exploring new market opportunities to help expand your MSP business.
In my first two blogs in this series, I looked at some of the obvious signs and not so obvious signs that it might be time to change your RMM. However, the reality is that most MSPs don’t want to change unless they really have to, and in many of the cases I’ve seen they’re prepared to let things be bad for way too long.
In my last blog I took a look at some of what I see as the most obvious signs that your MSP business might have outgrown its RMM. These included: In this blog, I’m going to turn my attention to looking at some of the less obvious signs to reconsider your RMM.
When thinking about your strategy around backups, recovery, availability, and business continuity, one part of the plan tends to fall by the wayside: backup retention. We focus so much on things like recovery objectives, SLAs, and tiers of data, that our thinking revolves around the need to potentially recover the backup that we just made a matter of minutes afterward. But there are data sets that need to be available weeks, months—even years—after they are made.