NeduraTalk to us ↗

CONTROL & GOVERNANCE

Set the boundaries
for agent work.

Operate Nedura in your environment and configure tool access and approval behavior. Choose Nedura Gov when the Sevengate governance layer is required.

01 / THE BASELINE

Control starts with configuration.

Tool availability

Enable toolsets by platform and filter tools exposed by MCP servers. Make the available tool surface fit the task.

Tool configuration ↗

Profile separation

Keep configuration, credentials, memory, sessions, skills, and gateway state in independent profiles.

Profile boundaries ↗

Command approvals

Configure how dangerous command patterns are handled. The security guide describes approval modes and unattended behavior.

Approval modes ↗

02 / DATA FLOW

Deployment location and connections are separate choices.

Nedura runs in your cloud tenant or on your servers. Model calls use configured providers, and connected tools may communicate with external services.

A customer-operated runtime does not by itself make every call private or offline. Review provider endpoints, tool credentials, messaging channels, and execution backends together.

The security documentation covers command approvals, messaging authorization, and isolation options. Review current behavior for the setup you choose.

Read the security guide ↗

03 / NEDURA GOV

Policy-controlled actions.
Traceable decisions.

Sevengate

Sevengate is built into Nedura Gov.

For defense, federal, and regulated organizations, Nedura Gov adds the Sevengate governance layer to the Nedura foundation.

Nedura-branded bot connecting through a Sevengate gateway to OpenAI, Gemini, and Claude
  1. Evaluate policy

    Actions begin denied and proceed when policy allows them.

  2. Bring a person into the decision

    Human approval can be required for sensitive actions.

  3. Retain the decision record

    Tamper-evident, hash-chained audit decisions support traceability.

  4. Approve where your team works

    Approve or deny in the terminal, in chat, or in Microsoft Teams with Microsoft Entra identity. A request nobody answers expires and is recorded as not approved.

  5. Approved providers and models

    An installation policy lists the model providers, and optionally the models, the agent may use. Anything else is refused.

  6. Verifiable records

    Verify the audit hash chain on demand and anchor it to a separate log so truncation is detectable.

Discuss governance requirements ↗

04 / PLAN THE ROLLOUT

Questions to resolve with your team.

  • Which models, tool servers, and messaging platforms are approved?
  • Which tasks need human review before actions proceed?
  • How should profiles and credentials be separated?
  • What should unattended workflows do when an approval is required?
  • Does the deployment require Nedura Gov and Sevengate?

Discuss your environment and requirements with support. These capability descriptions do not assert a compliance certification.