I'm Imran — I build agentic AI for cybersecurity, and I'm allergic to systems that only detect.
At Vezran / Zyberpol I lead AI/ML on a system that takes a threat all the way to closed — with proof. The loop I build by:
detect → decide → approve → act → verify → prove
# the model reasons · the control layer governs · a human stays in command · every action leaves evidenceMost AI security stops at "we found something." The hard, unglamorous, valuable part is trusted closure — and proof a regulator will accept. That's the part I care about.
I build on the belief that the model is rented and swappable; the control layer is the moat.
AGENTIC AI → multi-agent orchestration, tool use, governed autonomy
LLM SECURITY → prompt-injection robustness, red-teaming, adversarial evals
AI SAFETY → differential privacy, causal inference, fraud / lure detection
RELIABILITY → the eval harness that decides if a model can be trusted
MLOPS → notebook → production, without losing the receipts
+ LangChain · Hugging Face · DSPy · RAG · LoRA/QLoRA · vector DBs
| Repo | Proof of |
|---|---|
| dspy-security-bench | LLM security — does prompt optimization make agents more injectable? Measured against AgentDojo's attack suite. |
| lurebench | AI safety — a benchmark for detecting AI-generated fraud lures (phishing, romance scams). |
| PyRIT | Red-teaming — working in Microsoft's framework for proactively finding risk in generative AI. |
| opacus · dowhy | Rigor — differential privacy for PyTorch, and causal inference done right. |
EOF — the model investigates · the control layer decides · a human stays in command · and it proves the threat was closed.

