AI & ML
Why Trust Your Agent? Empirical Security Gains from TRiSM-Guided Agentic Workflows in Healthcare
arXiv cs.CR0 views
arXiv:2606.28666v2 Announce Type: replace Abstract: Agent-based AI has enabled the automation of tasks by exposing application tools and resources to large language models (LLMs). However, to improve scope and accuracy, agents are often given access rights that exceed those of ordinary users, introducing significant security risks and potential regulatory breaches. This paper applies the AI Trust, Risk, and Security Management (TRiSM) framework to a medical report-generation application to demonstrate how an insecure baseline workflow can be transformed into a security-conscious agentic workflow. Both designs were evaluated with five LLMs (Claude Haiku 4.5, GPT-4.1-nano, GPT-4.1-mini, GPT-5.4-mini and Gemini 2.5 Flash) across 800 report generations and 500 attack trials covering RAG poisoning, data-field injection and client-side network injection. The redesign reduced attack success from 31% to 10% for RAG poisoning and from 42% to 25% for data-field injection (McNemar p < 0.001 for both), removed network injection by construction, and raised report accuracy from 72.5% to 86.5%. In an exploratory post-hoc grouping by attack goal, success against attacks aimed outside the report task, such as data disclosure and tool abuse, fell from 21.7% to 2.5% and no patient record was disclosed under the redesign. Attacks altering the reported Covid-19 diagnosis remained effective, accounting for 32 of the 35 successful attacks against the redesign. Least-privilege architecture limits what an injection can reach, but not whether a model follows injected content within its task, so clinical outputs need verification independent of the LLM. No model resisted all three attack vectors, so model selection cannot substitute for secure workflow design.
Source:https://arxiv.org/abs/2606.28666PreviousBehavioral Integrity Verification for AI Agent SkillsNextNo Country for Old Privacy: The Evolving Challenges of Anonymity in Bitcoin
Related posts

Serving Qwen3.5-0.8B with a 0.016% weight edit: measure the loops, pin the sampling on the server
0dev.to
Design Tokens for AI: Extract a Website's Real Colours, Fonts, Shadows and Icons So an LLM Builds On Brand
0dev.to
Trying to get our Arms around AI efficiency
0Stack Overflow Blog
Why an Embedded Game Fails on Some Phones, and How to Debug It
0dev.to
Microsoft 365 vs Office 2024: The Break-Even Math
0dev.to
Master AI Evals: Build Reliable, Scalable Model Evaluation Pipelines
0dev.to