How Vaigil defends itself
Its own network purposes, sealed credentials, separate log writer and session limits.
What it may connect to
vaigil networkEvery outbound connection is for one declared purpose: an action, anchoring, a connector, mail, the AI analyst's model, the SIEM stream, shared signals, Slack reminders, single sign-on and notice webhooks. An undeclared purpose is refused in every mode, and network.mode offline refuses everything that would leave the host.
Sealed credentials
vaigil vault status
vaigil vault rotateA connector's credentials and a feed's secret are sealed under a keyring, so the store's files alone give nobody the values: a lost laptop, a backup on an open bucket, a disposed disk. With no keyring, none can be stored.
Sign-in
Everybody signs in with two factors: a passkey that checks it is them, or single sign-on that says it used two. Failed sign-ins lock out places, not people, and sessions end after an hour unused, fifteen minutes for anybody who can grant access.
The AI only suggests
The AI analyst and agents over MCP read and propose. Neither can record a decision, approve an action, change who may do what, or reach another platform. See Findings and AI agents over MCP.
Reporting a vulnerability
Use GitHub's private vulnerability reporting for the repository.