summaryrefslogtreecommitdiffhomepage
path: root/content
diff options
context:
space:
mode:
authorNicolas Lacasse <nlacasse@google.com>2020-03-13 09:47:57 -0700
committerNicolas Lacasse <nicolas.lacasse@gmail.com>2020-03-16 09:26:39 -0700
commitacad1aa8cf96950637e9cb58baae3207bbb2f67f (patch)
tree404b010d6ce244aa1fdfe57453ecdf613c053455 /content
parente024f8fa560c1420039f8e29b601f30b1bb233e5 (diff)
Grammar fix
"trusts each other component" is not grammatical.
Diffstat (limited to 'content')
-rw-r--r--content/blog/1_security_basics/index.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/blog/1_security_basics/index.md b/content/blog/1_security_basics/index.md
index 5d6e82be0..3503ef7a2 100644
--- a/content/blog/1_security_basics/index.md
+++ b/content/blog/1_security_basics/index.md
@@ -67,7 +67,7 @@ In this post, we are only discussing security-related features of gVisor, and yo
## Defense-in-Depth
-For gVisor, Defense-in-Depth means each component of the software stack trusts each other component as little as possible.
+For gVisor, Defense-in-Depth means each component of the software stack trusts the other components as little as possible.
It may seem strange that we would want our own software components to distrust each other. But by limiting the trust between small, discrete components, each component is forced to defend itself against potentially malicious input. And when you stack these components on top of each other, you can ensure that multiple security barriers must be overcome by an attacker.