The problem
The digest that arrives every morning and changes nothing
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
The standard failure mode of threat intelligence is comfortable and quiet: a subscription is bought, a portal is stood up, a daily digest lands in a mailbox, and eighteen months later nobody can name one decision that would have gone differently without it. The reporting is usually competent. What is missing is a receiving end — a person with a pending decision that the information could tilt. Without that, intelligence is journalism about other people's incidents, read with interest and acted on never.
The fix is to enumerate the decisions first. A security programme makes the same kinds of calls again and again: which of this month's vulnerabilities get patched out of turn; which techniques the detection engineers build coverage for next; whether a rumoured campaign against the sector warrants raising posture; what the leadership is told is changing in the environment. Each becomes a written intelligence requirement — the question, its owner, the form of a useful answer — and everything collected or bought is judged against that list. What serves no requirement is noise, however interesting, and it is allowed to pass by unread with a clear conscience.
Two shapes of the same spend
A feed subscription and an intelligence function, side by side
The budget line can look identical. The difference is whether anything downstream is obliged to change.
| Option | What arrives | Who consumes it | What it changes | How it is judged | Best for |
|---|---|---|---|---|---|
| A feed subscription | Everything the provider publishes, at the provider's priorities. | A mailbox, a portal, occasionally an analyst skimming. | Little that can be pointed to; the queue orders itself as before. | By renewal date, which is to say not at all. | A raw input into a function that exists — never a substitute for one. |
| An intelligence function | Answers to written requirements, filtered for this estate and sector. | The named owner of each pending decision, in their own workflow. | Patch order, detection backlog, posture, what leadership is told. | By decisions changed per quarter, reviewed requirement by requirement. | A programme mature enough to have recurring decisions worth informing. |
The working cycle
From a standing question to a queue that reordered itself
The cycle is old doctrine; the discipline is the last step, which most programmes skip.
Requirements, written and owned
Each recurring decision becomes a standing question with a named owner — the vulnerability manager, the detection lead, the CISO — and a stated form of useful answer. A short list every source is judged against.
Collection chosen, not accumulated
Sources — commercial, open, sectoral, and your own incident history, which is the most underused source in most organisations — earn their place by which requirement they serve. Less volume, higher relevance, known gaps.
Analysis that says so-what
Raw reporting is confronted with your estate: is the exploited product deployed here, is the technique visible to current detections, does this change any standing answer. A judgement specific to you, with its reasoning shown.
Delivery inside the decision
The answer lands where the decision is made — a reprioritised item in the patch queue, a ticket in the detection backlog, a paragraph in the leadership brief — not in a parallel portal. Intelligence indistinguishable from the workflow it serves.
Feedback, kept honestly
Each quarter, every requirement is asked one question: did any decision change because of what was delivered. Requirements that keep answering no are rewritten or retired. A programme that can prove its keep, or shrink.
Our role
The analysis we supply and the judgement calls that stay yours
- 01
Requirements before sources
We run the workshop that turns your recurring decisions into written requirements, and we will say plainly when an existing subscription serves none of them.
- 02
The analytical layer
Our analysts confront the reporting with your estate and produce the so-what — because the expensive gap in most programmes is not information but the hours to weigh it against a specific environment.
- 03
Wired into your operations
Findings are delivered into your patching, detection and briefing workflows — and where detection is run by a partner, into theirs — so nothing depends on anyone remembering to check a portal.
What the organisation patches first, watches for, and tells its board are decisions your owners keep; our work is to make sure each one is taken with the best available picture, and to show which decisions the intelligence actually moved.
Common questions
What buyers ask
Our security tools already include threat feeds. What is missing?+
The feeds inside your tools do one narrow job well: they update machine-readable indicators so the tools block and flag current infrastructure. What they cannot do is answer the questions a human decision needs — whether a reported campaign changes your patch order, whether your detections would see the technique involved, whether posture should rise. Those need analysis against your specific estate, and a named person receiving the answer. If no decision in your organisation consumes intelligence, adding more feeds adds volume to a pipeline with no outlet; the missing piece is the receiving end, and that is where we start.
How much of the intelligence needs to be specific to our region and sector?+
More than a global feed provides and less than a bespoke unit costs. The techniques that matter are largely global — the same initial-access and extortion playbooks appear everywhere — but the targeting is not: which sectors are being worked, which lures fit the region's languages and business rhythms, which regulatory obligations a given incident type would trigger here. That local layer is exactly the part generic subscriptions are weakest at and the part your own sources are strongest in: sector peers, national advisories, and your own incident history. A sensible programme buys the global layer and builds the local one.
How do we know whether the intelligence programme is paying for itself?+
Count changed decisions, because that is the product. Each quarter, walk the requirement list and ask the owner of each: did anything you decided go differently because of what was delivered — a patch pulled forward, a detection built that would not have been, a posture change, a briefing that altered what leadership funded. Keep the tally honestly, including the zeros. A requirement that changes nothing for two quarters is rewritten or retired, and a programme where most requirements score zero should shrink to a feed and stop pretending. The discipline sounds harsh; it is what separates a capability from a subscription with analysts attached.
In this cluster
Next step
Define your intelligence requirements
A requirements workshop that names the five decisions your intelligence must serve and what each needs delivered, to whom, on what rhythm.

