Cloud platforms · 01 · The problem and the decision
Kubernetes Cluster Estate (AKS)How much of your AKS attack surface can you prove is closed?
Defender, Advisor and your scanners already list findings. What is missing is the loop after detection: proving which findings are true, deciding what to fix, fixing it through your own pipeline, and proving the attack surface stays reduced.
For platform, security and engineering leads running AKS on Azure who need an independent security review, a smaller attack surface and evidence that best practice holds.
3–4 weeks elapsedOne agreed AKS estate: the named clusters and their Azure subscriptionsA named architect accountable
02 · What we check
Agree the scope. Inspect the evidence.
We check identity and access, network exposure, workload and admission controls, images and registries, secrets, and logging and alerting, across the clusters and the subscriptions they run in. The method is encoded as software: checks, read guards, a verifier and publishers do the reading, cross-checking and document work, and a named architect decides what every result means and signs every published word. That is why the time goes into fixes rather than slides.
A verified check catalogue
Each check is written down before it runs: the surface it reads (Azure Resource Graph, Log Analytics, or the cluster through run-command), the access it needs, the expected result and a positive control. A check that cannot show its positive control is reported as a failed check, never as a clean result.
Read-only on your estate
We read the agreed subscriptions and clusters with read-level roles, and our kit refuses anything but read commands. The exact permissions are listed in the proposal; we walk through them in the working session.
A record of every session
Live reads run in bracketed sessions. After each one we file a record showing that our identity made no changes to your Azure resources.
Every check and finding challenged first
An independent verification pass tries to break each check before it runs and each finding before it reaches the record. Failures surface as failures. Severity, scope and wording remain an architect's decision.
Records in your tools, with receipts
Findings, decisions and tickets land in your own Jira and Confluence through publishers that keep a manifest and a receipt for every item. These are the only places our tooling writes, and you decide what is shared.
Posture-hold jobs
In Module 3 the same catalogue reruns on a schedule against the baseline you approved and reports deviations with evidence, from your own tenant if you prefer. An architect reviews each deviation before it reaches you.
What we need from you
Reader on the agreed subscriptions and the AKS run-command permission on the agreed clusters, as listed in the proposal.
Read-only access to the infrastructure code and pipelines that declare the estate.
A named platform owner and the people who own decisions.
For Module 2: pre-production first, protected branches and your approvers for every pull request.
Scope and boundaries
We take no rights to change Azure resources, clusters or protected branches. Our engineer pushes agreed fixes as pull requests; your approvers merge and your pipeline deploys.
We find misconfigurations, exposure and the known vulnerabilities your tools report. Penetration testing, disruptive failover and 24/7 operations or incident response are not included: Hold proves the posture, it does not run the platform.
EKS, GKE and clusters outside the agreed estate need separate scope.
03 · What you get
A decision you can act on.
Module 1, Acclimatise: a register of findings, each evidenced against code or the live estate, with every open question paired with a proposed default.
Module 1: a decision sheet you only have to approve, and a Findings & Agreement Record you review line by line, with every correction published.
Module 2, Remediate: the agreed priority fixes delivered as pull requests over four two-week sprints, each checked against its acceptance criteria, with a decision log and a handover pack your team can operate from.
Module 3, Hold: deviations from the approved baseline reported with evidence, and a short quarterly decision batch instead of a dashboard.
04 · Relevant work and a sample
See the thinking behind the review.
Delivery through an MSP partner
An assessment grounded in the Azure estate
For a Dutch municipality, through Infield ICT, Atsky assessed an AKS landing zone built on Bicep and Azure DevOps. Resource Graph and Traffic Analytics supplied evidence for the findings. The engagement also included an AKS enablement programme for the team inheriting the platform.
Findings issued for review in three weeks; a signed, evidence-backed agreement record inside four. The open-question list fell from 53 to 14 in two days of checks, without a meeting. Two findings we got wrong were corrected by us before the client found them; one dispute was settled by evidence in the client's favour; more than a hundred review comments, no escalations. Forty scoped, about thirty closed: half evidenced platform changes, half decision records and designs, each with filed evidence and a recorded owner decision.
05 · Duration and price
A defined engagement. An agreed scope.
From €10,500Starting price, excluding VAT
Module 1, Acclimatise, from €10,500, excluding VAT. We quote a fixed fee after agreeing the clusters, subscriptions, access and review depth. Findings are issued for review in three weeks and the signed record follows inside four.
We agree the included scope, deliverables and fixed fee in the proposal before work starts.
Duration
3–4 weeks elapsed
Base scope
One agreed AKS estate: the named clusters and their Azure subscriptions
Your data
We read your Azure estate and never modify Azure resources or AKS clusters. Our tooling pulls repositories read-only and writes only records, to your Jira and Confluence. Agreed fixes are pushed by our engineer as pull requests to protected branches; your approvers merge and your pipeline deploys. If your policy requires it, we work with EU-only processing and zero data retention. Any extra cost is named in the proposal.
Our method is encoded as software: it collects evidence, drafts findings and publishes with receipts. A named architect checks and signs every published word. How we work and handle data →
06 · Request a working session
Start with the question you need to resolve.
In 45 minutes, bring your AKS estate and your access policy. We walk through exactly what we read, where we write and the session record we file, show an illustrative register row, and agree whether Module 1 fits.