Azure Policy Regulatory Compliance controls for Azure Kubernetes Service (AKS)

Regulatory Compliance in Azure Policy provides initiative definitions (built-ins) created and managed by Microsoft, for the compliance domains and security controls related to different compliance standards. This page lists the Azure Kubernetes Service (AKS) compliance domains and security controls.

You can assign the built-ins for a security control individually to help make your Azure resources compliant with the specific standard.

The title of each built-in policy definition links to the policy definition in the Azure portal. Use the link in the Policy Version column to view the source on the Azure Policy GitHub repo.

Important

Each control is associated with one or more Azure Policy definitions. These policies might help you assess compliance with the control. However, there often isn't a one-to-one or complete match between a control and one or more policies. As such, Compliant in Azure Policy refers only to the policies themselves. This doesn't ensure that you're fully compliant with all requirements of a control. In addition, the compliance standard includes controls that aren't addressed by any Azure Policy definitions at this time. Therefore, compliance in Azure Policy is only a partial view of your overall compliance status. The associations between controls and Azure Policy Regulatory Compliance definitions for these compliance standards can change over time.

Azure Security Benchmark

The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Azure Security Benchmark, see the Azure Security Benchmark mapping files.

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Azure Security Benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Network Security NS-2 Secure cloud services with network controls Authorized IP ranges should be defined on Kubernetes Services 2.0.1
Privileged Access PA-7 Follow just enough administration (least privilege) principle Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Data Protection DP-3 Encrypt sensitive data in transit Kubernetes clusters should be accessible only over HTTPS 7.0.0
Logging and Threat Detection LT-1 Enable threat detection capabilities Azure Kubernetes Service clusters should have Defender profile enabled 1.0.3
Logging and Threat Detection LT-2 Enable threat detection for identity and access management Azure Kubernetes Service clusters should have Defender profile enabled 1.0.3
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations [Preview]: Kubernetes clusters should gate deployment of vulnerable images 2.0.0-preview
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters 1.0.2
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits 8.0.0
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes cluster containers should not share host process ID or host IPC namespace 4.0.1
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes cluster containers should only use allowed AppArmor profiles 5.0.0
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes cluster containers should only use allowed capabilities 5.0.1
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes cluster containers should only use allowed images 8.0.0
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes cluster containers should run with a read only root file system 5.0.0
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes cluster pod hostPath volumes should only use allowed host paths 5.0.1
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes cluster pods and containers should only run with approved user and group IDs 5.0.2
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes cluster pods should only use approved host network and port range 5.0.0
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes cluster services should listen only on allowed ports 7.0.0
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes cluster should not allow privileged containers 8.0.0
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes clusters should disable automounting API credentials 3.0.1
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes clusters should not allow container privilege escalation 6.0.1
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes clusters should not grant CAP_SYS_ADMIN security capabilities 4.0.0
Posture and Vulnerability Management PV-2 Audit and enforce secure configurations Kubernetes clusters should not use the default namespace 3.0.1
Posture and Vulnerability Management PV-6 Rapidly and automatically remediate vulnerabilities Running container images should have vulnerability findings resolved 1.0.1
DevOps Security DS-6 Enforce security of workload throughout DevOps lifecycle Running container images should have vulnerability findings resolved 1.0.1

Azure Security Benchmark v1

The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Azure Security Benchmark, see the Azure Security Benchmark mapping files.

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Azure Security Benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Network Security 1.1 Protect resources using Network Security Groups or Azure Firewall on your Virtual Network Authorized IP ranges should be defined on Kubernetes Services 2.0.1
Data Protection 4.6 Use Azure RBAC to control access to resources Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Vulnerability Management 5.3 Deploy automated third-party software patch management solution Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version 1.0.2

CIS Microsoft Azure Foundations Benchmark 1.1.0

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CIS Microsoft Azure Foundations Benchmark 1.1.0. For more information about this compliance standard, see CIS Microsoft Azure Foundations Benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Other Security Considerations CIS Microsoft Azure Foundations Benchmark recommendation 8.5 Enable role-based access control (RBAC) within Azure Kubernetes Services Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2

CIS Microsoft Azure Foundations Benchmark 1.3.0

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CIS Microsoft Azure Foundations Benchmark 1.3.0. For more information about this compliance standard, see CIS Microsoft Azure Foundations Benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Other Security Considerations CIS Microsoft Azure Foundations Benchmark recommendation 8.5 Enable role-based access control (RBAC) within Azure Kubernetes Services Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2

