istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

though -> through (#4645) (#4646) 

(cherry picked from commit 9e03700cb0)
This commit is contained in:
mergify[bot] 2019-07-09 10:29:17 -04:00 committed by Frank Budinsky
parent 1d6678e1fe
commit 7e7a3e671e
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/blog/2019/egress-traffic-control-in-istio-part-1/index.md
View File

@ -17,7 +17,7 @@ Future installments will describe the implementation of the secure control of eg
compare it with other solutions.
The most important security aspect for a service mesh is probably ingress traffic. You definitely must prevent attackers
from penetrating the cluster though ingress APIs. Having said that, securing
from penetrating the cluster through ingress APIs. Having said that, securing
the traffic leaving the mesh is also very important. Once your cluster is compromised, and you must be
prepared for that scenario, you want to reduce the damage as much as possible and prevent the attackers from using the
cluster for further attacks on external services and legacy systems outside of the cluster. To achieve that goal,