From 55a97fabd407b75a45a3929f79e8cf80f2487289 Mon Sep 17 00:00:00 2001 From: Bobby DeSimone Date: Sat, 3 Aug 2019 22:29:40 -0700 Subject: [PATCH] typo --- docs/docs/background.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/background.md b/docs/docs/background.md index 38c643ce6..624ce938d 100644 --- a/docs/docs/background.md +++ b/docs/docs/background.md @@ -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... >