Harden the software supply chain
Integrate security scanning, SBOMs, policy gates, signing, secrets detection and container controls.
The situation
Today
- Images ship with known vulnerabilities, nobody can prove where an artifact came from, and the security review happens after the deployment it should have stopped.
After the engagement
- Signed, attested artifacts from build to runtime
- Security findings developers see where they work
- Evidence for auditors without a scramble
How we approach it
- 01
Add dependency, container, IaC and secrets scanning to the build path
- 02
Generate SBOMs and sign artifacts with provenance
- 03
Enforce admission policy so only signed, scanned images run
- 04
Replace static credentials with workload identity
- 05
Map the controls to the frameworks you report against
Services involved
DevSecOps & Cloud Security
Security in the delivery path: scanning, SBOMs, signing, admission policy, workload identity and posture review.
DevOps & CI/CD Engineering
Reusable pipelines, faster builds, dependable deployments and release engineering on Azure DevOps, GitHub Actions or GitLab.
Kubernetes & Container Platforms
AKS and EKS platforms: networking, ingress, identity, autoscaling, upgrades and security, kept repeatable with GitOps.
How we think about it
Platform engineering · GitOps · CI/CD · 7 min
Golden paths that engineers actually take
A platform team's output is not the platform; it is the paths other teams take through it. How to build paved roads that are faster than the alternative, keep them honest with the people who use them, and avoid turning them into mandates.
Kubernetes · Security · Platform engineering · 8 min
Isolating tenants on a shared Kubernetes cluster
A namespace is not a security boundary, but a namespace plus five other controls is a usable one. What separates tenants on a shared cluster, what still needs a cluster of its own, and how to decide which customer gets which.
CI/CD · Security · GitOps · 8 min
A pipeline that proves what it ships
Scanning, software bills of materials, signatures and admission control are four separate controls that only mean something together. How to build a delivery path where the cluster refuses anything the pipeline did not vouch for.