Skip to content
Back to skills

Cis Aks V180 5.1.2

ASecurity

Minimize user access to Azure Container Registry (ACR) (Manual)

  • 3,518 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 3, 2026
securitygokubernetesazuresecurity

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill cis-aks-v180-5.1.2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cis Aks V180 5.1.2?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cis Aks V180 5.1.2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-cis-aks-v180-5-1-2/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-aks-v180-5-1-2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cis-aks-v180-5.1.2
description: "Minimize user access to Azure Container Registry (ACR) (Manual)"
category: cis-aks
version: "1.8.0"
author: cyberstrike-official
tags: [cis, aks, kubernetes, azure, acr, iam, access-control, least-privilege]
cis_id: "5.1.2"
cis_benchmark: "CIS Azure Kubernetes Service (AKS) Benchmark v1.8.0"
tech_stack: [kubernetes, azure, aks]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---

# 5.1.2 Minimize user access to Azure Container Registry (ACR) (Manual)

## Profile Applicability

- Level 1

## Description

Restrict user access to Azure Container Registry (ACR), limiting interaction with build images to only authorized personnel and service accounts.

## Rationale

Weak access control to Azure Container Registry (ACR) may allow malicious users to replace built images with vulnerable containers.

## Impact

Care should be taken not to remove access to Azure ACR for accounts that require this for their operation.

## Audit

Review Azure Container Registry access permissions to ensure only authorized users and service accounts have access.

## Remediation

Azure Container Registry: If you use Azure Container Registry (ACR) as your container image store, you need to grant permissions to the service principal for your AKS cluster to read and pull images. Currently, the recommended configuration is to use the az aks create or az aks update command to integrate with a registry and assign the appropriate role for the service principal. For detailed steps, see Authenticate with Azure Container Registry from Azure Kubernetes Service.

To avoid needing an Owner or Azure account administrator role, you can configure a service principal manually or use an existing service principal to authenticate ACR from AKS. For more information, see ACR authentication with service principals or Authenticate from Kubernetes with a pull secret.

## References

1. https://docs.microsoft.com/security/benchmark/azure/security-controls-v2-privileged-access#pa-7-follow-just-enough-administration-least-privilege-principle

## CIS Controls

| Controls Version | Control                                               | IG 1 | IG 2 | IG 3 |
| ---------------- | ----------------------------------------------------- | ---- | ---- | ---- |
| v8               | 3.3 Configure Data Access Control Lists               | x    | x    | x    |
| v7               | 14.6 Protect Information through Access Control Lists | x    | x    | x    |

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in security →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.