-
Notifications
You must be signed in to change notification settings - Fork 521
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
huberts90
wants to merge
5
commits into
cncf:main
Choose a base branch
from
huberts90:hsiwik/zero-trust-announcement
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
d02e1cd
Add a blog announcement for an updated Zero Trust paper
d81625f
Update website/content/blog/zero-trust-new-paper-announcement.md
huberts90 cc16094
Update website/content/blog/zero-trust-new-paper-announcement.md
huberts90 f0fbf4c
Update website/content/blog/zero-trust-new-paper-announcement.md
huberts90 82c0dd4
Update website/content/blog/zero-trust-new-paper-announcement.md
huberts90 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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: "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. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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.