Governance you can point to, not just claim.
We didn't retrofit compliance language onto three products after the fact. Every control below maps to a named framework, and every framework maps to a specific mechanism you can inspect.
Three frameworks. Named mechanisms.
These aren't badges on a footer. Each one shapes how a specific product behaves.
- NIST AI RMFAI Risk Management Framework
- Structures how we categorize agent risk, from discovery through enforcement. Quin's agent inventory and intent analysis support the RMF's Map function; Zino's call-time authorization and audit ledger support Measure and Manage.
- MITRE ATLASAdversarial Threat Landscape for AI Systems
- MITRE's catalog of adversary techniques against AI systems. Zino limits what three of them can achieve: an injected instruction (AML.T0051, LLM Prompt Injection) still can't make an ungranted call, because every tool call is authorized against policy first (AML.T0053, AI Agent Tool Invocation), and agents hold no long-lived credentials to harvest (AML.T0083, Credentials from AI Agent Configuration). Quin flags AI software supply chain exposure (AML.T0010.001) by checking the detected agent framework and version against OSV.dev.
- OWASP LLM Top 10LLM Application Security Risks
- The baseline risk taxonomy for LLM-integrated applications. Zino checks every tool and network call against the agent's policy before it runs, which limits what LLM01 (prompt injection) and LLM06 (excessive agency, 2025 edition) can do: an injected instruction still can't make a call the policy doesn't grant. Drona, in private development, is being designed to add workflow contracts on top.
What "governed" means in practice.
Every access decision is logged
Zino writes an append-only audit ledger for every permission grant, denial, and scope change, attributable to a specific agent identity rather than a shared service account.
Enforcement is structural, not advisory
Zino denies any tool or network call the agent's policy doesn't grant, before it runs. A policy that can be silently bypassed by a misconfigured agent isn't a control; it's a suggestion.
Visibility doesn't require instrumentation
Quin scans source code and configuration without agent-side changes, so shadow agents (the ones nobody registered) still show up in your repositories.
Security at Gaincontrol
Where we stand as a vendor, item by item.
- Where your data lives
- In your environment. Quin and the Zino control plane run on infrastructure you control, and Gaincontrol hosts no customer data.
- Quin and your code
- Code and prompts go from your machine to the LLM provider you choose, never to Gaincontrol. With --no-llm and --no-vuln-check, a scan of a local repo makes no external calls.
- Zino and your credentials
- Your existing vault stays the source of truth. Zino brokers a scoped credential for each approved call, and agents never hold a long-lived secret.
- Vulnerability disclosure
- Report security issues to security@gaincontrol.ai. Our security.txt points to the policy below.
Found a vulnerability?
Email us with details and reproduction steps. We acknowledge credible reports promptly.
Want the mechanism, not the marketing?
Talk to our team about how Quin and Zino map to your existing compliance requirements and audit process, and where Drona will fit as it develops.
