Rust · eBPF · Kubernetes · Network Security · Attack Surface Management
I build security systems around explicit trust boundaries, reproducible engineering, and evidence-backed claims.
- Security control planes with explicit policy and trust boundaries.
- High-performance network infrastructure where latency, observability, and failure modes are first-class concerns.
- Attack-surface and vulnerability systems that turn raw findings into evidence and remediation.
- Adversary-emulation tooling with safety constraints and measurable Blue Team feedback.
🛰️ ShapoclyackSelf-hosted External Attack Surface Discovery and Risk-Based Vulnerability Management. Asset-centric identity, distro-aware patch gaps, and mechanical remediation verification.
|
High-performance HTTP/HTTPS forward proxy and Secure Web Gateway written in Rust. Selective TLS inspection, tiered caching, policy enforcement, and asynchronous analytics.
|
🛡️ FerrumSelf-hosted Kubernetes enforcement plane written in Rust. Admission policy, signed bundles, and eBPF runtime enforcement.
|
🔥 AsmodeusAdversary-emulation / BAS and chaos-engineering engine. Built around explicit safety boundaries and Blue Team feedback metrics.
|
Make trust explicit. Make failure observable. Make claims reproducible.
I prefer systems that are:
- Inspectable — architecture and policy should be understandable without archaeology.
- Measurable — performance, reliability, and security claims need evidence.
- Composable — capabilities should have clear boundaries instead of growing around one critical path.
- Safe by construction — dangerous operations need constraints, not just documentation.
- Operationally boring — predictable systems beat clever systems in production.
security infrastructure
├── attack surface management
├── secure web gateways
├── Kubernetes enforcement
├── eBPF runtime controls
└── adversary emulation
Security engineering with explicit boundaries, measurable behavior, and reproducible results.