Zero Trust Security
Assumptions are the mother of all mistakes. I design systems that verify everything, trust nothing, and minimize attack surfaces.
Principles that guide my approach to security research and software engineering.
(Tap on cards to expand)Assumptions are the mother of all mistakes. I design systems that verify everything, trust nothing, and minimize attack surfaces.
Complexity is where vulnerabilities hide. I fight bloat to keep systems auditable, maintainable, and inherently secure.
Human labor is error-prone. I automate repetitive tasks to ensure consistency, reduce mistakes, and free up time for creative problem-solving.
Heuristics is exploitable. I trust logs, metrics, and Proof-of-Concepts (PoCs) over gut feelings to guide my architectural and security choices.
Whether I design for millions of users or a niche audience, I prioritize speed and efficiency to deliver seamless experiences.
Monoliths get messy. I build systems with interchangeable components to enhance flexibility, scalability, and ease of maintenance.
Looking for proof of my skills?
Check out my
write-ups
about my discoveries.
Declassified architectural overviews of my recent work.
Event-driven architecture handling TB-scale ingestion from hostile sources.
Bypassing advanced anti-bot fingerprinting (TLS, Canvas, Audio) in real-time.
Automated static analysis pipeline for Android (APK) malware detection.
Reconstructing undocumented internal APIs for emulation and monitoring.
A quick overview of the tools, technologies, and methodologies I employ regularly.
I'm a polyglot developer. Here's a breakdown of the top programming languages I've used recently.
| Language | Time spent | Percentage |
|---|---|---|
| languages in total | ||