AI security infrastructure

Enterprise agentic last-mile identity and access control layer

IBM Technology — Why AI Agents Break Zero Trust at the Last Mile

A security layer that bridges AI agents with fragmented legacy enterprise systems while preserving the user's identity, intent, context, and delegation.

Problem: Legacy systems commonly authenticate connecting applications with API keys or shared credentials rather than the user initiating the request. This loses identity, intent, context, and delegation, breaks zero-trust controls, enables agents to chain tools, and exposes backend systems to rogue agents.

For: Companies deploying AI agents that must access legacy backend processes and data systems.

Identity-based security infrastructure for multi-agent AI systems

IBM Technology — Kagenti’s Approach to Multi-Agent Security for AI Agents

Deploy an open-source security layer around multi-agent systems so authorization decisions use each agent's cryptographic identity and the full delegation chain, rather than relying on bearer tokens or a statically defined request path.

Problem: A confused deputy can receive a valid credential through an agent chain and use it to access data or tools it was never authorized to reach, potentially leaving only normal-looking authorized activity in the audit trail.

For: Organizations running multi-agent AI systems in production, including systems that process patient records, financial histories, internal communications, or other protected information.

Examples

• A hospital patient-billing system: Agent A orchestrates agents B, C, and D with a bearer token for patient data; Agent D receives the token while verifying insurance, and the delegation-chain policy blocks Agent D from patient records because it is not authorized for that resource.

A guardrail tool that enforces strict test-driven development and other engineering rules for AI coding agents

Modern Software Engineering — The Most Important AI Coding Advice You Haven't Heard Yet

Use an automated validation layer to keep coding agents in a red-green-refactor cycle, prevent over-implementation, stop them from disabling lint rules, and require checks before changes are committed.

Problem: AI coding agents may skip TDD steps, over-implement solutions, disable lint rules, commit before running required checks, or write tests that do not provide sufficient confidence. Manual supervision is tedious and can allow bugs, unexpected behavior, undocumented assumptions, and unnecessary complexity.

For: Software developers and teams using AI coding agents who need confidence in agent-written code and want to supervise multiple agents without manually policing every step.

Examples

• RPG combat kata: the agent wrote a test that expected a magical sword's health to become four after use; Probity blocked an unnecessary use method that was not referenced and required a simpler implementation.

Slop Stop AI defense against automated sales outreach

My First Million — 9 drunk ideas that sound stupid (but are secretly genius)

An AI gatekeeper that responds to mass AI-generated outreach, asks the sender to do research and provide detailed follow-ups, schedules calls and requests contract revisions, consuming the spammer's time and resources instead of the recipient's.

Problem: AI makes it inexpensive to scrape contact details and send mass personalized-looking outreach, creating an increasing volume of sales spam that recipients must filter manually.

For: Business owners and professionals being overwhelmed by automated email, text and phone outreach from AI sales-development systems.

Examples

• AI sales development representatives: described as systems that scrape email addresses and contact people through email, text and calls while appearing to come from real people.

Shared AI team brain with cited, revisable business knowledge

ManuAGI - AutoGPT Tutorials — Top AI Agent Projects : Fluree AI, Pushary, Notte, OpenCode Superapp & Pulse

Connect company data sources into shared AI threads and a permissioned knowledge base that improves through corrections made during everyday work.

Problem: Teams repeatedly maintain context and correct AI answers because business knowledge is scattered and changes over time.

For: Teams across data, support, and go-to-market

Ephemeral least-privilege identity management for AI agents

IBM Technology — Can you social engineer an AI? Plus: AI worms and the nonhuman identity problem

Build identity and access-management infrastructure that provisions narrowly scoped identities and permissions for AI agents only when needed, limits them to the required action and time period, monitors their behavior, and removes their identities afterward.

Problem: Non-human identities can remain active indefinitely, escape regular monitoring, accumulate excessive privileges, and be abused without anyone noticing. Agents running under a primary or root user account can cause significant damage when they make mistakes.

For: Organizations operating AI agents, service accounts, APIs, or other non-human identities.

Examples

• OpenClaw was described as allowing anyone to run an agentic framework on a laptop; the panel warned that such agents may run under the main or superuser account and could make a large mess if they make a mistake.

Local coding-agent observability and policy monitoring

Github Awesome — GitHub Trending Weekly #42: nimbus, xy, persona, drawesome, letsseal, camelAI, OpenSlides, numbat

Numbat monitors coding agents on an endpoint without requiring a cloud service, unifying supported hooks, OTLP logs, and saved session artifacts into one event format with local CEL rules for alerts and forensic timelines.

Problem: Provides local visibility into coding-agent activity, alerts, and historical investigations without sending monitoring to a cloud service.

Examples

• Numbat: monitors coding agents locally and produces live alerts or forensic timelines.

AI-powered defensive vulnerability discovery and remediation

IBM Technology — Can you social engineer an AI? Plus: AI worms and the nonhuman identity problem

Use a self-propagating or distributed AI methodology defensively: identify vulnerabilities across devices, explain how to fix them, and potentially patch the vulnerabilities instead of exploiting them.

Problem: Traditional security teams may struggle to find vulnerabilities across changing environments quickly enough, while attackers can use similar AI techniques to discover and exploit them.

For: Organizations that need to discover and remediate vulnerabilities across their environments.

Examples

• University of Toronto researchers' self-replicating agent used an open-source LLM, spread from device to device, ran a local model, and selected different vulnerabilities and exploits for each device.

Git-based control plane for enterprise AI agents

ManuAGI - AutoGPT Tutorials — Top AI Agent Projects : Omniwork, Argos, Fin, Firecrawl & BrowserOS neo

Enterprises define agents as versioned files in their own repositories, specifying context, skills, tools, permissions, and identity so runtimes can read only what each agent is allowed to access.

Problem: Vendor-specific agent harnesses scatter context, tools, and lessons and make switching costly.

For: Enterprise organizations managing multiple AI agents.

Local browser that AI agents operate through users' logged-in accounts

ManuAGI - AutoGPT Tutorials — Top AI Agent Projects : Omniwork, Argos, Fin, Firecrawl & BrowserOS neo

Users import Chrome logins, connect agents over MCP, and delegate web tasks to isolated tabs while keeping the main browser, credentials, screenshots, and session replays local.

Problem: Chat assistants can describe actions but cannot reliably open tabs, sign in, and click through real websites.

For: People who run AI agents on the web.

AI-assisted Kubernetes remediation control plane

ManuAGI - AutoGPT Tutorials — Top Open-Source GitHub Projects : LobeHub, clawk, Jolt Physics, Clodex, mindwalk & Persome #276

A source-available infrastructure platform that connects alerts, evidence, topology, human approval, controlled remediation, recovery verification, and learning into an auditable loop.

Problem: Diagnosing and remediating infrastructure incidents while keeping execution governed, auditable, and verified against the original symptom.

For: Infrastructure and platform teams operating Kubernetes and cloud systems.

Governed enterprise environment for building AI agents, apps, and automations

ManuAGI - AutoGPT Tutorials — Top AI Agent Projects : Omniwork, Argos, Fin, Firecrawl & BrowserOS neo

Organizations provide a self-service path for teams to build AI systems while security and IT retain visibility and control over what exists, who built it, and what it can access.

Problem: Uncontrolled internal AI development can expose keys, use personal accounts, and ship ungoverned applications.

For: Security, IT, and enterprise teams.

Examples

• Alert triage, IT deployments, finance requests, and hiring are named as supported workflow examples.