Sievant documentation

These pages are the documentation in the Sievant repository, unchanged. Each one says the commit it was copied from.

• Scan, wrap and the local UI

  The local developer path: audit MCP client configurations, route their servers through Sievant, and watch the calls. docs/local-quickstart.md walks through it.

• Policies

  What Sievant enforces and how to choose it without writing policy from scratch. sievant config show --sources prints every effective value and where it came…

• Audit and dashboard

  The audit trail every call leaves, and the embedded dashboard that shows it.

• Security-posture report

  sievant report writes a report a team can hand to a customer's security reviewer: how Sievant sits between AI agents and their MCP servers, which controls…

• Traces and audit export

  Sievant keeps its audit trail in a local store. It can also send it elsewhere: audit records to a SIEM, and one trace per request to an OpenTelemetry…

• OWASP Top 10 for LLM Applications: Sievant control mapping

  Edition 2025, mapping version 1. Source: <https://genai.owasp.org/llm-top-10/> (categories, titles and links retrieved 2026-10-18). The mapping is data,…

• Threat model

  This document grows with each milestone; M10 completes it. Each entry names the threat, what Sievant does about it, and what the operator configures.

• Commands

  Commands: Sievant documentation. Every sievant command, in one table.

• Troubleshooting

  Start with sievant doctor: it checks the configuration, the per-user state, every wrapped server and the policy file it runs under, the gateway's ports and…

• FAQ

  No. Sievant sends no telemetry and has no account or license check. It contacts only the MCP servers and backends you configure. The audit trail is a SQLite…

• Roadmap

  What is planned after the first release. There are no dates: items ship when they are done and tested, and the order may change. Each lands without breaking…