3pp-mirror/pomerium
1
0
Fork 0
mirror of https://github.com/pomerium/pomerium.git synced 2025-07-24 20:18:13 +02:00
Code Issues Projects Releases Packages Wiki Activity

typo

Browse source
This commit is contained in:
Bobby DeSimone 2019-08-03 22:29:40 -07:00
parent 0a530fbea2
commit 55a97fabd4
No known key found for this signature in database
GPG key ID: AEE4CF12FE86D07E
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/docs/background.md
View file

@ -10,7 +10,7 @@ meta:
## History
For years, security was synonymous with network security. Firewalls, network segmentation, and VPNs reigned the day. Broadly speaking, that network focused security posture is what people mean today when they talk about the perimeter security model. So-called "impenetrable fortress" security worked well for a period of time when you could reasonably expect your network perimeter to correspond to an actual physical perimeters, users, devices, and servers. But as teams, applications, workloads, and users became more ephemeral, containered, and distributed, the shortcomings of perimeter based security have become more apparent in terms of both operational costs and security breaches.
For years, security was synonymous with network security. Firewalls, network segmentation, and VPNs reigned the day. Broadly speaking, that network focused security posture is what people mean today when they talk about the perimeter security model. So-called "impenetrable fortress" security worked well for a period of time when you could reasonably expect your network perimeter to correspond to an actual physical perimeters, users, devices, and servers. But as teams, applications, workloads, and users became more ephemeral and distributed, the shortcomings of perimeter based security have become more apparent in terms of both operational costs and security breaches.
> Most networks [have] big castle walls, hard crunchy outer shell, and soft gooey centers...
>