Intelligence as a Function: Building the OSINT Capability Your Team Is Missing
He was not a hacker. He had no classified access, no government tools, no intelligence community background. What he had was method. He was meticulous, analytically patient, and genuinely curious about how information connects.
After almost a week of evacuations, coordinating intelligence support, and crisis management in the Gulf region, I found the time to finish my latest article.
In part one of this piece, I described the principal as an attack surface. Not because they are careless, but because modern targeting is assembled upstream. Long before a door handle is touched, the adversary has already mapped routines, social ties, assets, assistants, vendors, and the soft edges of the network through open-source data. That is not a theoretical risk. It is how the environment operates in 2026.
Part two is about what you do with that reality when you are not a state service with institutional depth, long budgets, and bureaucratic memory, but a private protection team with a small roster, a highly fluid schedule, a chaotic chain of command, a finite budget, and a principal who expects capability without overhead.
The answer is a function. One that turns information into posture, systematically, before the threat becomes visible. Later in this piece I describe the four concrete outputs that make that function real and sustainable. But first, the structural decision that made me believe in it.