Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud

Keys for Working with Modern MSSPs

How to determine what an MSSP can do for your organization, and the questions to ask before signing a contract.

Managed security service providers (MSSPs) are critical elements of a cybersecurity infrastructure for many organizations large and small. So what are some best practices for working with MSSPs?

As with the rest of the security industry, MSSPs are constantly evolving the services they offer and the way they work with their customers.

The first step in working with an MSSP is understanding what you need from the partnership. Maxine Holt, research director of security at Ovum, says the three basic steps in cybersecurity — prevent, detect, and respond — are where the discussion begins. In a presentation during the Cybersecurity Crash Course at Interop last week in Las Vegas, she recommended applying those three security processes to the seven stages of the Mitre ATT&CK kill chain to answer a critical question: Where do I have gaps in my coverage?

When it comes to filling those gaps, MSSPs tend to promise a lot, according to Fred Kwong, CISO at Delta Dental Plans Association, who also discussed MSSPs in a presentation at the Interop Cybersecurity Crash Course. Among the features an MSSP might offer to potential customers, he said, are 24 x 7 monitoring, qualified security pros watching your network full-time, advanced correlation between behaviors and incidents, and reduced time to detect intrusions — all at a lower cost to organizations than performing those tasks in-house.

When those features are broken into their individual functional components, the result is a significant laundry list of possible services. Kwong said that figuring out which of those tasks to contract out, and how deliverables on each are defined, are critical for defining the customer/MSSP partnership and who "owns" which part of the total cybersecurity process.

Holt said that two words should be at the top of the list during the discussion over ownership: integrate and automate. Integration is critical, she said, because even in those cases in which an MSSP will take over essentially all of a company's security functions, effective cybersecurity has to be integrated into the overall IT infrastructure.

And when a company looks for an MSSP to take over a portion of the cybersecurity function, then task can't have any functional or visibility gaps between it and the customer-owned parts of the infrastructure if it's to remain effective.

Ensure there are no functional or visibility gaps between the MSSP's duties and the customer-owned, on-premise infrastructure to ensure the outsourced function is doing the job required with the necessary level of integration with other security functions -- and at the price agreed upon in the contract.

No matter how the MSSP's services are integrated into the customer infrastructure, you can't outsource accountability, Kwong said. Regardless of the the contract language, the MSSP customer is ultimately responsible for making sure that their IT infrastructure is secure, both Kwong and Holt warned.

Related Content:

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-24285
PUBLISHED: 2021-04-12
INTELBRAS TELEFONE IP TIP200 version 60.61.75.22 allows an attacker to obtain sensitive information through /cgi-bin/cgiServer.exx.
CVE-2021-29379
PUBLISHED: 2021-04-12
** UNSUPPORTED WHEN ASSIGNED ** An issue was discovered on D-Link DIR-802 A1 devices through 1.00b05. Universal Plug and Play (UPnP) is enabled by default on port 1900. An attacker can perform command injection by injecting a payload into the Search Target (ST) field of the SSDP M-SEARCH discover pa...
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.