Enno Gelhaus
I run operations and security at Postiz, an open-source social media scheduling platform. Outside of that I build the GHub applications under Gelhaus Solutions.
Every figure here is read from the system that owns it. Checked 15 minutes ago. How they are counted
What the job actually is
A C-level title here isn't about handing work to other people. The work is mine.
It covers security engineering and vulnerability research, trust and abuse, support and community, CI/CD, monitoring, CNA operations, and hiring.
I'm also the second-largest contributor to the core codebase, at 438 commits. My background is DevSecOps and platform engineering, and I still spend most of the week in code.
What that has produced
42 published advisories and 20 CVEs across the two programmes, seven of them critical, the highest scoring 10.0.
The largest cluster is server-side request forgery, eight advisories deep. That is not an accident of the codebase. A social scheduler exists to fetch and post things on your behalf, so making outbound requests to attacker-influenced URLs is its job description rather than a mistake in it. Bug classes that come from a product's shape have to be treated structurally, not one endpoint at a time.
One rule for everything I build
If the API can do it, the UI has to do it too.
I've seen too many tools ship a feature behind an undocumented endpoint and call it done. Anything only a maintainer can drive isn't finished. It costs more up front. I've never regretted it.
What's actually live
The GHub line is open core: base version free, Pro and Enterprise not. Closed work is labelled on the card.
What I actually run
Grouped by discipline instead of a wall of logos. These run in production. Things I tried once are not on the list.
Need a second opinion on something?
Security review, setting up a CVE programme, platform work, or an architecture you are not sure about. Email is fastest.
Email me