CMMC Level 3

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CMMC Level 3. For more information about this compliance standard, see Cybersecurity Maturity Model Certification (CMMC).

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC.1.001 Limit information system access to authorized users, processes acting on behalf of authorized users, and devices (including other information systems). Kubernetes cluster pods should only use approved host network and port range 5.0.0
Access Control AC.1.001 Limit information system access to authorized users, processes acting on behalf of authorized users, and devices (including other information systems). Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Access Control AC.1.002 Limit information system access to the types of transactions and functions that authorized users are permitted to execute. Kubernetes cluster pods should only use approved host network and port range 5.0.0
Access Control AC.1.002 Limit information system access to the types of transactions and functions that authorized users are permitted to execute. Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Access Control AC.2.007 Employ the principle of least privilege, including for specific security functions and privileged accounts. Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Access Control AC.2.016 Control the flow of CUI in accordance with approved authorizations. Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Configuration Management CM.2.062 Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities. Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Configuration Management CM.3.068 Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. Kubernetes cluster pods should only use approved host network and port range 5.0.0
Risk Assessment RM.2.143 Remediate vulnerabilities in accordance with risk assessments. Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version 1.0.2
System and Communications Protection SC.1.175 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. Kubernetes cluster pods should only use approved host network and port range 5.0.0
System and Communications Protection SC.3.177 Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys 1.0.0
System and Communications Protection SC.3.183 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). Kubernetes cluster pods should only use approved host network and port range 5.0.0
System and Information Integrity SI.1.210 Identify, report, and correct information and information system flaws in a timely manner. Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version 1.0.2

FedRAMP High

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP High. For more information about this compliance standard, see FedRAMP High.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC-4 Information Flow Enforcement Authorized IP ranges should be defined on Kubernetes Services 2.0.1
Configuration Management CM-6 Configuration Settings Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters 1.0.2
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits 8.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should not share host process ID or host IPC namespace 4.0.1
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should only use allowed AppArmor profiles 5.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should only use allowed capabilities 5.0.1
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should only use allowed images 8.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should run with a read only root file system 5.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster pod hostPath volumes should only use allowed host paths 5.0.1
Configuration Management CM-6 Configuration Settings Kubernetes cluster pods and containers should only run with approved user and group IDs 5.0.2
Configuration Management CM-6 Configuration Settings Kubernetes cluster pods should only use approved host network and port range 5.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster services should listen only on allowed ports 7.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster should not allow privileged containers 8.0.0
Configuration Management CM-6 Configuration Settings Kubernetes clusters should not allow container privilege escalation 6.0.1
System and Communications Protection SC-7 Boundary Protection Authorized IP ranges should be defined on Kubernetes Services 2.0.1
System and Communications Protection SC-7 (3) Access Points Authorized IP ranges should be defined on Kubernetes Services 2.0.1
System and Communications Protection SC-8 Transmission Confidentiality and Integrity Kubernetes clusters should be accessible only over HTTPS 7.0.0
System and Communications Protection SC-8 (1) Cryptographic or Alternate Physical Protection Kubernetes clusters should be accessible only over HTTPS 7.0.0
System and Communications Protection SC-12 Cryptographic Key Establishment and Management Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys 1.0.0
System and Communications Protection SC-28 Protection of Information at Rest Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host 1.0.0
System and Communications Protection SC-28 (1) Cryptographic Protection Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host 1.0.0
System and Information Integrity SI-2 Flaw Remediation Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version 1.0.2

FedRAMP Moderate

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP Moderate. For more information about this compliance standard, see FedRAMP Moderate.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC-4 Information Flow Enforcement Authorized IP ranges should be defined on Kubernetes Services 2.0.1
Configuration Management CM-6 Configuration Settings Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters 1.0.2
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits 8.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should not share host process ID or host IPC namespace 4.0.1
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should only use allowed AppArmor profiles 5.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should only use allowed capabilities 5.0.1
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should only use allowed images 8.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should run with a read only root file system 5.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster pod hostPath volumes should only use allowed host paths 5.0.1
Configuration Management CM-6 Configuration Settings Kubernetes cluster pods and containers should only run with approved user and group IDs 5.0.2
Configuration Management CM-6 Configuration Settings Kubernetes cluster pods should only use approved host network and port range 5.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster services should listen only on allowed ports 7.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster should not allow privileged containers 8.0.0
Configuration Management CM-6 Configuration Settings Kubernetes clusters should not allow container privilege escalation 6.0.1
System and Communications Protection SC-7 Boundary Protection Authorized IP ranges should be defined on Kubernetes Services 2.0.1
System and Communications Protection SC-7 (3) Access Points Authorized IP ranges should be defined on Kubernetes Services 2.0.1
System and Communications Protection SC-8 Transmission Confidentiality and Integrity Kubernetes clusters should be accessible only over HTTPS 7.0.0
System and Communications Protection SC-8 (1) Cryptographic or Alternate Physical Protection Kubernetes clusters should be accessible only over HTTPS 7.0.0
System and Communications Protection SC-12 Cryptographic Key Establishment and Management Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys 1.0.0
System and Communications Protection SC-28 Protection of Information at Rest Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host 1.0.0
System and Communications Protection SC-28 (1) Cryptographic Protection Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host 1.0.0
System and Information Integrity SI-2 Flaw Remediation Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version 1.0.2

