Browse categories
Explore
Fiverr Pro
English
$
USD
I will harden and secure your kubernetes cluster and docker containers
Lead Security Architect for Hybrid Cloud, IAM and Zero Trust
Lead Security Architect, 14+ years across banks, telecom and large enterprises, ex-IBM and TOTVS.
Most clients know something is wrong but not where. I find it, then I design what replaces it and the...
Vetted by Fiverr Pro
Marlon Costa was selected by the Fiverr Pro team for their expertise.
Vetted for
Cloud Computing
Cybersecurity
Data Governance & Protection
DevOps Engineering
Regulatory Compliance Consulting
Support & IT
About this Gig
Vetted Pro
Your cluster works. That is not the same as your cluster being safe.
Kubernetes ships wide open and most clusters are close to default. Everything runs, so nobody looks, until a customer asks or a pen test comes back.
You are probably here because
- A customer or auditor asked how you isolate workloads
- Containers run as root because that was the only way to ship
- Every pod can reach every pod and nobody meant that
What I change
- RBAC cut from cluster-admin to what each workload needs
- Root and privileged containers removed, Pod Security enforced
- Network policies, so pods stop reaching pods they should not
- Secrets out of ConfigMaps, image scanning in the build
How it works
- You tell me what you run and we agree a change window
- I apply changes in stages, validate each, log every one
- You get the documentation, rollback path and a walkthrough
What you can count on
Every change reversible, in a window you choose, tested in staging first.
Works with
EKS, GKE, AKS, OpenShift, self-managed, Docker, Helm, Terraform.
Hardened against CIS Kubernetes, NIST SP 800-190 and OWASP K8s Top 10.
Tell me what you run and I will say which fits.
My Portfolio
Other DevOps Engineering Services I Offer
FAQ
Do you need direct access to my Kubernetes environment?
No. In many cases, I can work from documentation, exported evidence, screenshots, configuration samples, architecture diagrams, and live walkthroughs. If direct access is available, we can define a limited and appropriate review model.
What kinds of issues can this review identify?
This review can highlight risks related to cluster configuration, RBAC, service accounts, secrets handling, workload hardening, network policies, policy enforcement, logging, monitoring, and runtime visibility.
Is this a penetration test or a formal compliance audit?
No. This project is a security review and advisory assessment. It is designed to identify control gaps, security weaknesses, and practical hardening priorities, but it is not a penetration test or an official audit unless separately defined.
What will I receive at the end of the project?
Depending on the selected tier, you will receive a structured review with findings, risk observations, practical recommendations, and, in higher tiers, a more detailed roadmap and executive-ready summary.
Can you review managed Kubernetes platforms like EKS, AKS, or GKE?
Yes. This project can be applied to managed Kubernetes services as well as self-managed environments, as long as the scope and available evidence are clearly defined.
