Sponsored By

Don’t Let Your MSP Be a Security Weak PointDon’t Let Your MSP Be a Security Weak Point

Do your due diligence before committing to a managed service provider.

Gary Audin

July 10, 2020

3 Min Read
Cybersecurity locks
Image: Maksim Kabakou - stock.adobe.com

Many businesses outsource the management of IT and network resources to managed service providers (MSPs), and some use managed security service providers (MSSPs), as well. These are important partners, but they can introduce risk, too, since they can serve as the launching platform for attacks into customer systems.

 

Attackers often target MSPs/MSSPs since compromising their networks can potentially net them access to multiple businesses. If an attacker can compromise a business network, it can then move into critical systems, learn workflows, and, ultimately, steal money or valuable information such as credit card data.

 

Ransomware is another preferred method of attack. And attackers can negatively impact customer experience, create system downtime, or cause the business to shut down operations temporarily.

 

Building Trust

Attacks via trusted partners that have privileged access to your resources can qualify as insider threats, the same as threats from employees. To build trust, first look at your MSP/MSSP agreements. If they contain goals, be aware: They’re not enforceable. What you need are concrete, measurable statements.

 

That said, credits for problems may look good on paper, but they’ll probably do little to cover the costs of an attack. In some cases, I’ve found that the customer’s work to report and verify the attack costs more than the credits, discouraging the reporting process entirely.

 

You need to review the security processes of the MSP/MSSP and compare them to what you would do internally on your own. The MSP/MSSP’s processes should be better than what you would implement. Look into the experiences of an MSP/MSSP and how it has prevented or mitigated attacks for other customers. If an MSP/MSSP will not share this information with you, ask why. You don’t need to know the identity of the customer attacked, but you should know what happened and how the MSP/MSSP responded.

 

Limiting Damages

Using an MSP/MSSP doesn’t absolve your organization from security responsibilities. Ensure that your users are familiar with security processes and procedures and that they understand that security is their responsibility. Provide training — and don’t forget contract workers. Contractors can be another weakness in your security posture.

 

As I mentioned previously, make sure you’ve properly secured your privileged access super users. Don’t assume they do everything right; they can make mistakes or be negligent — especially when they’re overworked. Ensure that your MSP/MSSP is following your privileged access policies and procedures, and that you can get a full audit of the provider’s actions. Staff turnover, illnesses, and new employees may open security holes.

 

Keep your service-level agreement current. Analyze what the SLA does and doesn’t cover — you may discover that some security holes don’t fall under the SLA’s purview. Every time your provider updates the SLA, look at the changed provisions. They may not favor your business. This means that you’ll probably have to provide some of your own security solutions because the SLA doesn’t cover everything you want.

 

The MSP/MSSP should audit its performance and formally report the results. The audit should cover the business’s employees, consultants, contractors, vendors, and service providers. The MSP/MSSP may not be able to enforce security procedures on everyone, but it should be able to report on weaknesses discovered. In addition, the MSP/MSSP should regularly scan for security vulnerabilities and report the results, as I’ve written in the post, “Network Analytics: Checklist for Failure.” When vulnerabilities are discovered, the MSP/MSSP should provide a report of the actions taken to mitigate the vulnerabilities.

 

The security landscape is constantly changing. As customers protect themselves, attackers develop new methods of attack. Fixing identified vulnerabilities fast will reduce the possibility of attacks, whereas waiting for a convenient time will leave your business open to attack.

About the Author

Gary Audin

Gary Audin is the President of Delphi, Inc. He has more than 40 years of computer, communications and security experience. He has planned, designed, specified, implemented and operated data, LAN and telephone networks. These have included local area, national and international networks as well as VoIP and IP convergent networks in the U.S., Canada, Europe, Australia, Asia and Caribbean. He has advised domestic and international venture capital and investment bankers in communications, VoIP, and microprocessor technologies.

For 30+ years, Gary has been an independent communications and security consultant. Beginning his career in the USAF as an R&D officer in military intelligence and data communications, Gary was decorated for his accomplishments in these areas.

Mr. Audin has been published extensively in the Business Communications Review, ACUTA Journal, Computer Weekly, Telecom Reseller, Data Communications Magazine, Infosystems, Computerworld, Computer Business News, Auerbach Publications and other magazines. He has been Keynote speaker at many user conferences and delivered many webcasts on VoIP and IP communications technologies from 2004 through 2009. He is a founder of the ANSI X.9 committee, a senior member of the IEEE, and is on the steering committee for the VoiceCon conference. Most of his articles can be found on www.webtorials.com and www.acuta.org. In addition to www.nojitter.com, he publishes technical tips at www.Searchvoip.com.