Security & Control
Niyatna is designed around least-privilege access, approval gates, scoped tools, and proof trails. The exact controls depend on the deployment architecture approved for each company.
Security posture
Agentic work can touch documents, tools, repositories, credentials, communications, and business decisions. Niyatna treats that as an operating-system problem: every deployment should define who can ask, what agents can access, which actions need approval, and what evidence must return.
1. Access Control
- Role-scoped access: People and agents should receive only the context and tool access required for their role.
- Company-approved sources: Documents, SOPs, channels, repositories, and memory systems are connected only when approved for the deployment.
- Credential boundaries: Credentials should use least-privilege scopes, service accounts where possible, and rotation after sensitive work is complete.
2. Approval Gates
- Human review: High-risk actions such as external sends, production writes, deployments, billing actions, or broad data access can be staged for review before execution.
- Veto windows: Workflows can include a waiting period or review state before an agent completes a sensitive step.
- Policy by workflow: Approval requirements should be defined per department, tool, task type, and risk level.
3. Runtime Isolation
Where configured, agent work can run inside isolated workspaces or sandboxes with scoped file access, controlled network access, and limited credential exposure. Isolation details vary by company environment and should be documented in the deployment plan.
4. Proof and Audit Trails
Niyatna uses Proof of Intent to make agent work inspectable. Meaningful actions should return evidence such as outputs, logs, screenshots, source references, test results, review status, and a summary of what changed.
5. Third-Party Providers
Niyatna may integrate with model providers, cloud platforms, collaboration tools, code hosts, payment processors, and company systems. Each provider has its own security model and terms. Sensitive deployments should document provider choice, data retention settings, and access boundaries before going live.
Vulnerability Reporting
If you find a security issue or have concerns about an integration, write to us at security@niyatna.com. Include enough detail to reproduce or assess the issue, but do not send secrets or private credentials by email.