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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
'Zero Trust': The Way Forward in Cybersecurity
Newest First  |  Oldest First  |  Threaded View
Suberman99
50%
50%
Suberman99,
 User Rank: Apprentice
1/25/2017 | 1:48:20 PM
Re: Nothing new except the name
Cool sounding maybe but, not many companies adhere to anything but perimeter security, including fortune 1000.

How many IT staffs/managers adhere to LAN segmentation or data center east/west, north/south security.  I'm not just talking about allowing a few ports like 443, 80,8080,25,53 etc.  Bad stuff rides on these ports as well because threat actors know they are most likely to be open.  Zero trust is about knowing the precise application regardless of port or protocol as well as connecting a username to that session.
ClarenceR927
50%
50%
ClarenceR927,
 User Rank: Strategist
1/25/2017 | 10:37:14 AM
Re: Nothing new except the name
Our management has fallen in love with "Cyber kill chain" as if it has value.  Same deal, put a cool sounding name on the same stuff security has been recommending for a decade and all of a sudden theypay attention.
Joe Stanganelli
100%
0%
Joe Stanganelli,
 User Rank: Ninja
1/14/2017 | 2:44:11 PM
Nothing new except the name
This strategy is what top cybersecurity experts have recommended for years.  Few listened.

The only difference now is that, as of sometime in the last year+, somebody came up with a catchy name ("Zero Trust") for it.

I guess buzzterms have their place.
Shantaram
0%
100%
Shantaram,
 User Rank: Ninja
1/13/2017 | 6:21:53 AM
Re: 192.168.0.1
Cool! i like it!
netwatcher
50%
50%
netwatcher,
 User Rank: Apprentice
1/12/2017 | 3:25:21 PM
Re: Isn't this what we were supposed to be doing all along?
some reasons why...
  • Executive is not aware of the risks – "We have a firewall and anti-virus so I think we are covered..."headinsand
  • Executive has bad information – "Hackers only attack the big companies, what would they want from us?"
  • Executive is a risk taker – "I'll take the risk, the probability for us getting attacked is low."
  • Executive is cheap – "No ROI means no priority."
  • Executive doesn't believe investment in security is worth it – "The loss involved will be so small compared to our revenues. It's easier to take a chance and write off any losses should they occur."
  • Executive is overwhelmed by the size of the necessary investment required to add additional security measures – "We can't afford Fire Eye, IBM, HP, Palo Alto etc.. those tools are only affordable to the fortune 1000"
  • Executive believes they are covered when they are not – "Our POS (or EMR) vendor is responsible for our security not us..."
  • Executive doesn't believe any investment will have much of an impact – "Big companies have all the tools and they are still getting hacked."
ClarenceR927
100%
0%
ClarenceR927,
 User Rank: Strategist
1/12/2017 | 9:10:58 AM
Isn't this what we were supposed to be doing all along?
Seriously, how far removed from the real world is IT/CISO management that this concept needs to be explained to them?  This exact structure has been undersood and recommeneded for at least 25 years.  The more important article would be one that examines the excuses, roadblocks and technical challenges that have prevented people from actually making it happen.
DamnDesert
50%
50%
DamnDesert,
 User Rank: Apprentice
1/10/2017 | 10:47:06 PM
If only it were that simple
If it were just up to cybersecurity to get it done it would be so simple. I've spent 5 years trying to get the company I'm at to get such controls in place to government requirements SP-800-53 for a contract we have. I the end it takes executive buy in, available Capex/Opex budget, priority from other IT departments, and patience for needed downtime for many of the changes that need to take place. No small task, needed yes, getting people to understand it's a high priority is a whole other challenge.


COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
9 Tips to Prepare for the Future of Cloud & Network Security
Kelly Sheridan, Staff Editor, Dark Reading,  9/28/2020
Attacker Dwell Time: Ransomware's Most Important Metric
Ricardo Villadiego, Founder and CEO of Lumu,  9/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15488
PUBLISHED: 2020-09-30
Re:Desk 2.3 allows insecure file upload.
CVE-2020-15849
PUBLISHED: 2020-09-30
Re:Desk 2.3 has a blind authenticated SQL injection vulnerability in the SettingsController class, in the actionEmailTemplates() method. A malicious actor with access to an administrative account could abuse this vulnerability to recover sensitive data from the application's database, allowing for a...
CVE-2020-14375
PUBLISHED: 2020-09-30
A flaw was found in dpdk in versions before 18.11.10 and before 19.11.5. Virtio ring descriptors, and the data they describe are in a region of memory accessible by from both the virtual machine and the host. An attacker in a VM can change the contents of the memory after vhost_crypto has validated ...
CVE-2020-14376
PUBLISHED: 2020-09-30
A flaw was found in dpdk in versions before 18.11.10 and before 19.11.5. A lack of bounds checking when copying iv_data from the VM guest memory into host memory can lead to a large buffer overflow. The highest threat from this vulnerability is to data confidentiality and integrity as well as system...
CVE-2020-14377
PUBLISHED: 2020-09-30
A flaw was found in dpdk in versions before 18.11.10 and before 19.11.5. A complete lack of validation of attacker-controlled parameters can lead to a buffer over read. The results of the over read are then written back to the guest virtual machine memory. This vulnerability can be used by an attack...