Skip to content

Commit

Permalink
Update website/content/blog/zero-trust-new-paper-announcement.md
Browse files Browse the repository at this point in the history
Co-authored-by: Eddie Knight <[email protected]>
Signed-off-by: Hubert Siwik <[email protected]>
  • Loading branch information
huberts90 and eddie-knight authored Nov 8, 2024
1 parent c8a4e49 commit d5790c1
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions website/content/blog/zero-trust-new-paper-announcement.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,8 @@ until the next release. It roughly presumed that access policy wouldn't be viola
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 shifted into something I'd call "Limited Trust." For some, the CNCF paper introduces, and for
others reminds, of a notion of total lack of confidence, regardless of the request's source. It enforces
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. This is the key takeaway from the document.
Expand Down

0 comments on commit d5790c1

Please sign in to comment.