Assessment · Typically two weeks
DevSecOps Assessment
Which security controls exist, which are missing, and how to add the ones that matter to the path developers use.
Scope
- Scanning coverage: dependencies, containers, IaC, secrets
- Artifact signing, provenance and admission
- Credentials, workload identity and RBAC
- Cloud and Kubernetes posture
- Control mapping to the frameworks you report against
Deliverables
- Gap analysis against a practical control set
- Remediation plan ordered by exposure
- Pipeline and admission changes ready to implement
We need read access to the relevant environments and a few hours of the team's time, never production credentials shared outside your own tooling.
How we think about it
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.
Cloud architecture · Security · 7 min
Landing zones before the first workload
The account structure, identity, network and guardrails that every later decision rests on. What a landing zone has to settle, what it can leave open, and the order that avoids rebuilding it in year two.