Shadow AI Is Costing Healthtech Vendors Deals | Verax
NEWS
Verax AI Risk Assessment is live. See what's exposed
Use cases
Resources
Company
Book a demoStart Free Assessment
blog<br>Healthtech CISOs: Shadow AI Is About to Cost You Deals<br>Author:<br>Leo Feinberg, CEO & Co-founder
10<br>min -
June 3, 2026
If a hospital or a pharmacy customer about to close or renew sent you an AI security audit tomorrow, how confident are you in your answers? And if the deal stalls, are you prepared to explain this to your CEO?<br>Hospitals have moved past the basics. AI policies and training completion rates aren't going to cover you anymore. They're auditing how well you are protecting PHI from leaking into AI tools and this includes having visibility into things you probably haven't gotten to yet: which employees are using personal ChatGPT accounts for work, who's connected an AI tool to your customer data, which of your SaaS vendors quietly turned on embedded AI last quarter, and whether you can produce evidence for any of it on request.<br>TLDR: What healthtech CISOs need to know about shadow AI<br>To qualify for a BAA, your healthcare customers are quickly expecting more concrete answers around how your entire org uses AI. With shadow AI usage that ranges from using non-enterprise tiers to using any SaaS tool with AI functionality, you need to move past the idea that procuring enterprise licenses for a couple of AI tools will suffice. What's now required is AI visibility and policy enforcement across all of your workforce's devices (including personal devices) and interfaces, understanding not only what tools they use, but what plans, models, connectors, access, and prompts are being used. All of this needs to happen in realtime, in order to catch and prevent any data leakage.<br>Why you need to pay attention to shadow AI today (or yesterday, really)<br>The shadow AI conversation in every other industry is challenging, but the unique mix of increased regulation and tech affinity amplifies each risk in ways you may not have realized.<br>Your engineers are the highest-risk users. Verizon's 2026 DBIR analyzed over 850,000 AI-related data loss events. The largest category of data leaked, by a wide margin, was source code. For healthtech that's a double exposure. Your codebase touches PHI structures: FHIR mappings, EHR integration logic, claims processing, patient-matching algorithms. An engineer pasting a customer screenshot into Copilot's free tier or asking Claude to find a bug based on a log file can simultaneously leak the IP that took years to build, the schemas that show how PHI flows through your system, and real patient data sitting in a debug log.<br>Training isn’t the issue here. Your engineers aren't pasting PHI into ChatGPT because they're reckless. They're doing it because their job is hard and AI makes it easier. Until you give them something faster that's also approved for PHI, they'll keep finding their own way.<br>Coding assistants live inside the IDE. Copilot, Cursor, Windsurf, Codeium. They watch every keystroke. They may be using Cursor safely, but an added tool to test code for bugs may be a personal plan they added themselves without anyone knowing. Not because they’re reckless, but because otherwise, they will be falling behind.<br>The wrong-tier trap is everywhere. ChatGPT Free, Plus, Pro, and Team are not BAA-eligible. OpenAI says so in all caps in its own terms. Claude, Gemini, and Copilot all have the same split: consumer tiers can't legally process PHI. Most of your employees do not know this - and this distinction exists for every tool, across desktop mobile, browser, and basically every SaaS tool that they’re using. Even free tier SaaS tools that seem harmless can be leveraging AI in such a way that PII is being exposed.<br>The AI you didn't buy is the hardest to govern. Notion AI summarizes documents. Slack AI indexes channels. Zoom AI Companion transcribes calls. Salesforce Einstein writes follow-ups. Atlassian Intelligence searches Jira tickets. These features were turned on by default, governed by terms that don't match your BAAs, adopted before security got a chance to review them. Your AUP almost certainly doesn't name the AI now living inside dozens of other tools you already pay for.<br>Hospital CISOs aren't just asking anymore. HITRUST released a formal AI Security Assessment with Certification in November 2024 and The Health Sector Coordinating Council published a third-party AI risk guide in 2025. AI questions are now in vendor security questionnaires, RFPs, and annual reviews. The changes and demands are only accelerating and your customers are expecting you to not only be on top of it, but ahead of the curve.<br>What to actually do about shadow AI in healthtech<br>Forget banning AI. Samsung tried it back in 2023, before AI usage truly boomed, and it was an utter failure. On the other hand, healthcare organizations that provided sanctioned alternatives saw an 89% drop in unauthorized AI use. So the answer is governance...