MCP-Open-Discovery-with-AMQP

The project demonstrates a very strong focus on security, particularly in plugin management, input sanitization, and credential handling. - **Strong Plugin Security**: Implements manifest validation (JSON Schema), SHA256 integrity checks for plugin distributions, static code analysis for restricted module imports, runtime sandboxing (via `Module._load` override) to enforce permissions and dependency policies (`bundled-only`, `external-allowlist`, `sandbox-required`), and optional digital signature verification for trusted plugins. Untrusted or invalid plugins can be quarantined. - **Input Sanitization**: Crucially, `nmap_tools_sdk.js` and `network_tools_sdk.js` explicitly use `sanitizeHost` and `sanitizeUrl` functions to mitigate command injection risks when executing external binaries (`nmap`, `ping`, `wget`, etc.). - **Secure Credential Management**: Utilizes AES-256-CBC encryption for sensitive data (passwords, API keys, SSH keys, etc.) stored locally, supports encryption key rotation, maintains an audit log, and integrates with AWS Secrets Manager and Azure Key Vault for robust secret management. - **Operational Security Concerns**: Default AMQP credentials (`amqp://mcp:discovery@localhost:5672`) and Zabbix credentials (`Admin/zabbix`) are provided for quick start but **must be overridden** in production deployments. Some Nmap tools (`-sS`, `-sU`) explicitly add `--privileged` arguments or inherently require elevated privileges (e.g., `CAP_NET_RAW`, `CAP_NET_ADMIN` in Docker), which is a significant deployment-time security decision and should be managed carefully.