Merge pull request #208728 from miwithro/patch-163

prmerger-automator[bot] · web-flow · commit 5653db82f555 · 2022-08-22T18:41:59.000Z
Update operator-best-practices-cluster-security.md
diff --git a/articles/aks/operator-best-practices-cluster-security.md b/articles/aks/operator-best-practices-cluster-security.md
@@ -95,7 +95,7 @@ For even more granular control of container actions, you can also use built-in L
 Built-in Linux security features are only available on Linux nodes and pods.
 
 > [!NOTE]
-> Currently, Kubernetes environments aren't completely safe for hostile multi-tenant usage. Additional security features, like *AppArmor*, *seccomp*,*Pod Security Policies*, or Kubernetes RBAC for nodes, efficiently block exploits. 
+> Currently, Kubernetes environments aren't completely safe for hostile multi-tenant usage. Additional security features, like *Microsoft Defender for Containers* *AppArmor*, *seccomp*,*Pod Security Admission*, or Kubernetes RBAC for nodes, efficiently block exploits. 
 >
 >For true security when running hostile multi-tenant workloads, only trust a hypervisor. The security domain for Kubernetes becomes the entire cluster, not an individual node. 
 >

Original file line number	Diff line number	Diff line change
`@@ -95,7 +95,7 @@ For even more granular control of container actions, you can also use built-in L`
`95`	`95`	`Built-in Linux security features are only available on Linux nodes and pods.`
`96`	`96`
`97`	`97`	`> [!NOTE]`
`98`		`-> Currently, Kubernetes environments aren't completely safe for hostile multi-tenant usage. Additional security features, like AppArmor, seccomp,Pod Security Policies, or Kubernetes RBAC for nodes, efficiently block exploits.`
	`98`	`+> Currently, Kubernetes environments aren't completely safe for hostile multi-tenant usage. Additional security features, like Microsoft Defender for Containers AppArmor, seccomp,Pod Security Admission, or Kubernetes RBAC for nodes, efficiently block exploits.`
`99`	`99`	`>`
`100`	`100`	`>For true security when running hostile multi-tenant workloads, only trust a hypervisor. The security domain for Kubernetes becomes the entire cluster, not an individual node.`
`101`	`101`	`>`