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
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7263
PUBLISHED: 2020-04-01
Improper access control vulnerability in ESConfigTool.exe in ENS for Windows all current versions allows a local administrator to alter the ENS configuration up to and including disabling all protection offered by ENS via insecurely implemented encryption of configuration for export and import.
CVE-2020-7066
PUBLISHED: 2020-04-01
In PHP versions 7.2.x below 7.2.9, 7.3.x below 7.3.16 and 7.4.x below 7.4.34, while using get_headers() with user-supplied URL, if the URL contains zero (\0) character, the URL will be silently truncated at it. This may cause some software to make incorrect assumptions about the target of the get_he...
CVE-2020-11445
PUBLISHED: 2020-04-01
TP-Link cloud cameras through 2020-02-09 allow remote attackers to bypass authentication and obtain sensitive information via vectors involving a Wi-Fi session with GPS enabled, aka CNVD-2020-04855.
CVE-2020-7064
PUBLISHED: 2020-04-01
In PHP versions 7.2.x below 7.2.9, 7.3.x below 7.3.16 and 7.4.x below 7.4.34, while parsing EXIF data with exif_read_data() function, it is possible for malicious data to cause PHP to read one byte of uninitialized memory. This could potentially lead to information disclosure or crash.
CVE-2020-7065
PUBLISHED: 2020-04-01
In PHP versions 7.3.x below 7.3.16 and 7.4.x below 7.4.34, while using mb_strtolower() function with UTF-32LE encoding, certain invalid strings could cause PHP to overwrite stack-allocated buffer. This could lead to memory corruption, crashes and potentially code execution.