The Atlas take.
Noma is a useful evaluation candidate when teams need an inventory and AI security posture view across a defined agent environment, with possible extension into runtime controls. Its public material separates AI-SPM, Agent Access Control and Open Enforcement integration paths, which should shape the architecture review. Atlas would first establish what the selected connectors can actually discover and which permissions substantiate a finding. Enforcement through hooks, gateways, SDKs or APIs then needs its own test. Platform breadth is promising, but does not prove every agent version and route is covered.
02 / DEFINE THE BOUNDARY
What you are actually evaluating.
Assess discovery and AI-SPM for a defined environment. Open Enforcement integrations and AI-DR are complementary modules whose coverage must be verified separately.
Noma combines discovery, registry governance, testing, and runtime detection. This profile emphasizes the connection between posture context and an enforceable policy at an existing control point. A pilot should name the assets it discovers and the hooks or gateways where a denied action can actually be stopped.
- Also covers
- Agent tool and execution controls · Agent detection, response and recovery · Agent security testing and validation
- Deployment surface
- SaaS agents · Custom/cloud agents · Endpoint/coding agents
- Integration point
- Platform connector · API/SDK · Gateway/proxy
- Availability
- Confirm availability
Documented scope; confirm release status, supported integrations and entitlement for the selected offering.
03 / THE CONTROL PATH
Where it sits. How it works.
Atlas architecture interpretation: environment connections establish AI asset/posture context; selected registry or enforcement integrations provide a separate path for controlling supported agent access.
- 01
Selected AI environment and connectors
Identify the assets, configurations and identity context available through the chosen integration.
- 02
AI-SPM and access context
Validate relationships and findings against actual agent versions and resource permissions.
- 03
Optional enforcement path
Verify the chosen hook, gateway, SDK or API behavior and the resulting target outcome.
Enforce through existing infrastructure
Open Enforcement separates policy definition from the control point and lists agent hooks, MCP gateways, AI gateways, SDKs, and direct APIs. Choose the supported integration that covers your actual execution path.
Carry identity and posture into decisions
The product pages describe scoping rules to the human attributed to an agent and enriching runtime decisions with ownership and blast-radius context. Verify how those attributes are obtained and protected from modification.
Review connectors and policy lifecycle
The platform describes endpoint, SaaS, and homegrown coverage and shared context among modules. Obtain a versioned integration list, policy rollout procedure, and license scope for each selected environment.
04 / WHAT EARNS ITS PLACE
Strengths, with the evidence attached.
Atlas analysis of documented capabilities; availability and behavior depend on the edition and environment.
Posture has a defined product surface
The AI-SPM page describes the asset and risk model, supporting a known-environment discovery and finding-validation trial.
Control integration is explicit
Agent Access Control and Open Enforcement material identify distinct places to examine supported access policy.
Inspect the documented capability notes
Evidence reviewed: Separate AI-SPM and Agent Access Control product descriptions, plus the platform’s Open Enforcement architecture.
Agent and supply-chain inventory
AI-SPM describes discovery of agents, models, MCP servers, toolsets, and skills across endpoint, SaaS, and homegrown environments. Its posture model considers tools, data, triggers, channels, connected agents, and users together.
Risk combinations and misconfiguration
AI-SPM evaluates combinations of capabilities and exposure, including excessive agency, unsandboxed agents, embedded secrets, and unauthenticated access. Findings can feed runtime context and framework-mapped reports.
Approved, review, or blocked registry status
Agent Access Control populates a registry from discovery and assigns approval states to agents, MCP servers, and skills. Policy can be scoped by team, role, or individual identity.
Tool policies and session detection
Access Control describes user- and tool-based rules plus behavior checks after a connection is approved. The platform’s AI-DR adds session context from prompts, tool calls, data access, and actions; red teaming is a separate assessment workflow.
05 / KNOW THE COMPROMISES
The tradeoffs to take seriously.
Architectural implications and procurement questions from Atlas; these are not independently measured product failures.
Integration determines runtime coverage
A hook, gateway, SDK and API offer different mediation boundaries; validate the exact path for each required action.
Additional coverage boundaries
- Using multiple enforcement points introduces a consistency problem: confirm policy-version propagation, exception handling, and behavior when a hook or gateway loses contact with policy services.
- Discovery coverage and prevention coverage may differ. Track which assets are inventoried, which sessions are observed, and which exact operations can be denied on each surface.
- Confirm data residency, prompt and tool-content retention, required connector permissions, module pricing, and the evidence supporting claimed risk detection in your workflows.
06 / FROM PURCHASE TO PRACTICE
Make it work in your environment.
A proposed implementation sequence. Confirm supported versions, permissions, and rollback with the current documentation.
- 01
Inventory a bounded environment
List known agents, versions, tools and identities and compare them with the connector output.
- 02
Validate one risk precisely
Tie the finding to an actual permission or configuration and a resource the agent can reach.
- 03
Choose and test enforcement
Record the selected integration point, failure behavior, target-side result and reversal procedure.
07 / THE OPERATING COMMITMENT
The bill is only part of the cost.
Commercial shape
Obtain a module and integration-specific quote. Include deployment responsibilities for the chosen Open Enforcement path and separate posture, access-control and detection/response scope.
- Connected AI estate and selected modules
- Chosen enforcement integration and deployment
- Connector upkeep, finding validation and response operations
08 / COMPARE THE JOB
Put these beside it.
Alternatives worth examining for the same problem. Check each offering’s scope before treating it as a substitute.
Zenity AI Agent Security Platform
Compare posture inventory and connector depth using the same agent environments and independently selected runtime controls.
Lasso SecurityLasso AI Security Posture Management
Compare agent configuration graphs and developer remediation when the immediate job is posture assessment.
09 / MAKE THE DECISION OBSERVABLE
Earn confidence through a real evaluation.
Suggested by Atlas. Agree acceptance criteria, use synthetic fixtures in an authorized environment, and capture both useful work and failed controls.
- TEST 01
Discover a known agent and its tool relationship
Acceptance evidence: Record version and authoritative configuration evidence.
- TEST 02
Reduce a safe excessive test permission
Acceptance evidence: Verify effective resource access and updated finding state.
- TEST 03
Exercise one selected enforcement route
Acceptance evidence: Capture policy, failure handling and the independent target effect.
START WITH ONE EXERCISE
A homegrown support agent gains an additional tool during a test deployment.
Evidence to look for: Preserve the inventory change, exposure finding and selected policy outcome for the new tool.
Questions to bring to the vendor
- Which assets are found without application changes?
- Which control points enforce this policy?
- How are session findings tied to the affected agent version?
10 / SHOW THE WORK
Evidence, and what is still unknown.
What this research cannot establish
- Atlas has not independently tested discovery completeness or runtime control efficacy.
- Confirm supported connectors, integration modes and release-specific module entitlement.
Dossier research reviewed October 18, 2026. Earlier profile references are retained for traceability; products and commercial terms change.
- Noma: platform and Open Enforcement ↗Product information
- Noma: AI-SPM asset and risk model ↗Product information
- Noma: Agent Access Control registry and policy ↗Product information
KEEP BUILDING YOUR JUDGMENT