From 8717e97f4ac17ae9d85fabf7f90db915d0817bc4 Mon Sep 17 00:00:00 2001 From: Istio Automation Date: Mon, 30 Oct 2023 07:11:32 -0700 Subject: [PATCH] fix #14069: updated incorrect hyperlink to PEP glossary (#14075) Co-authored-by: Roofer92 <50134488+Roofer92@users.noreply.github.com> --- content/en/docs/concepts/security/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/security/index.md b/content/en/docs/concepts/security/index.md index 9c2d8ef143..48fe6af3fc 100644 --- a/content/en/docs/concepts/security/index.md +++ b/content/en/docs/concepts/security/index.md @@ -61,7 +61,7 @@ Security in Istio involves multiple components: - [authorization policies](/docs/concepts/security/#authorization-policies) - [secure naming information](/docs/concepts/security/#secure-naming) -- Sidecar and perimeter proxies work as [Policy Enforcement Points](https://www.jerichosystems.com/technology/glossaryterms/policy_enforcement_point.html) +- Sidecar and perimeter proxies work as [Policy Enforcement Points](https://csrc.nist.gov/glossary/term/policy_enforcement_point) (PEPs) to secure communication between clients and servers. - A set of Envoy proxy extensions to manage telemetry and auditing