Showing Post From Security
Runtime security in 2026: revisit Falco, Tetragon and Tracee before you trust another runtime alert
Most teams now scan images before they ship and check manifests before they reach the cluster. Then the container starts, and for many of us the story stops there.
Read moreContainer sandboxing in 2026: revisit gVisor, Kata Containers and Firecracker before you run another untrusted workload
A normal container is a set of Linux processes with namespaces, cgroups, capabilities and a seccomp profile around them. That is a good packaging boundary and a reasonable resource boundary.
Read moreSecret scanning in 2026: revisit Gitleaks, TruffleHog and detect-secrets before another API key lands in a commit
Picture a software company in Bhubaneswar that builds cold chain tracking and export paperwork software for seafood processors and exporters along the Odisha and north Andhra coast (an invented example, not a real client).
Read moreContainer image signing in 2026: revisit cosign, Notation and in-toto attestations before you trust another image tag
Picture a software company in Rajkot that builds production planning and job work software for foundries, forging units and engineering workshops across Saurashtra (an invented example, not a real client).
Read moreTLS certificate automation in 2026: revisit cert-manager, Certbot and step-ca before the next certificate expires on you
Think of a bicycle and auto parts manufacturer in Ludhiana that sells through about 400 dealers across Punjab, Haryana, Rajasthan and the hill states (an invented example, not a real client).
Read moreVulnerability scanners in 2026: revisit Trivy, Grype and OSV-Scanner before you trust another green scan
Picture a small software company in Bhubaneswar that builds claims and pre-authorisation software for hospitals that deal with health insurance TPAs (an invented example, not a real client).
Read more