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

9/27/2019
10:00 AM
Himanshu Verma
Himanshu Verma
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
100%
0%

Is Your Organization Suffering from Security Tool Sprawl?

Most companies have too many tools, causing increased costs and security issues.

The advent of the cloud and software-as-a-service (SaaS) applications has given the IT industry many advantages, including increased agility and availability. Unfortunately, the trend has also significantly contributed to the growing issue of tool sprawl — the use of too many one-off specialized solutions — for both virtualized and point solutions.

Tool sprawl hurts IT productivity, resulting in troublesome management workflows and high costs. The compelling ease of deployment and flexibility of the cloud has led many organizations to adopt and deploy a wide roster of security solutions without having a comprehensive security strategy in place. According to a Forrester survey of IT decision-makers, 55% of respondents report having 20 or more tools between security and operations, and 70% say these tools lack full integration. For security specifically, simply deploying more technologies isn't the best way to stop breaches — in fact, it can be the opposite. 

A common side effect of security tool sprawl is exposure to vulnerabilities and backdoors to serious threats. Hackers often exploit vulnerabilities in tools that do not communicate securely or are not regularly updated. With a piecemeal approach, your network can be open to threats that are commonly used for reconnaissance in early stages, as well as lateral movement and pivoting in later stages of an attack.

Each year, IT spending increases while countless new tools enter the market. Mergers and acquisitions increase tool sprawl as well. When one company absorbs another, they must integrate two entirely different IT infrastructures and inevitably some of the pieces overlap. Disentangling all of them is often not practical, and the new business winds up with multiple tools that serve the same function and often don't integrate with one another.

The growing adoption of cloud management and cloud infrastructure makes this worse, since things like endpoint solutions and workstation instances running in public cloud infrastructures are much more likely to be overlooked in the integration process. According to a recent 451 Research survey, 39% of respondents juggle 11 to 30 monitoring tools to keep an eye on their application, infrastructure, and cloud environments — with 8% using between 21 and 30 tools! Rather than offering better visibility, adopting too many tools can result in high costs, inefficiencies, cumbersome workflows, and potential weak spots if security solutions aren't deployed and managed strategically.

Be On Guard
Every organization should be on guard against security tool sprawl. With the increase in IT security spending and the growing adoption of new defense technologies, network administrators often find themselves toggling between a large roster of security solutions with overlapping use cases and functionality — sometimes across up to 10 or more in specific functional areas (based on conversations I've had network admin customers and resellers who work with them). This creates many issues, including everything from licensing costs to reduced productivity and increased chances of missing or mishandling critical patches and bug fixes.

IT decision-makers within organizations of all sizes should focus on putting measures into place that curb security tool sprawl and curtail the serious security issues that can arise as a result. Here are several key best practices that every organization can use to avoid security tool sprawl:

1. Clearly identify the scope and entities of coverage required before deploying a new security tool. It's critical that you understand the various components of the IT infrastructure at hand (that is, network, endpoint, wireless, identities, etc.) and map security coverage across individual use cases (such as users, applications, physical, virtual, etc.). This will allow you to explore opportunities for consolidation when choosing the appropriate security solutions.

2. Take a platform-based approach to security, leveraging connectors and integrations. Look for platforms that offer layered security services across multiple use cases with a wide breadth of coverage either natively or with seamless technology integrations.

3. Segment your infrastructure based on intent. Logical segmentation can allow you to isolate critical assets. Network segmentation, microsegmentation, and macrosegmentation will all allow you to establish a secure environment and limit the exposure in distributed environments.

4. Take a unified approach to security monitoring. Ensure that you can centralize operations data and deploy strong tools to run analytics across a broad data set.

5. Implement strong, comprehensive access controls. Workflow-based multifactor authentication for users accessing applications and resources from devices can dramatically reduce, and even eliminate, the risk of security loopholes.

As the industry continues to adopt security tools delivered via convenient cloud services and SaaS-based procurement models, it will become increasingly important to identify and root out the inefficiencies and exposures caused by security tool sprawl. If you ignore this growing issue, potential data breaches could make the exorbitant costs and burdensome management associated with security tool sprawl the least of your worries. It's the timeless "quality over quantity" argument. Businesses of all sizes must adopt simplified, unified security platforms that eliminate the need for so many point solutions — full stop.

Related Content:

 

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "Why Clouds Keep Leaking Data."

Himanshu Verma is a Director of Business Development at WatchGuard Technologies, with a primary focus on delivering WatchGuard products and solutions to strategic partners and the managed security service providers (MSSP) market. Prior to WatchGuard, he held product ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Sodinokibi Ransomware: Where Attackers' Money Goes
Kelly Sheridan, Staff Editor, Dark Reading,  10/15/2019
Data Privacy Protections for the Most Vulnerable -- Children
Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
State of SMB Insecurity by the Numbers
Ericka Chickowski, Contributing Writer,  10/17/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16404
PUBLISHED: 2019-10-21
Authenticated SQL Injection in interface/forms/eye_mag/js/eye_base.php in OpenEMR through 5.0.2 allows a user to extract arbitrary data from the openemr database via a non-parameterized INSERT INTO statement, as demonstrated by the providerID parameter.
CVE-2019-17400
PUBLISHED: 2019-10-21
The unoconv package before 0.9 mishandles untrusted pathnames, leading to SSRF and local file inclusion.
CVE-2019-17498
PUBLISHED: 2019-10-21
In libssh2 v1.9.0 and earlier versions, the SSH_MSG_DISCONNECT logic in packet.c has an integer overflow in a bounds check, enabling an attacker to specify an arbitrary (out-of-bounds) offset for a subsequent memory read. A crafted SSH server may be able to disclose sensitive information or cause a ...
CVE-2019-16969
PUBLISHED: 2019-10-21
In FusionPBX up to 4.5.7, the file app\fifo_list\fifo_interactive.php uses an unsanitized "c" variable coming from the URL, which is reflected in HTML, leading to XSS.
CVE-2019-16974
PUBLISHED: 2019-10-21
In FusionPBX up to 4.5.7, the file app\contacts\contact_times.php uses an unsanitized "id" variable coming from the URL, which is reflected in HTML, leading to XSS.