Someone finally built a security database for the Claude ecosystem. It's called ClaudeSec, and Pluto Security just launched it for free. Here's the gap it fills => 53 new Claude connectors shipped in the last 30 days. Your security team reviewed zero of them. Someone on your team authorized at least one. Most enterprises adopting Claude have no process to evaluate connectors before authorization. ClaudeSec tracks 384 connectors. 103 flagged high risk. That's around 27% of the ecosystem. Every entry shows: → What capabilities the connector actually has → What tools it exposes to the model → Why it's rated risky → Source-code findings where they did the review Security guides are live for Claude Managed Agents and Cowork. Real configuration - policies, hooks, permission scopes, allow/deny rules. The Cowork guide is the one Enterprise teams need to read first. Cowork runs code, browses with real user sessions, and operates unattended. The architecture is solid, gVisor sandbox, layered network controls. But Cowork activity is excluded from Audit Logs, the Compliance API, and Data Exports. All plan tiers. Including Enterprise. Your visibility tools don't see what Cowork is doing. Claude Code and Office Agents guides ship next. The curated news feed flags CVEs and incidents as they happen. The window between a connector being compromised and detection is roughly 3 hours. The feed is built around that window. Read here: ClaudeSec: claudesec.pluto.security/ Launch blog: pluto.security/blog/introduc… Cowork teardown: pluto.security/blog/claude-c… Thanks to @pluto_security for supporting this post.