GOVERNATLAS / PRODUCT DOSSIER

Noma Security

Noma lists AI posture management, agent access control, runtime detection and response, and AI red teaming.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Evaluate how posture findings, agent access controls and runtime responses connect. A discovered agent identity becomes actionable when its permissions, tools and owner are understood, and when a response can be tied to the request or configuration that caused concern.

What this record does not establish

The listed platform functions do not establish discovery completeness, least-privilege enforcement across every tool or measured resistance to adversarial behavior.

1 current source · 1 published assertion
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗
A

A test worth running

Register a sandbox agent with a permitted tool and a deliberately restricted action. Inspect discovery and posture records, attempt the restricted action within the authorized test and follow the resulting finding or intervention into an analyst workflow. Change the agent's permissions and inspect the historical comparison.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. Distinguish an inventory observation, an access policy and an enforced tool restriction in the demonstration.
  2. Link a runtime response to the agent identity, policy version and accountable operator.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

01
vendor asserted

Noma lists AI posture management, agent access control, runtime detection and response, and AI red teaming. Scope: vendor documentation only; edition and availability boundaries require confirmation.

Source, dates & preserved provenanceNoma Security — official product or documentation page ↗

Authority: vendor owned
Observed 2026-10-14 · Reviewed 2026-10-15 · current until 2026-11-13

Artifact SHA-256: e5b386714d4ab95b910be8100f12fb2bb34510ed2052bde6b965020285d57082

The hash identifies the preserved capture. The live source may have changed.

Source register

Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

01

Which integrations discover assets and which enforce agent actions at runtime?

02

What deployment, retention and access-control evidence supports the intended use?

03

What underlying assurance documents are available, and which claims remain unverified?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

COMPLIANCE / CLAIMS, SCOPE & GAPS

Start with the requirement.
Inspect the support.

Prepare your vendor review ↗

These labels describe this dossier’s current evidence coverage. A published mention may be a framework mapping, a qualified assertion or a limitation; it is not a compliance finding.

For HIPAA-regulated use, request service-specific BAA eligibility, processing scope and responsibility details. Missing evidence here does not establish noncompliance. Payment cannot alter these evidence labels.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