theDocumentId => 1335936 8 Microsegmentation Pitfalls to Avoid

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.

Operations

9/30/2019
09:00 AM
Connect Directly
Twitter
RSS
E-Mail

8 Microsegmentation Pitfalls to Avoid

Don't fall victim to these common mistakes on the path to developing better security boundaries and limiting the blast radius of security incidents.
2 of 9

Overly Complex Metrics
'The biggest mistake you should strive to avoid here is adding unnecessary complexity. The simpler a solution is, the less room there is for a costly mistake that could lead to a breach. This also makes it easier for new employees to be brought up to speed on managing your solutions, applications, and services.'
-Marc Laliberte, senior security analyst, WatchGuard Technologies

Image Source: Marc Laliberte/WatchGuard Technologies

Overly Complex Metrics

"The biggest mistake you should strive to avoid here is adding unnecessary complexity. The simpler a solution is, the less room there is for a costly mistake that could lead to a breach. This also makes it easier for new employees to be brought up to speed on managing your solutions, applications, and services."
Marc Laliberte, senior security analyst, WatchGuard Technologies

Image Source: Marc Laliberte/WatchGuard Technologies

2 of 9
Comment  | 
Print  | 
Comments
Oldest First  |  Newest First  |  Threaded View
ArielZ999
50%
50%
ArielZ999,
User Rank: Author
11/7/2019 | 4:55:18 AM
Micro-segmentation is scary
From my experience the truth is that simple segmentation and zoning is very hard in todays environments - people are struggling to separate PROD from DEV in anything but non trivial environments. let alone doing smth that is even close to micro.
The biggest mistake that people make, imho, is that they try to move from 0 to 100 and the comlexity vs. the marginal benefit over a much more modest segmentation goals is what kills the project, unfortunatelly for many years in an organization, once they fail it will take them a long time to try again. And frankly for most organizations it seams so "unachievable" that they do not even start doing it. 
My recommendation is to define modest goals such as separate prod from dev and select ~10-20 of you most cirital apps to ring-fence this achievable especially if leveraging the modern micro-segmentation technologies and you will be in a much much better place from your risk perspective. 
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
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-4974
PUBLISHED: 2021-07-28
IBM Jazz Foundation products are vulnerable to server side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks. IBM X-Force ID: 192434.
CVE-2020-5004
PUBLISHED: 2021-07-28
IBM Jazz Foundation products are vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 192957.
CVE-2021-32001
PUBLISHED: 2021-07-28
A Missing Encryption of Sensitive Data vulnerability in k3s, kde2 of SUSE Rancher allows any user with direct access to the datastore, or a copy of a datastore backup to extract the cluster's confidential keying material (cluster certificate authority private keys, secrets encryption configuration p...
CVE-2021-32000
PUBLISHED: 2021-07-28
A UNIX Symbolic Link (Symlink) Following vulnerability in the clone-master-clean-up.sh script of clone-master-clean-up in SUSE Linux Enterprise Server 12 SP3, SUSE Linux Enterprise Server 15 SP1; openSUSE Factory allows local attackers to delete arbitrary files. This issue affects: SUSE Linux Enterp...
CVE-2021-23414
PUBLISHED: 2021-07-28
This affects the package video.js before 7.14.3. The src attribute of track tag allows to bypass HTML escaping and execute arbitrary code.