Yes, but only when negotiated — never by default. ServiceNow signs a BAA on an eligible enterprise contract with scoped services, and a default corporate account carries no HIPAA coverage. Its 2026 MCP server and Now Assist AI open the platform to any agent, which is where PHI in tickets can escape. HIPAA compliance is never automatic — it depends on a signed Business Associate Agreement with the vendor plus how you configure and use the tool. Below is exactly where ServiceNow stands, where PHI ends up, the AI/MCP gap most teams miss, and how to close it. Verified August 2026.
ServiceNow says it “is not a typical business associate” and will sign a BAA on an eligible enterprise contract when explicitly negotiated. The Healthcare and Life Sciences edition is recommended but not mandatory — standard Now Platform products can be configured for HIPAA workloads under a scoped, executed BAA. Engage ServiceNow’s compliance team to confirm which services and environments are HIPAA-eligible before any PHI enters an instance.
| Product / surface | PHI status |
|---|---|
| ✅ ITSM, HRSD, CSM & custom apps | When in scope of a signed, negotiated BAA — ServiceNow secures the cloud infrastructure and core platform under a shared-responsibility model |
| ❌ App Store & third-party integrations | Separate vendors with their own terms |
| ❌ Notification email, analytics & connected EHRs | External systems the BAA does not extend to |
| ❌ Any service or environment not named HIPAA-eligible | Must be explicitly scoped in the executed BAA |
Source: ServiceNow HIPAA overview. Vendor terms change — reconfirm your plan’s eligibility in writing before sending PHI.
Even teams that never intend to handle PHI accumulate it in ServiceNow. The common places it lands:
In 2026 ServiceNow made an MCP Server generally available in every Now Assist and AI-Native SKU, opening the platform to ServiceNow-built, Claude, Copilot, and custom agents, while Now Assist generative AI runs across ITSM, HRSD, and CSM. Actions route through the AI Control Tower for identity and audit — but any of these can move ticket or case content, including PHI, to a model unless governance is configured. See our ServiceNow MCP server guide.
Assume no HIPAA coverage on a default ServiceNow account: eligibility requires an eligible contract, scoped services, and a fully executed BAA in writing — and the BAA never extends to integrations, notification email, analytics, or connected EHRs. This is the leak path traditional HIPAA controls were never designed to see: the data does not breach outward, it is pulled inward by an AI agent on a legitimate, authenticated tool call. Read more on MCP data loss prevention and ServiceNow MCP server.
A BAA is a contract — it makes the vendor liable for the data it holds. It does not inspect your data, and it does not follow PHI into the AI features, integrations, or exports that sit outside its scope. Whether or not ServiceNow signs one, three gaps remain: PHI a user pastes or uploads where it should not go; PHI an AI agent pulls out over MCP; and PHI already sitting in ServiceNow that no one has found. Closing them needs data-layer DLP, not just paperwork.
Strac closes the exact gaps a ServiceNow BAA leaves open, across every surface PHI can move:
Detection alone does not stop a HIPAA violation — remediation does. Strac does not just alert; it acts the moment PHI appears:
PHI does not stay inside ServiceNow. It flows into email, chat, cloud storage, GenAI tools, and AI agents — so point fixes leave gaps. Strac is one agentless-plus-endpoint platform covering SaaS, cloud, browser, GenAI, endpoint, and MCP under a single policy and classifier, live in minutes.
| Question | Answer |
|---|---|
| Does ServiceNow sign a BAA? | Yes — eligible plans, executed BAA required |
| Is the AI / MCP layer covered? | No — outside the BAA; the main leak path |
| Can PHI be used safely? | Yes, on an eligible plan with a BAA plus data-layer controls |
| What closes the gap? | Strac MCP + Browser + Endpoint DLP and DSPM |
No tool is. You must be on an eligible plan, execute the BAA, and configure controls before PHI.
No. That is the single most common misread — the AI/MCP layer sits outside the core BAA and is the most likely place PHI leaks to a model.
Yes. ServiceNow’s official MCP server lets an agent read data on an authenticated tool call. Strac redacts PHI on that path before the agent sees it.
No. A BAA assigns liability; it does not inspect your data or follow PHI into AI, integrations, or exports. You still need data-layer DLP.
Strac layers on without slowing ServiceNow down — redacting PHI at the MCP layer, blocking it in the browser and on the endpoint, and finding PHI already stored via DSPM.
Related reading:
ServiceNow can be used with PHI on an eligible plan with a signed BAA — but the BAA stops at the core workflow, while the AI/MCP layer keeps moving PHI. Strac closes the gap on every surface — redacting PHI at the MCP layer, blocking it in the browser and on the endpoint, and finding what is already stored. Book a demo to see it on ServiceNow.
.avif){kind=icon}
.gif)
.webp)
