From c460b1746c01952359ecdf13bd57d29548aae72c Mon Sep 17 00:00:00 2001 From: Ian Fowler Date: Tue, 12 Nov 2024 13:16:18 +0000 Subject: [PATCH] Revision of hardening guide Correction Document how to secure and harden AAP https://issues.redhat.com/browse/AAP-32887 --- downstream/modules/aap-hardening/con-rbac.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/downstream/modules/aap-hardening/con-rbac.adoc b/downstream/modules/aap-hardening/con-rbac.adoc index 01905168c..4a5aefe35 100644 --- a/downstream/modules/aap-hardening/con-rbac.adoc +++ b/downstream/modules/aap-hardening/con-rbac.adoc @@ -9,7 +9,7 @@ As an administrator, you can use the _Role-Based Access Controls_ (RBAC) built into the {GatewayStart} to delegate access to server inventories, organizations, and more. Administrators can also centralize the management of various credentials, enabling end users to use a needed secret without ever exposing that secret to the end user. -RBAC controls allow {PlatformNameShorrt} to help you increase security and streamline management. +RBAC controls allow {PlatformNameShort} to help you increase security and streamline management. RBAC is the practice of granting roles to users or teams. RBAC is easiest to think of in terms of Roles which define precisely who or what can see, change, or delete an “object” for which a specific capability is being set.