[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fV0YoMshGhJ15sVbrOEKwO1MBLhUzsUailwBkWbDpGso":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":19,"status":27,"created_at":28,"published_at":29,"article":30,"tags":34,"podcasts":47,"controls":48},"61ac3c82-ea08-423b-ae2c-1355dbde7f28","anthropic-adds-edr-visibility-into-ai-agent-activity-inside-claude-cowork-vms","f6c73e9c-77ec-4981-bb94-b64a6d1123ad","Anthropic Adds EDR Visibility Into AI Agent Activity Inside Claude Cowork VMs","The launch of EDR sensor support in Claude Cowork highlights a previously overlooked security blind spot: AI agents executing shell commands and code inside local virtual machines were entirely invisible to host-level security tooling. Without this visibility, security teams had no way to detect malicious, anomalous, or policy-violating behavior initiated by AI agents on behalf of users. This matters because AI agents are increasingly granted broad system-level permissions, making them a high-value target for misuse or compromise. The absence of monitoring inside sandboxed AI execution environments represents a systemic gap as agentic AI use expands across enterprises.","**Immediate actions:**\n- Enable EDR sensor integration within Claude Cowork on all Team and Enterprise plan deployments for macOS and Windows immediately.\n- Audit current AI agent deployments to identify any execution environments that lack endpoint-level monitoring coverage.\n\n**Long-term improvements:**\n- Establish a formal policy requiring that all AI agent runtime environments support EDR or equivalent telemetry before being approved for enterprise use.\n- Maintain a living inventory of all AI tools and the system permissions they are granted, reviewing it on a quarterly basis.\n- Work with AI vendors to ensure security visibility is a contractual and technical requirement in procurement processes.\n\n**Detection measures:**\n- Configure EDR alerts specifically for unusual shell commands or code execution patterns originating from AI agent processes.\n- Route AI agent execution telemetry into your SIEM for correlation with broader threat detection rules and anomaly baselines.",[12,13,14,15,16,17,18],"CIS Control 10: Malware Defenses","CIS Control 13: Network Monitoring and Defense","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities","MITRE ATT&CK T1059: Command and Scripting Interpreter","NIS2 Article 21(2)(b)",{"NIS2 Article 21(2)(b)":20,"CIS Control 10: Malware Defenses":21,"NIST SP 800-53 SI-2: Flaw Remediation":22,"CIS Control 13: Network Monitoring and Defense":23,"MITRE ATT&CK T1059: Command and Scripting Interpreter":24,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":25,"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control":26},"NIS2 requires entities to implement appropriate technical measures for incident handling and monitoring; the prior lack of EDR visibility inside Claude Cowork VMs would have prevented timely detection of security incidents involving AI agent activity, violating this obligation.","AI agent activity inside VMs was invisible to host security software; deploying EDR sensors inside the execution environment directly fulfills the requirement to deploy and maintain anti-malware and behavioral monitoring on all active computing surfaces.","The gap in EDR coverage inside AI agent VMs represents a known architectural flaw; SI-2 requires organizations to identify and correct information system flaws, which applies here to closing monitoring gaps before they can be exploited.","Shell commands and code execution by AI agents constitute a form of lateral or internal activity that must be captured and analyzed; CIS Control 13 requires continuous monitoring of network and endpoint behavior to detect threats, including those originating from trusted but potentially abused processes.","AI agents executing shell commands inside local VMs map directly to this technique; without EDR sensors inside the VM, defenders have no telemetry to detect or respond to command execution abuse by a compromised or manipulated AI agent.","The absence of monitoring inside sandboxed AI environments is itself a technical vulnerability; A.8.8 requires organizations to identify and remediate technical vulnerabilities in a timely manner, including architectural gaps in security tooling coverage.","AI agents executing commands on behalf of users must have their actions attributable and auditable; PR.AA requires that identities and their associated activities be managed and monitored, which is impossible without EDR visibility inside agent runtime environments.","published","2026-11-03T05:20:22.85483+00:00","2026-11-03T05:20:22.821+00:00",{"id":7,"url":31,"slug":32,"title":33},"https:\u002F\u002Fcybersecuritynews.com\u002Fanthropic-enables-edr-monitoring\u002F","anthropic-enables-edr-monitoring-in-claude-cowork-to-detect-hidden-ai-agent-acti-6b96f6","Anthropic Enables EDR Monitoring in Claude Cowork to Detect Hidden AI Agent Activity",[35,41],{"id":36,"name":37,"slug":38,"description":39,"color":40},"1732a005-556e-411c-a9db-5edec3058571","Logging & Monitoring","logging-monitoring","Missing logs, no alerting, blind spots","#a855f7",{"id":42,"name":43,"slug":44,"description":45,"color":46},"859cf0ad-a7e9-42bb-a75d-bac6511fa5d5","Configuration Management","configuration-management","Misconfigs, default credentials, exposed services","#eab308",[],[49,53],{"slug":50,"name":51,"problem":52},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",{"slug":54,"name":55,"problem":56},"security-monitoring-siem","Security monitoring (SIEM)","Logs from everywhere end up in one place, with alerts that someone actually sees."]