Zero Trust Architecture - Now We Must, But What It Means?
summary
Governments mandate zero trust via EO 14028 and NIST SP 800-207 and expect private sector compliance; enforcement timelines push suppliers to produce SBOMs and cryptographic bill of materials. Reality check: commercial OSINT exposes military and corporate devices, QR/barcode fraud migrates globally over a decade, and $30 SDRs enable attacks once costly only to nation states. Strategy centers on identity-first protections, continuous validation, open source for critical apps, and the mantra never trust always verify while preserving privacy and anonymity.
AI-written summary · about
chapters (9)
- 0:00Introduction to zero trust
- 1:14Open source intelligence
- 4:46Cyberwar and information space
- 7:37The evolving threat landscape
- 10:31Rethinking security models
- 14:07Supply chain and verification
- 16:58Implementing zero trust
- 19:31Government mandates and policy
- 22:58Conclusion and mindset
related talks
50mZero Trust Privacy: Rethinking a Data Strategy
42mImplementing Zero Trust in Government Settings: Strategies, Challenges, and Best Pra...
40mZero Trust and Privacy: Moving Security Closer to the Target
31mEmbracing Zero Trust When You Aren't the World's Largest Internet Company
34mZero Trust Best Practices in Government and Federal Industries
31mAttacking Zero Trust Designs in 2021
47mThwarting the Adversary: Bending the Zero Trust Curve to Defense
02h 48mZero Trust: the new normal!