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 zero trust info

Browse source
This commit is contained in:
fria 2025-10-23 08:39:57 -05:00 committed by GitHub
parent 80bd72d38d
commit 36ed4a17fc
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 18 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -93,4 +93,21 @@ The reality today is, most of what we use isn't located on a network we control
This is where [Zero Trust](https://learn.microsoft.com/en-us/security/zero-trust/zero-trust-overview) comes in.
The motto here is "**never trust, always verify**". This means that
### Verify
The motto here is "**never trust, always verify**". This means that you should never assume any device accessing any resource or performing any action is trusted. You should verify explicitly every time and using as many data points as you can.
### Principle of Least Privilege
The [Principle of Least Privelege](https://www.cloudflare.com/learning/access-management/principle-of-least-privilege/) states that a user should only have access to the bare minimum they need in order to do what they need to do, and no more.
In a corporate network, a sales associate doesn't need full control over the network. In your home network, grandpa probably doesn't need access to your password manager or your user account on your PC.
### Assume Breach
Always assume the attackers are listening: use encryption whenever you can. Treat your internal network traffic like external traffic.
You never know what could be lurking. A single infected printer for example could be scanning your network for unencrypted traffic or holes in your device's firewall.
## Applying These Lessons