{"resourceId":"anthropic-claude-help-center-edr-sensor-in-cowork-vm-beta-local-only-20261102","versions":[{"version":"external-46f58d4f8de42f1727f9db1f4eb9d0b0302fd7c891e11d5687e1168b66278400","resource":{"id":"anthropic-claude-help-center-edr-sensor-in-cowork-vm-beta-local-only-20261102","title":"Anthropic admin guide: approved EDR sensors, including Palo Alto Networks, can run inside Claude Cowork's local VM in beta; cloud sessions are not covered and sensors can see prompts and files","organization":"Anthropic (Claude Help Center)","sector":"AI platform administration and endpoint security","geography":"Global product documentation","publishedAt":"Claude Help Center article, page shows \"Updated today\" when retrieved Nov. 2, 2026","publicationDate":"2026-11-02","eventDate":null,"sourceName":"Claude Help Center","sourceLabel":"Run your endpoint detection and response (EDR) sensor in Claude Cowork on Claude Desktop","sourceUrl":"https://support.claude.com/en/articles/17828685-run-your-endpoint-detection-and-response-edr-sensor-in-claude-cowork-on-claude-desktop","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["data-security","governance-procurement","developers-agents"],"finding":"Anthropic's documentation, independent of Palo Alto, says running an EDR sensor inside the Cowork VM is in beta for Team and Enterprise plans on macOS and Windows, including Claude Desktop connected to Amazon Bedrock, Google Cloud Vertex AI or Microsoft Foundry. Claude Desktop copies the vendor package into the VM at each start, checks its signature against an approved vendor key, and runs the install script. Palo Alto Networks is one of seven approved vendors. Only the VM on the user's computer is covered; cloud-run Cowork sessions cannot host a sensor. The sensor can see prompts, files and Claude responses and sends them to the EDR vendor, outside the Cowork network allowlist. Anthropic charges nothing extra during beta; package signatures expire within two years.","sledRelevance":"This is the platform operator's account of the constraints behind Palo Alto's announcement and is the more useful planning document for public-sector admins. The cloud-session gap and the fact that prompts and files flow to the EDR vendor matter for agencies subject to records, FERPA, HIPAA or CJIS rules. Interpretation: the integration is multi-vendor, so it is not a Palo Alto differentiator by itself.","evidence":"Opened and read the full Help Center article, including how it works, supported vendors, FAQ and data-handling notes.","architectureImplications":"Sensor deployment is controlled through Claude Desktop settings and vendor-signed packages; data egress from the VM bypasses the Cowork network allowlist.","governanceImplications":"Interpretation: agencies must decide whether cloud-run Cowork sessions are allowed, since they cannot be monitored this way, and must document that agent content flows to the EDR vendor.","securityPrivacyImplications":"Signature checking limits which packages run, but covers only the package file, not later sensor updates. Sensitive prompts and files become EDR telemetry.","caveats":"Beta feature documentation; describes mechanism, not detection effectiveness. Vendor documentation from Anthropic, not an independent evaluation.","streamIds":["palo-alto-networks"],"roles":{"sales":"Sales framing: Anthropic's guide shows the Cowork monitoring path is real but bounded, which helps set honest expectations with public-sector customers. The customer problem is approving desktop AI agents under privacy and records rules. A bounded engagement could be a policy and configuration review covering local-versus-cloud sessions and telemetry data handling. The document does not support claims of complete agent coverage or detection quality, and the capability is multi-vendor rather than Palo Alto-exclusive.","engineering":"Engineering framing: deployment depends on Claude Desktop settings that name the vendor and on signed packages copied into the VM at each start. Engineers should test VM start time, confirm signature handling and update behavior, and document that sensor telemetry leaves outside the Cowork allowlist. Because cloud sessions cannot host a sensor, design a separate control or policy for them. Validate supported platforms against the agency's Claude Desktop deployment, including Bedrock, Vertex or Foundry connections.","delivery":"Delivery framing: the AI platform admin and endpoint team share ownership. Proposed acceptance includes a documented setting for the approved vendor, verified sensor installs on pilot devices, a written decision on cloud-run sessions, and privacy sign-off on prompt and file telemetry. Plan for package re-signing within two years. Risks include beta changes, unmonitored cloud sessions, and sensitive data in EDR logs that fall under retention or disclosure rules."},"roleDetails":{"sales":{"customerProblem":"Agencies need to know exactly what desktop-agent monitoring covers before approving Claude Cowork.","stakeholders":["AI platform administrators","Endpoint teams","Privacy and records officers","CISOs"],"discoveryQuestions":["Will cloud-run Cowork sessions be allowed?","Who approves that prompts and files reach the EDR vendor?","Which Claude Desktop deployment paths are in use?","Who maintains re-signed packages?"],"valueHypothesis":"Interpretation: a clear policy for local monitoring and cloud-session limits may let agencies run controlled pilots.","potentialEngagement":"A desktop-agent monitoring policy and configuration review.","unsupportedClaims":["Complete coverage of all Cowork sessions","Detection effectiveness","Palo Alto exclusivity"]},"engineering":{"fit":"Relevant to any SLED organization piloting Claude Team or Enterprise with Cowork.","architectureIntegration":"Claude Desktop setting names vendor; signed package copied into VM; sensor reports to vendor cloud.","prerequisites":["Team or Enterprise plan","Approved EDR vendor","Desktop management tooling"],"constraints":["Beta feature","Local VM only","macOS and Windows only"],"security":"Signature check covers only the package file; telemetry includes prompts and files.","proofOfValue":["Verify sensor install on VM start","Confirm cloud sessions are blocked or separately governed","Review telemetry for sensitive content handling"]},"delivery":{"work":"Configure and validate EDR-in-VM for pilot devices with a cloud-session policy.","dependencies":["Claude Desktop admin access","EDR vendor package","Privacy approval"],"ownership":"AI platform admin owns settings; endpoint lead owns the sensor; privacy officer owns data approval.","skillsAdoption":"Admins learn combined Claude Desktop and EDR management.","governanceCheckpoints":["Privacy sign-off","Cloud-session decision","Re-signing calendar"],"acceptanceCriteria":["Proposed: sensor verified on 100% of pilot devices","Proposed: written cloud-session policy approved","Proposed: telemetry retention rule documented"],"risks":["Unmonitored cloud sessions","Sensitive data in EDR logs","Beta behavior changes"]}},"retrievedAt":"2026-11-03T04:06:55Z","enrichedAt":"2026-11-03T04:10:56Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Desktop administrators need to manage both Claude Desktop policy and EDR packaging.","procurementImplications":"No extra Anthropic charge during beta; EDR vendor pricing may apply.","operatingModelImplications":"Monitoring of desktop agents becomes a joint responsibility of AI platform admins and endpoint teams.","sourceVerification":{"openedUrl":"https://support.claude.com/en/articles/17828685-run-your-endpoint-detection-and-response-edr-sensor-in-claude-cowork-on-claude-desktop","referenceExcerpt":"The sensor can see activity and content inside the VM, which can include prompts, files, and Claude's responses.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}