Pluto Security

Everyone is a builder now. Security needs visibility and control - without slowing innovation.

[Pluto Security @pluto_security]

https://t.co/IEbgTyhQX0

[Pluto Security @pluto_security]

Last time, we published ClaudeSec - our security-first hub for the Claude ecosystem.

Now, CopilotSec is officially LIVE.
A new community knowledge hub for security of the Microsoft AI ecosystem, powered by Pluto.
Ever wanted a single place to understand what Microsoft AI connectors actually do?
Wondered which ones are high-risk?
Trying to figure out how to securely deploy Copilot Studio, agents, MCP servers, or AI workflows in production?
That’s exactly why we built CopilotSec.
Inside you’ll find:
1,718 Microsoft ecosystem connectors mapped by capability and riskSecurity guides for Copilot Studio and Microsoft AI deploymentsCurated security updates and findings that actually matter to security teams
Built for practitioners. Open to everyone.

Give it a try and let us know what you think!
Link in the first comment 👇

[Tech with Mak @techNmak]

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: https://t.co/EcB9rT1wWA
Launch blog: https://t.co/JRsZ3ibRJn
Cowork teardown: https://t.co/fuzaUJtoQW

Thanks to @pluto_security for supporting this post.

[Pluto Security @pluto_security]

@eugeneychan Exactly. Deployed means running. Governed means you actually know what it's doing!

[Pluto Security @pluto_security]

The average enterprise now runs 37 deployed AI agents. More than half have zero security oversight or logging. You can't govern what you can't see.

[Pluto Security @pluto_security]

@sama @VampireGurlAI Big move. Most enterprises are still figuring out how to govern the AI they already have. Now they need to secure what's securing them too.

[Pluto Security @pluto_security]

@AnthropicAI Opening up bug bounties is the right call. Finding the vulnerability is step one. The harder question is what happens in production before anyone finds it.

[Pluto Security @pluto_security]

@0xcorte That's the goal. Getting there in real time is where most teams get stuck.

[Pluto Security @pluto_security]

Your AI agent just connected to Salesforce, GitHub, and Slack. It has more access than most of your employees. Does your security team know that?

[Pluto Security @pluto_security]

@satyanadella Agent Mode default across Word, Excel, and PowerPoint. Every enterprise just got a much bigger AI footprint to secure.

[Pluto Security @pluto_security]

@AnthropicAI Models that can self-report misalignment is a big step. The harder question is whether enterprises can act on that signal in real time.

[Pluto Security @pluto_security]

https://t.co/shpgP5gGK5

[Pluto Security @pluto_security]

ClaudeSec is officially LIVE!
Meet the new security-first hub for the Claude ecosystem, powered by @pluto_security.

❓Always yearned for a unified search of all existing extensions?
❓Ever wondered what ones are flagged as high-risk?
❓Dreaming of knowing how to deploy safely with Claude?

All of this (and more) is now waiting for you on our new planet.

Give it a go and let us know in the comments what you thought!

Link in the first comment.

[Pluto Security @pluto_security]

@claudeai Agents that learn from every session are powerful. They also accumulate context that most security teams have zero visibility into.

[Pluto Security @pluto_security]

@omarsar0 Self-evolving agents are impressive. They're also the hardest thing to put guardrails on.

[Pluto Security @pluto_security]

@Baron_VonSnatch That's what makes this pattern so dangerous. The software is easy to run. The blast radius is not easy to see.

[Pluto Security @pluto_security]

Our research team disclosed CVE-2026-33032, a critical CVSS 9.8 vulnerability in nginx-ui that exposed over 500K users to full server takeover through a single unauthenticated request. No credentials. No exploit chain. Actively exploited in the wild.

The root cause: MCP endpoints that inherit an application's full capabilities but skip its security controls entirely.

The pattern is clear - and it's only getting more common as agentic workflows connect deeper into enterprise workspace infrastructure.

Most security teams have no visibility into what MCP servers are running in their environment, no inventory of the endpoints they're exposing, and no way to enforce it.

Full breakdown → https://t.co/Pp6gMQ9GhV
As covered by The Hacker News → https://t.co/6lcYZiiy7V

[Pluto Security @pluto_security]

@wkeything Good point. Action monitoring matters. Visibility into what the agent does after it's in is exactly the gap we're focused on.

[Pluto Security @pluto_security]

@OpenAI More AI capability for defenders is great. The question is who's governing what that AI can access inside your environment while it's defending.

[Pluto Security @pluto_security]

Everyone is racing to deploy AI agents. Nobody is asking who gave them permission to be there.