{"resourceId":"register-claude-dispatch-thisbash-no-fix-personal-accounts-20261105","versions":[{"version":"external-19a2f2f033744f69bbd6a0d7a18fdd19b6f9ae7939bcb8aba5c07dcc147acda3","resource":{"id":"register-claude-dispatch-thisbash-no-fix-personal-accounts-20261105","title":"The Register: Anthropic has not closed the Claude Dispatch flaw and did not answer questions; researcher data show 18%-71% personal Claude accounts in six organizations","organization":"The Register (reporting on Forever Security research)","sector":"Cross-sector endpoint security","geography":"Global","publishedAt":"2026-11-05 13:00 UTC","publicationDate":"2026-11-05","eventDate":null,"sourceName":"The Register","sourceLabel":"Independent reporting","sourceUrl":"https://www.theregister.com/research/2026/11/05/anthropic-wont-fix-a-claude-dispatch-flaw-that-could-let-attackers-execute-remote-commands-across-corporate-boundaries/5307684","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["data-security","governance-procurement","developers-agents"],"finding":"Source finding: The Register reports Anthropic did not respond to its questions, including on when Dispatch would be retired, and that as of October 30 Claude's support page listed Dispatch as limited beta on some Pro, Max and Ultra plans and closed to new users. Researcher-supplied figures: in six customer organizations personal Claude accounts in corporate environments ranged from 18% to 71% (e.g., 255 of 1,233; 214 of 695; 20 of 28). Researcher claim: OpenAI's Codex does not share web and desktop sessions, avoiding this pattern (not independently tested; noted only as the researcher's comparison). Why now: published Nov 5; not previously archived; adds Anthropic's non-response and account-mix data beyond the primary write-up.","sledRelevance":"The personal-account share is the most transferable signal for public agencies and campuses: shadow Claude accounts on managed devices create the bridge the attack needs. Relevant to CIO and CISO decisions on whether to standardize on a government or enterprise Claude tenant before broad use.","evidence":"Journalistic account of an exclusive briefing; account percentages come from the security vendor's customer data (six organizations, described as a small subset) and were not independently verified. Anthropic did not comment.","architectureImplications":"Supports identity-level controls: tenant restrictions and SSO enforcement that keep personal Claude accounts off managed devices.","governanceImplications":"Agencies should track vendor disclosure status and require timely remediation communication for agent features in use.","securityPrivacyImplications":"Mixed personal and corporate account use expands the attack surface beyond the managed environment.","caveats":"Small, non-representative private-sector sample; no public-sector organizations identified; Anthropic's side absent; status may change after publication.","streamIds":["anthropic"],"roles":{"sales":"Sales framing: use the account-mix data to open a shadow-AI conversation, carefully. Many organizations may have personal Claude accounts on managed devices; offering a measurement exercise is more credible than citing the vendor's percentages as a benchmark. Pair discovery with the value of consolidating onto an enterprise or government tenant with SSO and admin controls. Avoid implying Anthropic will or will not fix the flaw, and do not present six private-sector organizations as representative of public agencies.","engineering":"Engineering framing: quantify the customer's own personal-account exposure. Use SSO logs, CASB or secure web gateway data and endpoint inventory to count personal versus tenant Claude sign-ins on managed devices, then design tenant-restriction controls. Document which Claude features each identity type can use. Treat the reported Codex session-isolation comparison as a researcher claim, and keep any comparison within this stream limited to Claude configuration rather than cross-vendor recommendations.","delivery":"Delivery framing: run a measured shadow-account baseline, then a migration. Identify personal Claude accounts on managed devices, notify users, offer enterprise seats where justified, and enforce tenant restrictions with a grace period. Track Anthropic's Dispatch status as an external dependency. Report progress with counts rather than percentages from outside sources, and keep a register of approved exceptions with business owners."},"roleDetails":{"sales":{"customerProblem":"Organizations do not know how many staff use personal Claude accounts on managed devices, the precondition for cross-device attacks.","stakeholders":["CIO","CISO","Identity and access management lead","Department AI champions"],"discoveryQuestions":["Can you distinguish personal from tenant Claude sign-ins today?","Is there a sanctioned Claude tenant staff can move to?","Who tracks vendor security disclosures for AI tools in use?"],"valueHypothesis":"Measuring and consolidating Claude accounts lowers unmanaged exposure and improves license visibility.","potentialEngagement":"Shadow AI account baseline and tenant-consolidation plan for Claude users.","unsupportedClaims":["That public agencies have 18%-71% personal accounts","That Anthropic has refused to fix the issue permanently","That another vendor's product is safer"]},"engineering":{"fit":"Useful wherever SSO, gateway or CASB telemetry can see Claude sign-ins.","architectureIntegration":"Use identity-provider and secure web gateway tenant restrictions to permit only the organization's Claude tenant on managed devices.","prerequisites":["Identity provider with Claude SSO","Gateway or CASB visibility into claude.ai traffic","Endpoint inventory"],"constraints":["Privacy and labor-relations limits on monitoring staff use","Gateway decryption policies vary by jurisdiction"],"security":"Enforce tenant restrictions, log sign-in types, and alert on personal-account use on regulated systems.","proofOfValue":["Produce a count of personal vs tenant Claude accounts on managed devices","Demonstrate a tenant-restriction policy blocking a personal sign-in in a pilot group"]},"delivery":{"work":"Baseline, notify, migrate and enforce tenant-only Claude use on managed devices.","dependencies":["Identity team","Network/gateway team","HR or labor relations for communications","License budget for enterprise seats"],"ownership":"Identity and access management, with CISO oversight.","skillsAdoption":"Plain-language notice explaining why personal accounts are being blocked and how to request a sanctioned seat.","governanceCheckpoints":["Communications reviewed with HR before enforcement","Exception approvals by data owner","Monthly status review of vendor disclosures"],"acceptanceCriteria":["Proposed: baseline count completed for all managed devices","Proposed: personal Claude sign-ins on managed devices reduced to documented exceptions within an agreed window"],"risks":["User backlash or shift to unmanaged devices","Incomplete telemetry undercounts accounts","Vendor status changes"]}},"retrievedAt":"2026-11-08T04:04:29Z","enrichedAt":"2026-11-08T04:08:54Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Migration plans should preserve access for staff who rely on Claude for accessibility or workload reasons by providing sanctioned seats.","procurementImplications":"Enterprise tenant pricing (e.g., OneGov or state agreements) can be weighed against shadow-account risk; require security notification clauses.","operatingModelImplications":"Shadow-AI measurement becomes a recurring identity operations task.","sourceVerification":{"openedUrl":"https://www.theregister.com/research/2026/11/05/anthropic-wont-fix-a-claude-dispatch-flaw-that-could-let-attackers-execute-remote-commands-across-corporate-boundaries/5307684","referenceExcerpt":"Anthropic, aware of the problem since May, has taken no action to close the hole.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}