Giskard's tests: 94% of scanning-tool alerts are noise
Start here
Giskard tested four LLM security scanners—Garak, Promptfoo, DeepTeam and PyRIT—on Aria, a bank payment agent running on GPT-5.4 mini; of 4,101 alerts, 94% required no fix, and of 39 confirmed vulnerabilities only 7 were detected, and of 9 severe vulnerabilities only 4 were detected. The main cause of false positives is that the scanners' graders do not understand the agent's purpose and judge normal behaviors such as asking about the payee as failures; another 3 vulnerabilities were triggered but judged PASS by the scanners' own graders.
Generated by AI from reports · Updated 8 days ago
Attention and developments
Attention, hourly
Now 35, 0% in 24 hours·Peak 35 (Nov 6 03:00)
Related research
Papers whose work the reports mention
- The reports mention HarmBenchHarmBench: A Standardized Evaluation Framework for Automated Red Teaming and Robust RefusalScanning is not the same as AI red teaming: 94% of alerts are noise
arXiv · 2024-02-06 · Deep reading
Progress timeline
- GiskardScanning is not the same as AI red teaming: 94% of alerts are noise
Giskard used a bank payment Agent Aria running on GPT-5.4 mini to test four LLM security scanners: Garak, Promptfoo, DeepTeam, and PyRIT. Of 4,101 alerts, 94% required no fix; of 39 confirmed vulnerabilities, only 7 were detected, and of 9 severe vulnerabilities, only 4 were detected. The main cause of false positives was that the scanners' graders did not understand the Agent's purpose and judged normal behaviors such as asking about the payee as failures; in addition, 3 vulnerabilities were triggered but judged PASS by the scanners' own graders. Severe flaws were hidden in tool calls rather than text replies; the vulnerability of paying to a forged merchant ID was not found in any of 15,563 tests. Among 28 risk scenarios, the four scanners together implemented only 10 and never attempted 6, even though all claimed to cover the OWASP Top 10. The article suggests keeping the scanners and adding a threat model, using frameworks such as EBIOS Risk Manager and STRIDE to list risk scenarios, grading accordingly, counting coverage, and filling red-team gaps.
Related discussion
Attention trend
New sources per day
- Nov 4: 1 new sources (1 outlets, 0 accounts)
- Nov 5: 0 new sources (0 outlets, 0 accounts)
- Nov 6: 0 new sources (0 outlets, 0 accounts)
- Nov 7: 0 new sources (0 outlets, 0 accounts)
- Nov 8: 0 new sources (0 outlets, 0 accounts)
- Nov 9: 0 new sources (0 outlets, 0 accounts)
- Nov 10: 0 new sources (0 outlets, 0 accounts)
- Nov 11: 0 new sources (0 outlets, 0 accounts)
- Nov 12: 0 new sources (0 outlets, 0 accounts)
- Nov 13: 0 new sources (0 outlets, 0 accounts)