oscerd opened a new issue, #5: URL: https://github.com/apache/camel-kit/issues/5
## Description Add project-level security model and threat model documentation for Camel-Kit, following the precedent established in core Apache Camel ([CAMEL-23496](https://issues.apache.org/jira/browse/CAMEL-23496) / [PR #23181](https://github.com/apache/camel/pull/23181)) and other subprojects such as Camel Quarkus ([PR #8654](https://github.com/apache/camel-quarkus/pull/8654)) and Camel Spring Boot. As Camel-Kit joins the Apache Camel organization, having an authoritative scope statement and threat model is essential for contributors, reviewers, operators, and automated vulnerability triage. Camel-Kit inherits the core Apache Camel trust assumptions, but also introduces specific surfaces and trust boundaries related to AI coding assistants, agent workflow execution, graph parsing of migration sources, and dynamic classloader resolution. ### Proposed Scope & Areas to Cover 1. **Inherited Security Model:** - Reference the canonical [Apache Camel Security Model](https://camel.apache.org/manual/security-model.html). - Core trust boundaries (route/configuration vs. untrusted payload data). - Standard ASF vulnerability reporting procedure via `[email protected]` with explicit warnings prohibiting public GitHub issues or pull requests. 2. **Camel-Kit Specific Considerations:** - **AI Coding Agent Workflows & Prompt Boundaries:** - Trust boundaries around AI prompts, agent execution, skills (`SKILL.md`, `guides/`), and generated integration code. - Enforcement of safe defaults and security constraints in generated routes and configurations (aligning with `constitution.md` and `iron-laws.md`). - **Static Analysis & Graph Parsers (`camel-kit-graph`):** - Safe parsing of user-provided migration inputs (XML, DataWeave, Mule, BizTalk, Java, Groovy, YAML) preventing XXE, path traversal, or arbitrary code execution during inspection. - **Ship Resolver & Dynamic Dependency Resolution (`camel-kit-ship-resolver`):** - Classloader isolation and dependency resolution boundaries. - **CLI, JBang Plugin, & MCP Servers (`camel-kit-main`, `camel-jbang-plugin-kit`, knowledge MCP):** - Execution boundaries, local workspace file writes, and tool parameter validation. - **In-Scope vs. Out-of-Scope Definitions:** - Explicit guidance on what constitutes a framework vulnerability vs. LLM hallucination, user-directed insecure route designs, or local operator environment misconfigurations. 3. **Deliverables:** - `SECURITY.md`: Root-level policy with reporting guidelines and disclosure instructions. - `docs/security-model.md`: Detailed security architecture, trust boundaries, threat model, and deployment hardening. - Contributor/Agent documentation updates (`CLAUDE.md`, templates) referencing security boundaries and verification requirements. ## Expected Behavior Clear, published security model and threat model documentation in `apache/camel-kit` providing maintainers, security researchers, and users with a well-defined boundary for vulnerability reporting and safe usage. ## Additional Context - Precedents: - Apache Camel Core Security Model: https://camel.apache.org/manual/security-model.html - Camel Quarkus Security Model: https://github.com/apache/camel-quarkus/blob/main/docs/modules/ROOT/pages/user-guide/security-model.adoc - Apache Camel Security Reporting: https://camel.apache.org/security.html -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
