Hani Early

I came to security analysis with a perspective shaped by living and operating across multiple cultural and political contexts — not as a tourist but as someone who internalized different systems from the inside. That experience produces a different relationship to cultural assumptions, institutional logic, and the way adversaries actually think. When you have operated inside more than one system, you stop taking any single system's premises for granted. That habit of mind is, I think, the most useful thing I bring to security analysis. It is also the hardest thing to train.

A decade in military intelligence — CENTCOM, the full MENA theater — refined that instinct into discipline. Understanding an adversary is not primarily a technical problem. It is a human one: their grand strategy, their institutional pressures, their tolerance for risk, the gap between what they say and what they intend. The analytical tradecraft that answers those questions sits upstream of the kill chain. It is what tells you not just what an adversary is doing, but what they will do next and why — and that forward-looking discipline is what Doctrine Security is built around.

In the private sector, I applied that foundation to enterprise security — leading nation-state threat intelligence work at a global consulting firm, building executive risk protection programs, and developing the detection engineering and SOC transformation methodology documented on this site. My proficiency in nation-state threats, including deep expertise in Iranian cyber operations, is grounded in direct access to primary sources and years of analysis that goes beyond English-language reporting. Doctrine Security is the formalization of what I have observed and built. If something here resonates, I am happy to discuss it.