From 30eb2cc0cfabc19db9640559eceaa6d39f52dd60 Mon Sep 17 00:00:00 2001 From: Paszymaja <36695377+Paszymaja@users.noreply.github.com> Date: Wed, 27 Jul 2022 14:12:15 +0200 Subject: [PATCH] Update content/en/docs/concepts/security/rbac-good-practices.md Co-authored-by: divya-mohan0209 --- content/en/docs/concepts/security/rbac-good-practices.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/security/rbac-good-practices.md b/content/en/docs/concepts/security/rbac-good-practices.md index 7699a0da45..fe858bba72 100644 --- a/content/en/docs/concepts/security/rbac-good-practices.md +++ b/content/en/docs/concepts/security/rbac-good-practices.md @@ -135,7 +135,8 @@ granting rights to this resource. ### Escalate verb -Generally, the RBAC system prevents users from creating clusterroles with more rights than the user possesses. The exception to this is the `escalate` verb. As noted in the [RBAC documentation](/docs/reference/access-authn-authz/rbac/#restrictions-on-role-creation-or-update), +Generally, the RBAC system prevents users from creating clusterroles with more rights than the user possesses. +The exception to this is the `escalate` verb. As noted in the [RBAC documentation](/docs/reference/access-authn-authz/rbac/#restrictions-on-role-creation-or-update), users with this right can effectively escalate their privileges. ### Bind verb