Noma Security vs Zenity (2026)

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

Zenity covers Microsoft's Copilot Studio, Microsoft 365 Copilot, Power Platform and Azure AI Foundry, Salesforce Agentforce, AWS Bedrock and Google Vertex AI, ChatGPT Enterprise and Claude Enterprise, and ServiceNow. It also covers GitHub Copilot, OpenAI Codex, Microsoft Foundry and Agent 365. Custom agents report through OpenTelemetry, and Zenity integrates with CrowdStrike Falcon SIEM and ServiceNow.

Sourcezenity.io/platformread 2026-09-28

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

Surface, Enforce and Protect run as a fixed product pipeline, and one Guardian Agent is live, Blue Agent, a triage assistant that works in several steps. There is no coordination among several agents and no flow the customer configures. The Clarity and Correlation agents from earlier descriptions no longer appear.

Sourcezenity.io/blog/august-2026-product-updatesread 2026-09-28

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

Boundaries check every agent action in real time as it happens, in prevention or detection mode, and Blue Agent triages findings as they arrive, so events start the work with no one launching it.

Sourcezenity.io/platform/runtime-boundariesread 2026-09-28

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

A live inventory covers agents across SaaS, custom and endpoint deployments, with identity, data and behavior signals correlated into attack paths. There is no retrieval layer that an agent queries, and Blue Agent gathers context for each finding.

Sourcezenity.io/platformread 2026-09-28

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

Blue Agent's triage guidelines are generated at onboarding and persist for the organization, and the agent suggests revisions when it sees a need. That state persists and the agent maintains it, and Zenity says nothing more about its scope or lifetime.

Sourcezenity.io/blog/august-2026-product-updatesread 2026-09-28

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

Blue Agent runs in suggest mode, so nothing it proposes is applied without a person's approval. On the customer's agents, Boundaries let an action through, block it or shut the agent down.

Sourcezenity.io/blog/august-2026-product-updatesread 2026-09-28

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

Attestations on the trust center cover SOC 2 Type II, ISO 27001 and ISO 27701, with full reports on request. Account setup offers SSO through Azure AD and Okta or generic SAML and OIDC, along with an IP allowlist and encryption keys the customer manages. FedRAMP is in process, not authorized.

Sourcedocs.zenity.io/ssoread 2026-09-28

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

The customer's agents are analyzed in context: execution paths, tool invocations and memory updates, along with decision flows, RAG queries and file access. Each agent has an activity record, and spans from custom agents come in through OpenTelemetry, so every tool call the customer's agents make is on record.

Sourcezenity.io/platform/ai-observabilityread 2026-09-28

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

Commercial customers get SaaS on AWS. A federal deployment inside Knox Systems' platform is in process for FedRAMP, a second environment not yet authorized. There is no region list or option to host in the customer's own environment. Encryption keys the customer manages protect data but do not set where it lives, and the agent platforms Zenity covers are not where it is hosted.

Sourcezenity.io/company-overview/newsroom/company-news/zenity-achieves-fedramp-in-process-status-for-ai-agent-securityread 2026-09-28

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

A library of prebuilt Boundaries rules and a snippet library of prebuilt examples ship without a named catalog, and one Guardian Agent, Blue Agent, is live. There is no named set of prebuilt agents.

Sourcezenity.io/platform/runtime-boundariesread 2026-09-28

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

No model provider, choice or routing is named for Blue Agent or the platform's analysis. Zenity covers agents built on many models, which does not give its customers a choice of model for Zenity itself.

Sourcezenity.io/platformread 2026-09-28

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

The Evaluate API lets customers' custom agents call Zenity for inline enforcement decisions on their actions, alongside OpenTelemetry ingestion. It has a public documentation page, Custom Agents: Evaluate API, but the page shows no reference content.

Sourcedocs.zenity.io/integration/custom-agents-evaluate-apiread 2026-09-28

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

Before anything goes live, the customer's agents are checked for configuration and permissions against policy, and attack paths that correlated signals show to be reachable are scored from 0 to 100. That validates configuration. There is no red teaming or scored test run against the customer's agents.

Sourcezenity.io/platform/ai-exposure-managementread 2026-09-28

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

Zenity governs other agents, browser and endpoint agents among them, and does not drive an interface itself or use a browser or computer.

Sourcezenity.io/platformread 2026-09-28