IT AI Index
Index Vendors › Field Effect MDR · September 2026 Edition
Field Effect · 1 category · Named, not ranked

Field Effect MDR

12Judge labels
0First choices
0Negative labels
7 of 12Models named it
1Category
September 2026 Edition. Every number here is derived from the raw labels under vendor table vv2026-09.2, every buyer segment counted.
Standing
3 labels, too few to rank
A product needs 10 labels in a category before a share or quadrant is stated. Field Effect MDR was named 3 times in MDR, where Arctic Wolf Managed Detection and Response led with 39%. The labels and the evidence are below, counted exactly.
By buyer segmentRead the same way at every buyer size.
In mdr · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named Field Effect MDR for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.
CategoryFunctionShareRankNegative rateLabelsQuadrant
Managed detection and responseSecurity operations0%17 of 450%3under 10 labels · led by Arctic Wolf Managed Detection and Response at 39%

Movement

This is the first edition on this tier, so no move can be computed for Field Effect MDR yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated Field Effect MDR across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.
ModelFirst choiceAlternativeMentionNegativeLabels
Claude Haiku 4.500101
GPT-5.4 mini00000
Gemini 3.5 Flash00000
Perplexity Sonar00000
Grok 4.1 Fast00000
Mistral Small00000
DeepSeek V4 Flash00000
Llama 4 Maverick02002
Qwen 3.7 Flash00000
Kimi K200000
GLM 4.7 FlashX00000
MiniMax M2.500000

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.
FramingLabels by classFirst choices
Direct3 labelsNone
Paraphrase1 labelNone
Comparative6 labelsNone
Budget-constrained1 labelNone
Scale-constrained0 labelsNone
Negative1 labelNone
First choiceAlternativeMentionNegative12 labels in all, every segment counted; 0 of the 0 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

“Another good option for mid-market teams that want SIEM depth and unlimited incident response.” Llama 4 Maverick · MDR · paraphrase prompt · alternative
“Huntress, and Field Effect” Llama 4 Maverick · MDR · direct prompt · alternative

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

No model argued against it.

Named alongside

The products named in the same answers as Field Effect MDR, over the 12 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Field Effect MDR was named but was not.
ProductSame answerTook the first choice insteadHead to head
Huntress Managed EDR12 of 1210Not in the top three
Sophos MDR10 of 120Not in the top three
Arctic Wolf Managed Detection and Response9 of 121Not in the top three
Blackpoint Cyber7 of 120Not in the top three
CrowdStrike Falcon Complete6 of 120Not in the top three
Red Canary4 of 120Not in the top three
SentinelOne Singularity MDR3 of 121Not in the top three
Expel3 of 120Not in the top three
Rapid7 MDR3 of 120Not in the top three
Ontinue2 of 120Not in the top three
A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named Field Effect MDR. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 9 of the 12 answers that named Field Effect MDR and are not a share of its labels.

Domains cited

gbhackers.com8
consilien.com7
cyberpress.org6
cybersecuritynews.com6
smbsecureguide.com6
learn.g2.com5
mdrcost.com4
intezer.com3
mdrproviders.io3
bellatorcyber.com2

Fifty of the fifty domain citations in answers naming Field Effect MDR came from somebody else's page.

Pages cited

Pages are listed as the models cited them.

Names read as Field Effect MDR

What the judge wrote, as written, with how often. The vendor table decides that these count as Field Effect MDR; a claim can dispute any of them.
Field Effect 2
Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Field Effect MDR's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Field Effect MDR, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at fieldeffect.com is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.

Subscribe to the pack