This document discusses the principles of zero trust architecture, which aims to eliminate trust from IT systems by verifying all users and devices before granting limited, least-privilege access. It outlines the core elements of zero trust, including verifying the user, verifying their device, and limiting access and privileges. The document also notes that implementing zero trust will require monitoring the environment closely, architecting microperimeters, mapping acceptable data routes, and identifying sensitive data. Organizations may face challenges from technical debt, legacy systems, and other issues requiring new technologies or wrappers.

1. ZERO
TRUST
“Just because you're paranoid doesn't mean they aren't after you.”
Joseph Heller, Catch 22
Boaz@komodosec.com

2. Traditional Security

3. Enterprise
Network
Architecture

4. The Goal Of Zero Trust
ELIMINATE TRUST IN
THE SYSTEM
TRUST GETS
EXPLOITED

5. Zero Trust Enterprise
Architecture

6. Zero Trust Architecture

7. Core Elements Of Zero Trust
Verify The User Verify Their Device Limit Access and
Privileges

8. Becoming Trustless
(without NZT)

9. How to
Become
Trustless
Monitor Monitor the zero trust environment, in
detail, with security analytics
Architect Architect zero trust microperimeters
Map Map the acceptable routes for sensitive
data access and egress
Identify Identify your sensitive data at rest and in
motion

10. Problems Organizations will Face
Technical
Debt
Will require
new
technologies
Legacy
Systems
Will require
wrappers
Peer-to-Peer
Technologies
windows 10
updates

11. What’s next?
More Reading…
• Beyond Corp – Google
• Zero Trust – Microsoft
• Zero Trust – Palo Alto
• Why Zero Trust is Unrealistic