Planning a trip across Gujarat forces a choice that every traveller recognises. You can buy a package where someone else decides the route, hire a driver-guide who knows the ground, build your own itinerary from scratch, or take a light approach with a friend’s advice and a loose plan. None is universally right. The better option depends on your time, your confidence and what you are trying to see. Security teams meet the same fork when they set up ThreatOps, which pairs research on adversaries with deliberate searches for anything the automatic alarms let through. This comparison sets out four ways to run it, scores each on the criteria that matter, and gives a rule for choosing.
The four options on the table
- Feed-first: subscribe to outside streams of threat data and react to what arrives.
- Managed hunting: pay an outside team to search your systems and report findings.
- In-house build: assign your own people to keep questions, sources and hunts.
- Lean advisory: keep a very small function that answers specific questions for decision-makers when asked.
The Ops Atlas offers a short decision tree that sorts these, and it is worth knowing before we compare. If you lack recent telemetry (the Atlas uses ninety days as the yardstick), fix the data first, because no model works without records to search. If nobody in the organisation will take ownership of what hunting turns up, buy managed hunting. If nobody has questions to put to the function, a lean advisory model fits. Otherwise, build.
Criterion one: what you actually get
Feed-first delivers volume. You receive indicators and reports, and you decide what to do with them. The Atlas is wary of this on its own. It says the label “ThreatOps” does not mean a feed subscription, and it cites FIRST for the view that such streams belong in warning workflows, not in automatic enforcement. Value depends on your ability to weigh and filter.
Managed hunting delivers findings. A provider’s analysts search your records on a schedule and tell you what they found. Quality varies, and so does how well the findings connect to your priorities. The Atlas notes that vendors use the ThreatOps name in several senses, including a managed-detection team brand, so check what is actually being sold.
In-house build delivers fit. Because your own people write the questions, the hunts address your systems and your decisions. The price is time and a learning curve.
Lean advisory delivers answers on request. It suits organisations where leadership has occasional specific questions but no appetite for a standing programme.
Criterion two: the burden on your people
Feed-first looks cheap but quietly consumes attention. Without grading and expiry rules, an analyst spends hours triaging items of mixed quality. The Atlas’s worked example, a feed with only 18 true hits among 120 flags, shows how a subscription can cost more than it returns.
Managed hunting asks little of staff during the search but needs someone to receive findings and act. The Atlas lists “no findings owner” as the trigger for choosing it, and it is also the main way it fails: reports pile up unread because nobody is assigned to them.
In-house building asks the most. Expect a named owner, a couple of hours a week at the start, and regular review of standing questions. For a small business that may mean one person with protected time.
Lean advisory asks little routinely and a lot when a question lands.
Criterion three: what each does to the quality of evidence
This is where the option you choose shapes what you learn. Consider two kinds of clue. Indicators are fingerprints such as an address or a file signature. Behaviours are the habits of an attacker. A 2013 essay known as the Pyramid of Pain argued that denying an adversary fingerprints annoys them little, while forcing them to change habits hurts a great deal. Feed-first tends to fill the bottom of that pyramid. Hunting, whether managed or in-house, works higher up, because it tests behaviours.
The Atlas illustrates this with a February 2024 government advisory on a state-backed intrusion set, where classic indicators were scarce and the intruders’ staying power ran to years. Teams that relied only on sweeping for known items could have concluded all was well. An option that includes hunting is better placed to catch that kind of case.
Criterion four: measuring success
You need a way to compare results, and the Atlas supplies a useful set. Feed-first can be judged by feed precision. Managed hunting can be judged by how many findings led to a change. In-house building can be judged by coverage of standing questions and the share of hunts that end in something filed. Lean advisory is judged by whether decisions improved.
The Atlas steers away from vanity counts such as indicators ingested, reports published and hunts started, which flatter every option equally and tell you nothing.
Criterion five: staying in your lane
Each option can drift into work that belongs elsewhere. The Atlas keeps alert triage, live detection rules, incident response, vulnerability ranking and telemetry plumbing outside ThreatOps. Feed-first teams drift into triage. Managed hunters drift into response. In-house hunters drift into overflow for the alert queue, which the Atlas names as an anti-pattern. Whatever you pick, agree the handoff in writing: once a hunt result is confirmed, it travels to the people who author detection rules as a formal ask.
Hidden costs worth pricing in
Every option carries a cost that rarely shows in the first quote. Feed-first hides it in analyst attention and in the occasional wrongful block. Managed hunting hides it in the handoff: someone must read the reports, ask follow-up questions and turn recommendations into changes. In-house building hides it in continuity, because a programme that rests on one person stops when that person goes on leave. Lean advisory hides it in lag, since a question raised on Monday may not reach an answer until the following week.
A fair comparison therefore puts a rough number of hours beside each option, and also notes what happens when the key person is away. The cheapest plan on paper is not always the cheapest in practice.
A summary view
- Fits a tight budget with some spare time: start feed-first in observation mode, with grading and expiry, then add small hunts.
- Fits scarce staff with usable data: managed hunting, with a named person to receive findings.
- Fits teams with questions and a willing owner: in-house build, beginning with a shared folder under version control rather than a platform.
- Fits occasional strategic questions: lean advisory.
These are starting points, not endpoints. The Atlas proposes a maturity ladder, and organisations typically climb it in stages, from consuming outside warnings to running a requirements register to hunting regularly.
A note on compliance language
Several readers ask whether regulation settles the choice. In the Atlas, the US control catalogue’s hunting control is optional and appears in no baseline, while CSF 2.0 from NIST (2024) touches on risk assessment and adverse-event analysis in a way that threat work can support. In Europe, the NIS2 directive welcomes voluntary information sharing. None of these selects a model for you, and businesses with formal duties should consult their advisers.
How to decide, in an afternoon
Answer four questions on paper. Do we have ninety days of records? Does a person exist who will own findings? Do decision-makers have recurring questions? Is there any protected time? Your yes and no answers map straight onto the decision tree. Then pick one option for the next quarter, not for ever.
If you are weighing choices of a different kind, our pieces on the destinations most worth including on a Gujarat route and on the experiences that first-time visitors rate highly give the same kind of comparative guidance for itineraries.
The decision tree, the maturity ladder and the sample first-quarter plan are all set out in the Ops Atlas entry for ThreatOps.
Whichever option you pick, write down why. When you revisit the choice in three months, that note will be the most valuable page in the folder.