All topics
Security

Security built into the pipeline, not bolted on after the breach.

5 articlesEN · DE

Security is not a feature you add at the end — it is a property of how you design, build and ship software. The teams that stay out of incident channels bake it into the workflow: threat modeling before code, pipelines that fail closed, and auth that is boring because it is correct. I treat security as an engineering discipline with measurable controls, including in regulated enterprise systems, backed by CSA CCSK and CCZT.

Articles in this hub

5 articles

FAQ

What is your security background?
I build and harden production systems at scale, including regulated enterprise systems — DevSecOps pipelines, AppSec, auth and supply-chain hardening — as a Google Cloud Ambassador with CSA CCSK and CCZT.
Are you available to hire?
Yes — threat modeling, AppSec reviews, DevSecOps pipelines and auth design, as a contract, consulting or selected full-time engagement, remote across the EU or on-site in Germany. I work fluently in English.
How do we start working together?
Tell me what you need to secure — a product, a pipeline, an auth layer — on the contact page, and I will reply with how I can help.

Want security that ships with you?

From auth design to hardened CI/CD and supply-chain defense, I help teams build security into the workflow instead of patching it after an incident.

See security services →
ENDE