Kiro Gateway is a compliance-first bridge to the official kiro-cli binary. The gateway does not call private Kiro HTTP endpoints, pool accounts, or own Kiro credentials. Authentication remains inside kiro-cli.

This policy covers the gateway source code, its HTTP API, ACP translation, and its configuration and deployment examples. Vulnerabilities in kiro-cli, Kiro, third-party AI harnesses, or MCP servers should be reported to their respective maintainers.

Please do not open a public issue for a security vulnerability. Use GitHub's private vulnerability reporting form when it is available. If the form is unavailable, contact the maintainer through the GitHub profile and request a private channel.

Include the affected version or commit, reproduction steps, impact, and any mitigation you know. Never include API keys, session tokens, Kiro credentials, or other secrets in a report.

ACP_TRUST_TOOLS=true allows kiro-cli to run its built-in tools after the gateway answers permission requests. For shared or exposed deployments, set it to false and scope the workspace deliberately. See the configuration and security notes in the README.