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.

Never Trust, Always Verify: Demystifying Zero Trust to Secure Your Networks
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
7/15/2021 | 5:17:30 PM
Zero-Trust also applies to ITAD
When it comes to sensitive data, trust is a luxury today's organizations can't afford.

That's exactly why the Zero-Trust security model has gained acceptance as the go-to framework for network security. But Zero-Trust isn't just effective in combating modern cyber threats — it's also the cornerstone of an effective IT asset disposition strategy.

Whereas Zero-Trust network access is about permission (Do you have permission to be on this network?) Zero-Trust computer recycling is about possession (Do you have possession of this asset?).

Assets get lost or stolen in transit, manifests are filled with errors, and equipment is sold off through shady remarketing channels. Worst of all, even though these open your company up to significant financial and legal liability, it's you, not your vendor, that's left holding the bag when things go south.

Ransomware is all over the news right now. But it's not just gaps in your firewall that these hackers are looking for; it's your old computer equipment. A single unsecured asset can create a plethora of problems because these backdoors make it easy to install ransomware.
Traditional trust-based ITAD create a nightmare for data security and a dilemma for IT asset management. Traditional trust-based ITAD is ineffective.

As John Kindervag eloquently states, the point of Zero Trust is not to make networks more trusted; it's to eliminate the concept of trust.

The point of Zero-Trust ITAD is not to make disposal vendors more trusted; it's to eliminate the concept of trust from ITAD.

To learn more, please visit https://retire-it.com/zero-trust-itad/

Kyle Marks

(614) 522-2301 x 14

[email protected]


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
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
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
Current Issue
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2022-01-26
In Bromite through 78.0.3904.130, there are adblock rules in the release APK; therefore, probing which resources are blocked and which aren't can identify the application version and defeat the User-Agent protection mechanism.
PUBLISHED: 2022-01-26
Exposure of Sensitive Information to an Unauthorized Actor in NPM hiep-simple-get prior to 4.0.1.
PUBLISHED: 2022-01-26
The firmware on Moxa TN-5900 devices through 3.1 has a weak algorithm that allows an attacker to defeat an inspection mechanism for integrity protection.
PUBLISHED: 2022-01-26
The firmware on Moxa TN-5900 devices through 3.1 allows command injection that could lead to device damage.
PUBLISHED: 2022-01-26
In Varnish Cache before 6.6.2 and 7.x before 7.0.2, Varnish Cache 6.0 LTS before 6.0.10, and and Varnish Enterprise (Cache Plus) 4.1.x before 4.1.11r6 and 6.0.x before 6.0.9r4, request smuggling can occur for HTTP/1 connections.