Skip to main content
Compliance · High severity

AKS Cluster API Server Not Private

The Kubernetes API is reachable from the internet, so a leaked kubeconfig can be used from anywhere.

Free to start. No card. The playground just needs your work email.

Azureprovider
Highseverity
Compliancewhere it shows up
Manualfix, steps written out

AzureKubernetes

Found, explained, handed over.

Where the estate departs from your policies, frameworks and tagging rules.

01

Detect

ZopNight checks this automatically across Azure, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Restrict public access to AKS API server.

03

Fix

The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.

Applies to
AKS Clusters on Azure
The fix, by hand
  1. Decide between full Private cluster mode (API server has no public endpoint) and Authorized IP ranges (public endpoint with allowlist).
  2. Authorized IP ranges (online): AKS → the resource → Networking → API server authorized IP ranges → add corporate + CI egress CIDRs. Set and save.
  3. Private cluster (requires recreate): create a new AKS with --enable-private-cluster; ensure kubectl clients run on a peered VNet, jump host, or use the private endpoint.
  4. Update CI/CD runners to a self-hosted pool inside the cluster's VNet (or use a hosted agent with VNet integration).
  5. Validate kubectl access from each authorized network; confirm public internet probes get TCP-refused.

These are the steps the finding carries in the product.

Category
Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
Where it appears
The Compliance tab of Recommendations, with every affected resource listed.
Rule ID
RC-1353
Full reference

AKS Cluster API Server Not Private

Related checks

See the compliance findings in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

Prefer to talk it through first? Book 20 minutes with the team.

  • $30M+annualised cloud spend under management
  • 550K+resources tracked since launch
  • 20-60%off the bill in the first month
  • SOC 2Type II report, plus ISO 27001

Figures published on zop.dev.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·