

Security and disclosure
Ogun handles downloads and data-source credentials. If you find a weakness, we want to hear about it first.
How to report
Email info@vernesystems.com with the subject line starting SECURITY:. Please include what you found, the affected component and version or commit, steps to reproduce, the impact you expect, and how you would like to be credited. Do not include real credentials or other people’s data. Once the repositories are public, private reporting through GitHub security advisories will also be available.
Scope
- ogund, the ogun command line and its MCP server and bridges.
- Operator sandboxing and the operator ABI.
- The artifact store and lineage records.
- The zeus-core engine library as embedded by Ogun, and the session bridge to Zeus.
- This website and its machine-readable files.
Out of scope: volumetric denial-of-service, social engineering of Verne staff, physical attacks, findings that require a compromised device or browser, and reports produced only by automated scanners without a demonstrated issue.
What we care about most
- Any way for an agent, a web page, an operator or a dataset to approve a request, widen a budget or obtain credentials.
- Escaping an operator sandbox, or an operator reading files or network it did not declare.
- Secrets reaching logs, events, lineage records, error messages or model prompts.
- Benchmark runs reaching the user’s artifact stores, the Zeus daemon or the network when they should not.
- Corrupting the run journal or the artifact store so that Ogun reports work it did not do.
What we commit to
- Acknowledge your report within 3 business days.
- Give an initial assessment within 10 business days and keep you informed.
- Fix confirmed issues as fast as their severity requires, and coordinate disclosure with you. Our default disclosure window is 90 days.
- Credit you in the advisory if you wish.
We do not currently run a paid bug bounty.
Safe harbour
We will not pursue legal action against good-faith research that follows this policy: test only against your own installations and accounts, avoid privacy violations and service disruption, do not access or keep other people’s data, and give us reasonable time to fix an issue before disclosing it.
Security by design
Ogun never holds browser session material; code runs only in sandboxed child processes; approvals are bound to request hashes and decided only on human trust surfaces; the daemon has a single local endpoint; secrets are zeroized and never serialized; benchmark runs are sealed by default.