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
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
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
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.
netwatcher
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
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
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.


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 Promise and Reality of Cloud Security
Cloud security has been part of the cybersecurity conversation for years but has been on the sidelines for most enterprises. The shift to remote work during the COVID-19 pandemic and digital transformation projects have moved cloud infrastructure front-and-center as enterprises address the associated security risks. This report - a compilation of cutting-edge Black Hat research, in-depth Omdia analysis, and comprehensive Dark Reading reporting - explores how cloud security is rapidly evolving.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-0519
PUBLISHED: 2023-01-26
Cross-site Scripting (XSS) - Stored in GitHub repository modoboa/modoboa prior to 2.0.4.
CVE-2023-0493
PUBLISHED: 2023-01-26
Improper Neutralization of Equivalent Special Elements in GitHub repository btcpayserver/btcpayserver prior to 1.7.5.
CVE-2022-46967
PUBLISHED: 2023-01-26
An access control issue in Revenue Collection System v1.0 allows unauthenticated attackers to view the contents of /admin/DBbackup/ directory.
CVE-2022-46966
PUBLISHED: 2023-01-26
Revenue Collection System v1.0 was discovered to contain a SQL injection vulnerability at step1.php.
CVE-2023-0455
PUBLISHED: 2023-01-26
Unrestricted Upload of File with Dangerous Type in GitHub repository unilogies/bumsys prior to v1.0.3-beta.