Partner Perspectives  Connecting marketers to our tech communities.
SPONSORED BY
9/13/2017
09:00 AM
Craig Dods
Craig Dods
Partner Perspectives
Connect Directly
Twitter
RSS
50%
50%

Detection, Prevention & the Single-Vendor Syndrome

Why security teams need to integrate 'Defense in Depth' principles into traditional solutions designed with integration and continuity in mind.

It’s a controversial statement, particularly when it comes from a security vendor, but it must be said: No single vendor can adequately protect your enterprise from all of today’s threats, let alone what might be on the horizon.

There is a misconception today that "complete prevention" is a realistic goal for an enterprise security program. As an adversary’s level of sophistication increases, the ability and efficacy of a single product at preventing arbitrary intrusions begins to decrease dramatically. As a result, security teams need to adopt a new mantra:  Given sufficient time, motivation, and funding, a sufficiently capable adversary will find their way into your organization, regardless of the tools that you have deployed.

One can simply recall the tale of djbdns and how its touted impenetrable "secure code" written by cryptographer Daniel J. Bernstein, failed to stand up to focused scrutiny. The story, as reported by The Register in 2009, is a cautionary tale about assumptions that organizations continue to make about the vulnerabilities of many devices and applications running on the typical enterprise network.

Knowing that the development of a perfectly secure application, system, or device is effectively impossible, we must shift our focus from "prevention” towards "rapid detection, coordination, and response." 

Regardless of market buzzwords, all vendors try to accomplish the same end goals by leveraging similar techniques and technologies. As discussed at this year’s BlackHat by Lidia Giuliano and Mike Spaulding (Lies, and Damn Lies), unsurprisingly, each vendor, based on their unique implementations,  have certain strengths and weaknesses, depending on the type of attack or technique being tested.

Consider the following scenario:

  • Product “A” may be able to detect attack “x”
  • Product “B” may be able to detect behavior "y"
  • Product "C" is unable to detect either "x" or "y," but is best positioned within the network to take the most effective action against the attacker
  • As is typical in the modern enterprise, Product A, B, and C are managed by separate teams and do not share the same reporting or communication structure.

This is a scenario to which many enterprises are now being exposed to, generally for the first time during post-breach incident response and forensics. Tools that they may have had in place detected portions of the attacker’s activity, but none were able to combine their results together to take effective action against the intruder in a timely fashion.

As a result, security teams are beginning to realize that due to the overwhelming volume and increasing sophistication of the modern threat landscape, they must now combine the proverbial "Defense in Depth" principle with solutions that are designed with integration and continuity in mind.  This means they need to prioritize partnering with companies whose cybersecurity offerings are open in nature and seamlessly augment security operations with automated detection, enforcement and remediation. Only in doing so can they maximize their chances of success against a motivated attacker.

Craig Dods is the Chief Architect for Security within Juniper Networks' Strategic Verticals. He currently maintains top-level industry certifications, holds multiple networking and security-related patents, and has disclosed multiple critical-level CVE's in a responsible ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Cracking 2FA: How It's Done and How to Stay Safe
Kelly Sheridan, Staff Editor, Dark Reading,  5/17/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: "The one you have not seen, won't be remembered".
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10428
PUBLISHED: 2018-05-23
ILIAS before 5.1.26, 5.2.x before 5.2.15, and 5.3.x before 5.3.4, due to inconsistencies in parameter handling, is vulnerable to various instances of reflected cross-site-scripting.
CVE-2018-6495
PUBLISHED: 2018-05-23
Cross-Site Scripting (XSS) in Micro Focus Universal CMDB, version 10.20, 10.21, 10.22, 10.30, 10.31, 10.32, 10.33, 11.0, CMS, version 4.10, 4.11, 4.12, 4.13, 4.14, 4.15.1 and Micro Focus UCMDB Browser, version 4.10, 4.11, 4.12, 4.13, 4.14, 4.15.1. This vulnerability could be remotely exploited to al...
CVE-2018-10653
PUBLISHED: 2018-05-23
There is an XML External Entity (XXE) Processing Vulnerability in Citrix XenMobile Server 10.8 before RP2 and 10.7 before RP3.
CVE-2018-10654
PUBLISHED: 2018-05-23
There is a Hazelcast Library Java Deserialization Vulnerability in Citrix XenMobile Server 10.8 before RP2 and 10.7 before RP3.
CVE-2018-10648
PUBLISHED: 2018-05-23
There are Unauthenticated File Upload Vulnerabilities in Citrix XenMobile Server 10.8 before RP2 and 10.7 before RP3.