用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-aks-v170-3-1-3命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | cis-aks-v170-3.1.3 |
| description | Ensure that the azure.json file has permissions set to 644 or more restrictive (Automated) |
| category | cis-aks |
| version | 1.7.0 |
| author | cyberstrike-official |
| tags | ["cis","aks","kubernetes","azure","worker-node","file-permissions","azure-json"] |
| cis_id | 3.1.3 |
| cis_benchmark | CIS Azure Kubernetes Service (AKS) Benchmark v1.7.0 |
| tech_stack | ["kubernetes","azure","aks"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
The azure.json file in an Azure Kubernetes Service (AKS) cluster is a configuration file used by the Kubernetes cloud provider integration for Azure. This file contains essential details that allow the Kubernetes cluster to interact with Azure resources effectively. It's part of the Azure Cloud Provider configuration, enabling Kubernetes components to communicate with Azure services for features like load balancers, storage, and networking.
Ensure the file has permissions of 644 or more restrictive.
The azure.json file in AKS structure typically includes:
None.
Method 1
First, SSH to the relevant worker node.
To check to see if the Kubelet Service is running:
sudo systemctl status kubelet
The output should return Active: active (running) since...
Run the following command on each node to find the appropriate Kubelet config file:
ps -ef | grep kubelet
The output of the above command should return something similar to --config /etc/kubernetes/azure.json which is the location of the Kubelet config file.
Run the following command:
stat -c %a /etc/kubernetes/azure.json
The output of the above command is the Kubelet config file's permissions. Verify that the permissions are or more restrictive.
644Method 2
Create and Run a Privileged Pod.
You will need to run a pod that is privileged enough to access the host's file system. This can be achieved by deploying a pod that uses the hostPath volume to mount the node's file system into the pod.
Here's an example of a simple pod definition that mounts the root of the host to /host within the pod:
apiVersion: v1
kind: Pod
metadata:
name: file-check
spec:
volumes:
- name: host-root
hostPath:
path: /
type: Directory
containers:
- name: nsenter
image: busybox
command: ["sleep", "3600"]
volumeMounts:
- name: host-root
mountPath: /host
securityContext:
privileged: true
Save this to a file (e.g., file-check-pod.yaml) and create the pod:
kubectl apply -f file-check-pod.yaml
Once the pod is running, you can exec into it to check file permissions on the node:
kubectl exec -it file-check -- sh
Now you are in a shell inside the pod, but you can access the node's file system through the /host directory and check the permission level of the file:
ls -l /host/etc/kubernetes/azure.json
Verify that if a file is specified and it exists, the permissions are 644 or more restrictive.
Run the following command (using the config file location identified in the Audit step):
chmod 644 /etc/kubernetes/azure.json
See the Azure AKS documentation for the default value.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 3.3 Configure Data Access Control Lists | X | X | X |
| v7 | 5.2 Maintain Secure Images | X | X |