Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a blog announcement for an updated Zero Trust paper #1400

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions website/content/blog/zero-trust-new-paper-announcement.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "A reader's perspective on the latest Zero Trust White Paper"
date: 2024-11-07 12:00:00 +0000
author: Hubert Siwik
---

What comes to mind when you think of Zero Trust security? Personally, I had a distorted understanding of this concept
until now, seeing it as an approach that blindly assumed that security, once granted, was eternal or... at least valid
until the next release. It roughly presumed that access policy wouldn't be violated, the network perimeter wouldn't be
breached, and a vulnerable pod wouldn't be exploited. Up until now…

After reading the TAG Security Zero Trust white paper, my understanding of this philosophy has radically changed,
and my previous view has shifted into something closer to _Limited_ Trust. The emphasis I took away
was on the notion of total lack of confidence, regardless of the request's source. It enforces
a "trust nothing" policy, relying on metrics that are constantly evaluated and adjusted according to the current context.
Stolen credentials of a benign user or an exploited Kubernetes instance will no longer be a foothold for significant damage,
as non-standard activity is expected to be quickly identified and neutralised.

To learn how to actually implement this, immerse yourself in the reading.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: Add link after the publication is released.

Loading