HIPAA HITRUST 9.2

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - HIPAA HITRUST 9.2. For more information about this compliance standard, see HIPAA HITRUST 9.2.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Privilege Management 1149.01c2System.9 - 01.c The organization facilitates information sharing by enabling authorized users to determine a business partner's access when discretion is allowed as defined by the organization and by employing manual processes or automated mechanisms to assist users in making information sharing/collaboration decisions. Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Privilege Management 1153.01c3System.35 - 01.c All file system access not explicitly required is disabled, and only authorized users are permitted access to only that which is expressly required for the performance of the users' job duties. Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Segregation of Duties 1229.09c1Organizational.1 - 09.c Separation of duties is used to limit the risk of unauthorized or unintentional modification of information and systems. Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2

NIST SP 800-53 Rev. 5

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-53 Rev. 5. For more information about this compliance standard, see NIST SP 800-53 Rev. 5.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC-3 (7) Role-based Access Control Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Access Control AC-4 Information Flow Enforcement Authorized IP ranges should be defined on Kubernetes Services 2.0.1
Configuration Management CM-6 Configuration Settings Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters 1.0.2
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers CPU and memory resource limits should not exceed the specified limits 8.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should not share host process ID or host IPC namespace 4.0.1
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should only use allowed AppArmor profiles 5.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should only use allowed capabilities 5.0.1
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should only use allowed images 8.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster containers should run with a read only root file system 5.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster pod hostPath volumes should only use allowed host paths 5.0.1
Configuration Management CM-6 Configuration Settings Kubernetes cluster pods and containers should only run with approved user and group IDs 5.0.2
Configuration Management CM-6 Configuration Settings Kubernetes cluster pods should only use approved host network and port range 5.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster services should listen only on allowed ports 7.0.0
Configuration Management CM-6 Configuration Settings Kubernetes cluster should not allow privileged containers 8.0.0
Configuration Management CM-6 Configuration Settings Kubernetes clusters should not allow container privilege escalation 6.0.1
System and Communications Protection SC-7 Boundary Protection Authorized IP ranges should be defined on Kubernetes Services 2.0.1
System and Communications Protection SC-7 (3) Access Points Authorized IP ranges should be defined on Kubernetes Services 2.0.1
System and Communications Protection SC-8 Transmission Confidentiality and Integrity Kubernetes clusters should be accessible only over HTTPS 7.0.0
System and Communications Protection SC-8 (1) Cryptographic Protection Kubernetes clusters should be accessible only over HTTPS 7.0.0
System and Communications Protection SC-12 Cryptographic Key Establishment and Management Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys 1.0.0
System and Communications Protection SC-28 Protection of Information at Rest Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host 1.0.0
System and Communications Protection SC-28 (1) Cryptographic Protection Temp disks and cache for agent node pools in Azure Kubernetes Service clusters should be encrypted at host 1.0.0
System and Information Integrity SI-2 Flaw Remediation Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version 1.0.2
System and Information Integrity SI-2 (6) Removal of Previous Versions of Software and Firmware Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version 1.0.2

