For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex CloudApplication Security

Azure AKS cluster nodes have public IP addresses misconfiguration detected in code

Rule Details

Cortex AppSec Rule ID

APPSEC_AZURE_143

Category - Subcategory

Public Exposure - VPC VCN VNet

Provider

AZURE

Severity

LOW

Framework

Terraform

Impact

This rule is verifying that Azure Kubernetes Service (AKS) cluster nodes are not assigned public IP addresses. Having a public IP address can be problematic as it exposes the nodes to the internet, which could potentially lead to unauthorized access or malicious attacks. It's a recommended best practice to limit exposure to the web in order to reduce the surface area for these potential threats.

How to Fix

To fix this issue, add the Service annotation "service.beta.kubernetes.io/azure-load-balancer-internal" and set it to "true" in the Kubernetes service configuration. This will ensure AKS cluster nodes do not have public IP addresses.

By setting the "service.beta.kubernetes.io/azure-load-balancer-internal" annotation to "true", it ensures that the Azure load balancer that is automatically created will be internal, which means the IPs of the nodes will not be exposed publicly. This improves the security of your application by reducing the exposure to attack vectors. [source,go]

apiVersion: v1 kind: Service metadata: annotations: service.beta.kubernetes.io/azure-load-balancer-internal: "true" name: internal-app labels: app: internal-app spec: type: LoadBalancer ports:

  • port: 80 selector: app: internal-app


Last updated

Was this helpful?