TMA-AZURE-DB-2.5
Ensure that 'System Assigned Managed Identity' is set to 'On'
Description
System Assigned Managed Identities provide the Azure Cache for Redis instance with a unique account like a service principle but automatically assigned and managed by Azure. These identities are unique to the resource instance they are created for, and removed when the resource is deleted. The System Assigned Managed Identity is authenticated with Entra ID, and allows for privileges required for the instance of Azure Cache for Redis to be granted or restricted using Azure Role Based Access Control (RBAC). Additionally, the managed identity provides a means for the Azure Cache for Redis instance to authenticate without storing credentials in code.
How it is checked
Audit method: Manual review
This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.
Audit From Azure Portal 1. Search for and open the Azure Cache for Redis service 2. For each instance, repeat the remaining steps 3. Click on the name of the instance 4. In the blade menu on the left, under Settings, click on Identity 5. Under the System assigned tab, ensure that Status is set to On. If Yes is selected and Object (principal) ID is populated, the configuration for that instance is compliant.
How it is fixed
Fix method: Guidance or infrastructure patch
Remediate From Azure Portal 1. Search for and open the Azure Cache for Redis service 2. For each instance, repeat the remaining steps 3. Click on the name of the instance 4. In the blade menu on the left, under Settings, click on Identity 5. Under the System assigned tab, toggle the status to On 6. Click the Save button 7. In the pop-up dialog titled Enable system assigned managed identity that appears after clicking save, click the Yes button.
Properties
- Operating systems
- Any
- Tags
- azureclouddatabase
- Reference
- CIS Microsoft Azure Database Services Benchmark v2.0.0 - 2.5 Ensure that 'System Assigned Managed Identity' is set to 'On'