NZ ISM Restricted v3.5

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NZ ISM Restricted v3.5. For more information about this compliance standard, see NZ ISM Restricted v3.5.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control and Passwords NZISM Security Benchmark AC-18 16.6.9 Events to be logged Resource logs in Azure Kubernetes Service should be enabled 1.0.0
Gateway security NZISM Security Benchmark GS-2 19.1.11 Using Gateways Authorized IP ranges should be defined on Kubernetes Services 2.0.1
Infrastructure NZISM Security Benchmark INF-9 10.8.35 Security Architecture Azure Policy Add-on for Kubernetes service (AKS) should be installed and enabled on your clusters 1.0.2
Infrastructure NZISM Security Benchmark INF-9 10.8.35 Security Architecture Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Software security NZISM Security Benchmark SS-3 14.1.9 Maintaining hardened SOEs Kubernetes cluster containers should not share host process ID or host IPC namespace 4.0.1
Software security NZISM Security Benchmark SS-3 14.1.9 Maintaining hardened SOEs Kubernetes cluster containers should run with a read only root file system 5.0.0
Software security NZISM Security Benchmark SS-3 14.1.9 Maintaining hardened SOEs Kubernetes cluster should not allow privileged containers 8.0.0
Software security NZISM Security Benchmark SS-3 14.1.9 Maintaining hardened SOEs Kubernetes clusters should be accessible only over HTTPS 7.0.0
Software security NZISM Security Benchmark SS-3 14.1.9 Maintaining hardened SOEs Kubernetes clusters should disable automounting API credentials 3.0.1
Software security NZISM Security Benchmark SS-3 14.1.9 Maintaining hardened SOEs Kubernetes clusters should not allow container privilege escalation 6.0.1
Software security NZISM Security Benchmark SS-3 14.1.9 Maintaining hardened SOEs Kubernetes clusters should not grant CAP_SYS_ADMIN security capabilities 4.0.0
Software security NZISM Security Benchmark SS-3 14.1.9 Maintaining hardened SOEs Kubernetes clusters should not use the default namespace 3.0.1

Reserve Bank of India - IT Framework for NBFC

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Reserve Bank of India - IT Framework for NBFC. For more information about this compliance standard, see Reserve Bank of India - IT Framework for NBFC.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
IT Governance RBI IT Framework 1 IT Governance-1 Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version 1.0.2
Information and Cyber Security RBI IT Framework 3.1.a Identification and Classification of Information Assets-3.1 Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Information and Cyber Security RBI IT Framework 3.1.c Role based Access Control-3.1 Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Information and Cyber Security RBI IT Framework 3.1.g Trails-3.1 Azure Kubernetes Service clusters should have Defender profile enabled 1.0.3
Information and Cyber Security RBI IT Framework 3.3 Vulnerability Management-3.3 Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version 1.0.2
Information and Cyber Security RBI IT Framework 3.3 Vulnerability Management-3.3 Running container images should have vulnerability findings resolved 1.0.1

RMIT Malaysia

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - RMIT Malaysia. For more information about this compliance standard, see RMIT Malaysia.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Cryptography RMiT 10.19 Cryptography - 10.19 Both operating systems and data disks in Azure Kubernetes Service clusters should be encrypted by customer-managed keys 1.0.0
Access Control RMiT 10.54 Access Control - 10.54 Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Access Control RMiT 10.55 Access Control - 10.55 Kubernetes cluster containers should only use allowed capabilities 5.0.1
Access Control RMiT 10.55 Access Control - 10.55 Kubernetes cluster containers should run with a read only root file system 5.0.0
Access Control RMiT 10.55 Access Control - 10.55 Kubernetes cluster pods and containers should only run with approved user and group IDs 5.0.2
Access Control RMiT 10.55 Access Control - 10.55 Kubernetes cluster should not allow privileged containers 8.0.0
Access Control RMiT 10.55 Access Control - 10.55 Kubernetes clusters should not allow container privilege escalation 6.0.1
Access Control RMiT 10.60 Access Control - 10.60 Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Access Control RMiT 10.61 Access Control - 10.61 Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Access Control RMiT 10.62 Access Control - 10.62 Role-Based Access Control (RBAC) should be used on Kubernetes Services 1.0.2
Patch and End-of-Life System Management RMiT 10.65 Patch and End-of-Life System Management - 10.65 Kubernetes Services should be upgraded to a non-vulnerable Kubernetes version 1.0.2
Security Operations Centre (SOC) RMiT 11.17 Security Operations Centre (SOC) - 11.17 Authorized IP ranges should be defined on Kubernetes Services 2.0.1
Security Operations Centre (SOC) RMiT 11.17 Security Operations Centre (SOC) - 11.17 Authorized IP ranges should be defined on Kubernetes Services 2.0.1
Control Measures on Cybersecurity RMiT Appendix 5.5 Control Measures on Cybersecurity - Appendix 5.5 Kubernetes cluster services should only use allowed external IPs 4.0.1
Control Measures on Cybersecurity RMiT Appendix 5.6 Control Measures on Cybersecurity - Appendix 5.6 Kubernetes cluster pods should only use approved host network and port range 5.0.0
Control Measures on Cybersecurity RMiT Appendix 5.6 Control Measures on Cybersecurity - Appendix 5.6 Kubernetes cluster services should listen only on allowed ports 7.0.0
Control Measures on Cybersecurity RMiT Appendix 5.6 Control Measures on Cybersecurity - Appendix 5.6 Kubernetes clusters should be accessible only over HTTPS 7.0.0

Next steps