-
Notifications
You must be signed in to change notification settings - Fork 533
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add a blog announcement for an updated Zero Trust paper
- Loading branch information
hubert.siwik
committed
Nov 7, 2024
1 parent
82c6861
commit b98b556
Showing
1 changed file
with
19 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
--- | ||
title: "An updated CNCF Zero Trust White Paper is looming" | ||
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 Zero Trust paper by the CNCF security team, 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 | ||
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. | ||
|
||
To learn how to actually implement this, immerse yourself in the reading. |