Noma Security
Also known as: Noma ARM, Noma Agent Access Control, Noma AIDR
Agent security platform that discovers agents and MCP servers into an approval registry, controls access to each tool at runtime, logs and blocks agent traffic, and red teams the customer's agents continuously.
Noma Security sells a platform to discover, govern and protect the AI agents an enterprise builds, buys and runs on its endpoints. Discovery and posture management (AI-SPM) inventory models, agents, MCP servers and skills and automatically populate a registry in which each one is approved, needs review or blocked. Agent Access Control defines which agents can use which skills and tools within an MCP server, based on runtime context and the person the agent acts for, and enforces at gateways, EDR, MDM and agent hooks at the moment a connection or action is attempted.
AI Detection and Response monitors prompts, responses, tool calls, MCP interactions and agent to agent messages, masks PII, credentials and keys, alerts, audits or blocks, and keeps a searchable audit trail of every interaction, policy decision and response action. AI Red Teaming continuously tests the customer's agents and applications with multi turn attack sequences, maps findings to the OWASP LLM Top 10, MITRE ATLAS and the NIST AI RMF as well as the EU AI Act and ISO 42001, and feeds them into runtime policies. Noma states HIPAA, SOC 2 and ISO 27001 certification.
Vendor details
Canonical URL
https://noma.security
Category
Security / SOC agent
Funding status
Independent. Investors named on the about page include Evolution, Ballistic Ventures, GLILOT Capital Partners, Databricks, Cyber Club London and SVCI.
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
Covers homegrown agents on AWS Bedrock, Azure AI Foundry and Databricks, SaaS agents such as Copilot Studio and Agentforce, and endpoint coding agents such as Claude Code, Cursor and GitHub Copilot. Policy is enforced through gateways, EDR, MDM and agent hooks. No public API reference or SDK is published.
In practice
Engineers have started running Claude Code, Cursor and Codex on their laptops with MCP servers nobody approved. Noma finds them through the EDR or MDM the company already runs, puts each one in a registry as approved, needs review or blocked, and lets security limit write and delete actions to a smaller group.
A customer facing agent built on an in house stack handles personal data. Noma watches its prompts, responses and tool calls at runtime, masks PII, credentials and keys before they reach the model, and blocks a malicious tool call when one appears.
Before an agent goes live, the security team wants to know how it breaks. Noma's red teaming runs multi turn attack sequences against it, maps the findings to the OWASP LLM Top 10, MITRE ATLAS and the EU AI Act, and feeds them into the runtime policies that protect it in production.
Sources & related URLs
Research sources
Agentic Index coverage score
7.0 / 14 capabilities · 50%
| Integrations & Tool Calling | Full |
|---|---|
|
Discovery and governance cover homegrown, SaaS and endpoint agents and MCP servers, and policy is enforced through agent hooks, AI and MCP gateways, SDKs, direct APIs and the EDR or MDM a company already runs, at the moment a connection or action is attempted. Requests are masked or blocked at runtime. On employee laptops Noma finds Claude Code, Claude Cowork, Cursor, Codex, Windsurf, Kiro, Antigravity and OpenClaw, with their MCP servers, skills, connectors and linked personal and enterprise accounts. Noma also connects to Claude's Compliance API and is offered inside the AWS Security Hub Extended console. SourceNoma Security, noma.security/platform/agentic-access-control and the endpoint agent security post on noma.security/blogread 2026-10-06 |
|
| Workflow Orchestration | Full |
|
The red teaming is done by Noma's own agents, which probe the customer's AI apps and agents and compound several techniques into one multi turn attack sequence, with escalating pressure at each step. The wider platform runs as a fixed pipeline of posture management, access control and runtime protection, with red team findings fed into the AI-DR runtime policies. The Agentic Risk Map brings discovery, posture and runtime together to show each agent's blast radius before deployment. SourceNoma Security, noma.security/products/ai-red-teaming and /solutions/ai-agent-securityread 2026-10-06 |
|
| Knowledge Grounding & RAG | Partial |
|
Discovery fills an MCP and agent registry automatically and gives each agent, MCP server and skill a status, with a profile of its toolsets, functions, data access permissions and MCP server connections, which together map the customer's AI estate. Noma says discovery finds 10 to 100 times more agents than teams expect. Noma names no knowledge store of its own for the customer's agents to draw on. SourceNoma Security, noma.security/platform/agentic-access-control, /solutions/ai-agent-security and noma.securityread 2026-10-06 |
|
| Human Oversight & Guardrails | Partial |
|
Each agent, MCP server and skill in the registry is approved, needs review or blocked, and newly found assets land there for the security team to decide what belongs. Policies are enforced when a connection or action is attempted, read access can be open to many while create, update and delete stay with a smaller group, and runtime responses run from alert and audit to masking and blocking, set by application, agent profile, risk level or policy type. Noma names no step where a person approves a single agent action before it goes through. SourceNoma Security, noma.security/platform/agentic-access-control, /platform/runtime-protection and the endpoint agent security post on noma.security/blogread 2026-10-06 |
|
| Security, Identity & Governance | Partial |
|
Attestations cover SOC 2 Type II audited by EY, ISO 27001, ISO/IEC 42001 and HIPAA, along with ISO 9001:2015. Controls for Noma's own operations include multi factor authentication, access reviews, audit logging, disk encryption, network segregation and endpoint detection and response. Noma names no SSO, role model or audit log for the customer's own users of the Noma console. SourceNoma Security, trust.noma.security and noma.securityread 2026-10-06 |
|
| Observability & Auditability | Full |
|
Runtime protection monitors prompts, responses, agent tool calls, MCP server interactions and agent to agent communications, and every interaction, policy decision and response action is logged and searchable. Automated reporting gives auditors and regulators full traceability. The Agentic Risk Map shows each agent's connections, tools, identities and knowledge sources, so the security team can see what an agent could reach. SourceNoma Security, noma.security/platform/runtime-protection and /solutions/ai-agent-securityread 2026-10-06 |
|
| Memory & State Persistence | Not documented |
|
The customer's agents get no memory from Noma. Its registry and audit trail record the AI estate and its traffic for the security team, not for an agent to read back. SourceNoma Security, noma.security/platform/runtime-protectionread 2026-10-06 |
|
| Deployment & Data Residency | Not documented |
|
Where the platform itself is hosted is not published, and Noma names no region choice, data residency option or way to run it in the customer's own environment. AWS, Azure and Databricks are platforms whose agents Noma covers, not places it runs. Noma's subprocessors include Frontegg in the US for authentication, Datadog for logging and Snowflake for analytics. SourceNoma Security, noma.security and trust.noma.securityread 2026-10-06 |
|
| Prebuilt Agents, Templates & Packs | Partial |
|
Red teaming findings map to prebuilt compliance presets for the OWASP LLM Top 10, MITRE ATLAS, the NIST AI RMF, the EU AI Act and ISO 42001, and runtime protection ships prebuilt masking for PII, credentials, API keys and sensitive business data. Beyond these presets, no named catalog or prebuilt agents are offered. Solution pages package the platform for AI asset discovery, agentic identity, MCP security, AI supply chain security and coding assistant security. SourceNoma Security, noma.security/products/ai-red-teaming, /platform/runtime-protection and noma.securityread 2026-10-06 |
|
| Triggers & Channel Coverage | Full |
|
Runtime detection fires on every prompt, response, tool call, MCP interaction and agent to agent message, and access policies are checked the moment a connection or action is attempted, with no one starting the work. Newly discovered agents, MCP servers and skills enter the registry on their own, and red teaming runs continuously. SourceNoma Security, noma.security/platform/runtime-protection and /products/ai-red-teamingread 2026-10-06 |
|
| Model Flexibility & Routing | Not documented |
|
Noma secures traffic to the customer's models and offers no model choice or routing of its own. Its detection of prompt injection and policy violations runs on proprietary AI models trained for security analysis. SourceNoma Security, noma.security/platform/runtime-protectionread 2026-10-06 |
|
| APIs, SDKs & MCP Extensibility | Not documented |
|
Noma publishes no API reference, SDK or MCP server for building on its platform, and no docs site. It says policies can be enforced through SDKs and direct APIs as well as hooks and gateways, but publishes a reference for neither, and its MCP features govern the customer's own MCP servers. SourceNoma Security, noma.security and the endpoint agent security post on noma.security/blogread 2026-10-06 |
|
| Testing, Debugging & Optimization | Full |
|
AI Red Teaming continuously tests the customer's AI agents and applications, whether on endpoints, in SaaS or built in house, with adaptive multi turn attack sequences covering prompt injection, jailbreaks, data leakage, denial of wallet and harmful content generation. Findings map to compliance presets with audit ready reporting and feed into the AI-DR runtime policies, so each weakness found hardens production protection. SourceNoma Security, noma.security/products/ai-red-teamingread 2026-10-06 |
|
| Browser & Computer Use | Not documented |
|
Noma names no browser or computer control by its own agents. The platform governs other agents, including coding and productivity agents on employee laptops found through the EDR or MDM a company already runs. SourceNoma Security, noma.security and the endpoint agent security post on noma.security/blogread 2026-10-06 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Product updates
Noma connected its AI-DR runtime product to NVIDIA OpenShell through the supervisor middleware, so each request an agent makes inside an OpenShell sandbox, including prompts, tool calls and MCP traffic, passes to Noma for inspection after OpenShell's own policy check. When a Noma policy triggers it can block the action, steer the agent, mask sensitive data or alert a person, and the verdict is enforced outside the agent's process.
Bears on: Human approval / guardrails
View sourceNoma now finds and governs the AI agents employees run on their laptops, using the EDR or MDM a company already has to discover coding and productivity agents, MCP servers, skills and connected accounts. Each lands in a registry as approved, under review or blocked, with policies tied to users and groups down to individual tools and actions.
Bears on: Security / enterprise
View sourceNoma Security is available through the AWS Security Hub Extended console as its AI security partner, so enterprises can turn on AI security monitoring from within AWS.
Bears on: Integrations
View sourcePricing
Contact sales; no prices published. Demo on request.
Inference, not stated by the vendor: agents secured, MCP servers covered, integrations and deployment scope.
What is public
The four products are public; no plans, prices or billing basis are disclosed.
Variable cost rationale
Inference, not stated by the vendor: cost likely grows with the number of agents and MCP servers governed.
Sales call required
Yes, required for paid access
Free / trial
Not published
Related vendors
- 7AI — Agentic SOC from the Cybereason founders: domain specialized agents…
- Abnormal AI — Behavioral AI email security with three named autonomous agents: a…
- AirMDR — AI native MDR whose AI analyst investigates every alert and writes…
- Airrived — Agentic OS that unifies SOC, GRC, IAM, vulnerability management, IT,…
- Andesite — Human-AI SOC platform where customers build their own agents and…
- Anvilogic — Agentic security operations platform that works on top of existing…
Alternatives to Noma Security
The closest documented capability profiles to Noma Security among security and SOC agents tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.
- Terra Security6.5 / 14A lighter documented profile than Noma Security
- Lasso Security7.0 / 14Adds documented APIs, SDKs & MCP ExtensibilityNoma Security vs Lasso Security →
- Repello AI8.0 / 14Adds documented APIs, SDKs & MCP Extensibility
- Pillar Security7.5 / 14Adds documented Deployment & Data ResidencyNoma Security vs Pillar Security →
- Straiker8.5 / 14Adds documented Deployment & Data Residency and APIs, SDKs & MCP ExtensibilityNoma Security vs Straiker →
- Equixly6.0 / 14Adds documented APIs, SDKs & MCP Extensibility
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded