abdulmalik
devsecops product security infrastructure security
i write golang for security tooling, kubernetes clis, audit tools and go+templ products, and i sit with the infra and development teams, ensuring products are secure, doing code reviews and building secure pipelines, from appsec, cloud and kubernetes security, the supply chain: ebpf, sboms, runtime. i've disclosed vulns to openclassroom, andela and kuda, and i contribute to open source.
right now i'm in runtime security, supply chain and cloud posture: ebpf on ci runners, sboms that get queried, and the evidence that survives an audit. i lead devsecops at bluebulb financials. 2x aws community builder.
in a day i'm on agent identity, runtime policy and attested tool calls: proving what an agent ran, under what policy, and that it wasn't a borrowed name. next i want work that's close to the machine — detection and attestation of ci/cd, kubernetes memory and runtime, anything low-level enough to care what the box is doing. i still ship products from lived experience, and i write.
projects
see all →-
cicd-sensor // edr for github actions. the job is the attack surface.
open-source ebpf runtime security sensor for github actions and gitlab ci. artifact signing and pinned shas matured. runtime insight into the runner itself lagged behind.
-
k8sradar // what's known about the cluster you actually run, not the one in the docs.
you put in provider, kubernetes version, add-ons, node os. you get exploitability, kev, and the version that closes it. built for the moment someone from leadership asks if you are exposed to the thing on the news.
-
supabase-audit // rls that looks locked until you actually query it.
cli that finds over-permissive row level security, exposed tables, and the supabase misconfigs that keep showing up in assessments.