prehistoric-systems/privacyguides.org
1
0
Fork 0
mirror of https://github.com/privacyguides/privacyguides.org.git synced 2026-03-11 08:54:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

add graph

Browse source
This commit is contained in:
fria 2025-10-23 07:48:08 -05:00 committed by GitHub
parent 37ce012e28
commit bee0b6d363
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 17 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
blog/posts/zero-trust.md
View file

@ -20,6 +20,21 @@ preview:
You may have heard of "Zero Trust", usually in relation to corporate networks. It's used a lot as a buzzword to sell cloud products to companies, but the overall concept is sound. Even though it seems complicated, I think we can learn from it for our personal home networks.<!-- more -->
## Overview
## Previous Method
Zero Trust
A traditional approach to security focuses heavily on protecting network access. You define a "secure" network that you control, usually with a [firewall](https://www.cisco.com/site/us/en/learn/topics/security/what-is-a-firewall.html#tabs-9da71fbd27-item-1288c79d71-tab) and/or a [NAT](https://www.cisco.com/site/us/en/learn/topics/networking/what-is-network-address-translation-nat.html#tabs-9da71fbd27-item-1288c79d71-tab).
Anyone inside the secure network is considered trusted and has access to things such as network drives belonging to the organization, and other data.
Anyone outside the network is considered "untrusted" and are not given access to sensitive data.
``` mermaid
graph LR
A[Untrusted Traffic] -.-> B{Network Boundary};
B --> C[Network Drive];
C --> B;
B --> D[User];
D --> B;
B --> E[Printer];
E --> B;
```