The rest of the portfolio

Request access

Your name is the only required field. When you send this, my phone pings — and I approve it personally, the moment it reaches me. A link only ever exists because I deliberately released it.

Behind the gate, grouped by the security function each system serves:

• Vulnerability management at fleet scale — an inventory-and-correlation agent, the fleet reporter that turns its findings into owned work with running clocks, and an external attack-surface counterpart.
• Endpoint detection and response — a resident monitor that ties network activity to verified executable identity, with evidence collection and reversible containment.
• Key custody and encryption — local encryption whose actual subject is recovery: not losing access without creating a path an attacker would enjoy.
• Release and supply-chain integrity — the self-hosted distribution and update service behind my own products, and the identity backbone designed to sit beside it.
• Security operations workflow — the ownership and ticketing layer, including a data-integrity audit that found two defects where the first was masking the second.
• The engineering underneath — session coordination, integration test infrastructure, and developer tooling.

For each one: what it does, the problem it exists to solve, and what I think it demonstrates. Architecture and judgment — not recipes. Some of it is running daily; some is designed and openly labelled as unbuilt.

Requests are rate-limited and expire on their own after 30 days. Your name and note go to me and nowhere else.