captain@colombo:~$ ./introduce --brief
▍
Builds secure, automated cloud platforms. Breaks them first, on purpose. I build the platforms I used to defend.
Colombo, Sri Lanka · open to remote · ⌘K to navigate
$ whoami --long
Security teams find problems. Platform teams ship products. I do both jobs — and each one makes me better at the other.
Most organizations run security and engineering as separate worlds: one builds fast, the other audits after. My career has been about collapsing that gap — from the national FINCSIRT defending Sri Lanka's banks, through 24×7 SOC leadership, VAPT and DevSecOps, into platform engineering — across banking, telecom and enterprise IT, for local and international clients, including a Fortune 500 enterprise.
What that combination delivers: platforms that are fast and defensible. Pipelines with security designed in rather than bolted on. Infrastructure holding 99.99% availability for millions of users. One engineer who can handle a compliance audit in the morning and a production incident in the afternoon — no translator required.
What's next: AI on both sides of the fence. I'm building toward AIOps — operations that detect, predict, and heal intelligently — and AI Security, protecting the machine-learning systems every organization is racing to adopt.
MISSION
Make secure the default: platforms where the safe path and the fast path are the same path.
VISION
Engineering where AI observes, security informs design, and humans handle only what machines can't.
NOW
AIOps × AI Security — applying AI to operations, and defending the AI systems entering production.
EDUCATION
MSc Cyber Security — University of Gloucestershire · 2026Dissertation: The Biometric Deed
BSc (Hons) Cyber Security — SLIIT
$ systemctl status ops.service sec.service
Most teams hire a platform engineer or a security engineer. The rare leverage is one person who ships with both threat models in their head.
● active
Build it fast, keep it running.
● active
Assume breach, design accordingly.
$ kubectl get skills -A --sort-by=depth
Blue nodes build; amber nodes defend. Size is depth of daily use. Filter or search to isolate a constellation.
$ git log --career --oneline --graph
Seven years, both sides of the fence. Expand any commit for the diff.
$ ls ~/certs --group-by=domain
Twelve active credentials spanning Kubernetes, Linux, Azure, cloud security and offensive security.
▸ Kubernetes & Linux
▸ Microsoft — DevOps & Cloud
▸ Microsoft — Security
▸ Cloud Security & Offense
$ docker ps --filter status=shipped
Research, running infrastructure, and one side quest. Each card unfolds into architecture → challenge → result.
years across security & platforms
active certifications
uptime platforms operated
domains, one engineer
$ watch -n1 tech-radar --split=domain
What I run in production (adopt), what I'm piloting (trial), and what I'm studying (assess) — platform on the left, security on the right.
$ tail -f ~/writing.log
Notes from both sides of the fence — platform engineering, security, and where AI is dragging both.
▸ in print: Peer-reviewed research: biometric digital-signature schemes for land-registry verification — University of Gloucestershire, 2026.
$ ssh captain@colombo
No contact form, no published email — that's a deliberate security posture, not an oversight. The terminal explains.
Last login: from somewhere behind a well-configured firewall
Type `help` to see available commands.