Skip to content

Commit 98dd725

Browse files
committed
better wording
Signed-off-by: Matt Welke <matt.welke@spectrocloud.com>
1 parent ef68906 commit 98dd725

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ See the [samples](https://github.com/validator-labs/validator-plugin-azure/tree/
2626

2727
This rule compares the Azure RBAC permissions associated with a [security principal](https://learn.microsoft.com/en-us/azure/role-based-access-control/overview#security-principal) against an expected permission set.
2828

29-
It checks if an Azure security principal (e.g., users, service principals) has the required Azure RBAC permissions. In Azure RBAC, permissions are applied to principals by a role assignment being created that links a role (which can be a BuiltInRole or a CustomRole) to the principal at a particular scope. API operations at that scope or lower (e.g. operations against a subscription or to a resource group within the subscription) are permitted but operations outside of that scope are not.
29+
It checks if an Azure security principal (e.g., users, service principals) has the required Azure RBAC permissions. In Azure RBAC, permissions are applied to principals by a role assignment being created that links a role (which can be a BuiltInRole or a CustomRole) to the principal at a particular scope. API operations at that scope or lower (e.g. operations against a subscription or against a resource group within the subscription) are permitted but operations outside of that scope are not.
3030

3131
Validation is successful if the principal has the necessary permissions, either from one role assignment or a combination of role assignments.
3232

0 commit comments

Comments
 (0)