Security & operations · v0.2.1
Local-first, and quiet by design.
DSI runs on your infrastructure. The primary path makes no model-provider call, keeps no state by default, and sends nothing home. This page describes the product's posture — it is not an independent third-party security audit.
Architecture posture
Local-first
You own the model call; DSI audits a supplied prompt/response pair. No external service is required to run it.
Stateless by default
No database is created and no audit history is retained unless you deliberately configure persistence. Evidence bundles are portable artefacts you choose to keep.
No telemetry
No usage reporting, no remote logging, no hidden ingestion. DSI phones nothing home.
Deterministic
Under the same product version, configured expected map, pack, and instrument settings, the same inputs produce the same audit and the same audit identifier. The evidence-bundle export timestamp is the only intentionally variable field.
Authentication & network exposure
- Optional API key. Set an environment variable to require a key on the /v1/* routes. With none set, auth is disabled — appropriate only on a local or trusted network. /health, /ready, and /version are intentionally unauthenticated, and /ready returns a slim body to unauthenticated callers (no paths, secrets, pack names, or fingerprints).
- Bind to loopback. The server defaults to 127.0.0.1. Exposing it on a network interface is done only behind a reverse proxy you configure and control; TLS and network access control are the operator's responsibility.
- Secrets. The API key is read from the environment at request time; it is never written to evidence bundles or logs.
Handling prompts, responses & evidence
- Treat prompts and responses as potentially sensitive. They may contain personal or confidential content; DSI does not redact them for you.
- Log content. By default the runtime does not emit prompt/response text to logs. If you raise verbosity for debugging, review what your configuration writes before sharing logs.
- Evidence retention is yours. A bundle contains the audited text (or its representation), the coverage result, and provenance fingerprints. Where you store it, how long you keep it, and who can read it are your decisions.
- Access control & multi-tenancy. DSI provides no user accounts, roles, or tenant isolation; access control is delegated to your deployment. Multi-tenant use is unsupported in 0.2.1.
Dependencies & reporting
The core installs with no third-party runtime dependency; the API/dashboard extra adds a small, well-known web stack. Keep these updated per your organisation's process.
This page describes the product's posture; it does not claim an independent security audit has taken place. Report suspected vulnerabilities privately via the contact page rather than a public channel.