TL;DR: Most raw AI-assisted vulnerability candidates in OT security software never survive refutation, with 60 to 90 percent dropped before human review, according to Dragos. OT security software needs reproducible proof and threat models, or it will keep turning discovery volume into noisy triage.
Editorial analysis by NHI Mgmt Group, based on content published by Dragos: “Refuted by Default: Dragos’ Methodology for AI-Driven Vulnerability Detection in OT Security Software”.
Key questions
Q: Why do AI-generated vulnerability reports create more triage friction than value?
A: They create friction because models can produce fluent attack narratives without confirming target state, exploitability, or version fit.
Q: What are the signs that an AI remediation pipeline is failing?
A: Look for repeated PRs on low-value findings, conflicting severity signals, manual triage after the agent has already acted, and unresolved issues that never make it into the pipeline.
Q: What breaks when AI detection has no current threat intelligence?
A: The main failure is false confidence.
Practitioner guidance
- Build a threat model before large AI-assisted hunts Map trust boundaries, entry points, privileged operations, and existing mitigations before you let agents generate candidates, so verifiers evaluate claims against the same system context.
- Separate recall from verification Use one stage to generate broad candidate coverage and a different stage to refute claims with a bare hypothesis, so persuasive reasoning does not bias the skeptic.
- Require reproducible proof in an isolated environment Only accept findings that reproduce from clean state against pinned builds or replicas, because plausible prose is not evidence of exploitability.
Bottom line: AI-assisted vulnerability discovery in OT security software creates a trust problem as much as a detection problem.
Glossary terms: Threat Modeling, Refutation Gate, Proof-of-exploit, Validation Pipeline
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Signal quality is the real security control here, not candidate volume. AI can flood a team with plausible findings, but trust in the result depends on how aggressively the pipeline kills weak claims. In OT security software, that matters because the downstream cost of a false positive is not just wasted engineering time, but distorted risk prioritisation around systems that support critical infrastructure. The practitioner lesson is to measure verification quality, not discovery throughput.
A question worth separating out:
Q: What should OT security teams do before trusting AI-assisted vulnerability discovery?
A: They should validate the workflow against known cases and confirm that the test fixture actually reaches the code under review. If the setup cannot exercise the target path, every later result is suspect, no matter how expensive the run looked. In OT environments, that calibration step is essential because access gates and environment mismatch can invalidate an entire campaign.
👉 Read our full editorial: AI-driven vulnerability detection in OT security needs trust calibration