Zero Trust: verify explicitly, use least privilege, assume breach
Slide deck explaining Zero Trust security model: verify explicitly using signals, use least privilege access, and assume breach for containment and detection.
Zero Trust: verify explicitly, use least privilege, assume breach
Introduction to Zero Trust security model: verify explicitly, use least privilege, and assume breach for better security.
Zero Trust: verify explicitly, use least privilege, assume breach
Introduction to Zero Trust security model: verify explicitly, use least privilege, and assume breach for better security.
What Zero Trust means
Trust is earned per request, not assumed by location. Security model (principles), not a single product. No automatic trust for users/devices/apps. 'Internal network' does not equal guaranteed safe. Verify each access request using signals.
Castle-and-moat vs Zero Trust
The boundary isn't the main proof of trust anymore. Perimeter model: inside trusted by default. Modern reality: cloud apps plus remote work. Compromise can happen anywhere. Zero Trust: decide using evidence, not assumptions.
Verify explicitly
Authenticate and authorize using signals—not just location. Authentication equals prove identity (sign in). Authorization equals decide allowed access. Use signals (context evidence). Network location is only one signal.
Signals you can use
Use multiple signals to decide how much access to grant. Identity (who is requesting). Sign-in risk and anomalies. Device compliance/health. Location and network context. Resource sensitivity (what's being accessed).
Scenario: inside the network
Being 'internal' doesn't skip verification. Office network does not equal automatic trust. Verify identity plus device plus risk. Consider resource sensitivity. Apply checks to internal and external requests.
Least privilege access
Give the minimum access needed, scoped and time-limited. Minimum permissions (just enough). Smallest scope (only needed resources). Shortest duration (just-in-time). Limits damage from mistakes or compromise.
Scenario: contractor for 2 days
Make access intentional: specific, limited, and time-bound. Grant access to one specific resource. Limit permissions to the task. Set a short time window (2 days). Avoid broad 'just in case' access.
Assume breach
Design for containment, visibility, and fast response. Minimize blast radius (limit damage). Segment access (block easy lateral movement). Detect and respond (monitor and investigate). Focus on resilience, not a 'perfect wall'.
Scenario: compromised account
Prevention helps, but containment and detection limit real damage. Strong sign-in does not equal full protection. Use segmentation to limit reach. Monitor for suspicious movement. Improve alerting and investigation.
Recap + common pitfalls
Perimeter tools can exist, but trust decisions come from signals and principles. VPN (Virtual Private Network) is not automatic trust. Zero Trust is a model, not a single product. Don't apply it only to 'external' users. Don't ignore assume breach (contain plus detect).