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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-3154
PUBLISHED: 2020-01-27
CRLF injection vulnerability in Zend\Mail (Zend_Mail) in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the header of an email.
CVE-2019-17190
PUBLISHED: 2020-01-27
A Local Privilege Escalation issue was discovered in Avast Secure Browser 76.0.1659.101. The vulnerability is due to an insecure ACL set by the AvastBrowserUpdate.exe (which is running as NT AUTHORITY\SYSTEM) when AvastSecureBrowser.exe checks for new updates. When the update check is triggered, the...
CVE-2014-8161
PUBLISHED: 2020-01-27
PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to obtain sensitive column values by triggering constraint violation and then reading the error message.
CVE-2014-9481
PUBLISHED: 2020-01-27
The Scribunto extension for MediaWiki allows remote attackers to obtain the rollback token and possibly other sensitive information via a crafted module, related to unstripping special page HTML.
CVE-2015-0241
PUBLISHED: 2020-01-27
The to_char function in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to cause a denial of service (crash) or possibly execute arbitrary code via a (1) large number of digits when processing a numeric ...