Skip to content

Commit 731ffcd

Browse files
committed
minor edits
1 parent b9822ea commit 731ffcd

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

firewall.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -470,11 +470,11 @@ The term "zero trust" was coined by the analyst firm Forrester in
470470
2009, and continues to be widely used in the industry today. The
471471
central idea behind zero trust is that, by default, every device and
472472
user should be untrusted. Each user and device then needs to
473-
authenticate itself to a precise set of services. There is no blanket
474-
"trust this device to access anything" policy. Zero trust stands in
475-
contrast to the old "perimeter security" model in which there is the
476-
idea of a trusted region within a perimeter defined by firewalls and
477-
an untrusted region outside the perimeter.
473+
authenticate itself to gain access to a precise set of services. There
474+
is no blanket "trust this device to access anything" policy. Zero
475+
trust stands in contrast to the old "perimeter security" model in
476+
which there is the idea of a trusted region within a perimeter
477+
protected by firewalls and an untrusted region outside the perimeter.
478478

479479
Zero trust is sufficiently well accepted that NIST has written a
480480
specification (see Further Reading below) which provides this helpful

0 commit comments

Comments
 (0)