Security, versions, and vulnerability reporting¶
QuantDinger handles model secrets, trading credentials, and account data. A production operator should treat the application, database, cache, and reverse proxy as one security boundary and restrict network access to administration surfaces.
Operator responsibilities¶
- Deploy trusted releases or images and read release notes before upgrading.
- Use long random passwords and separate administrators from regular users.
- Provide credentials through environment variables or a secret system; never put them in source, logs, screenshots, or issues.
- Grant trading APIs only the permissions required, disable withdrawals, and prefer a dedicated subaccount.
- Apply access control, encryption, and retention rules to databases, object storage, and backups.
- Enable HTTPS at the reverse proxy, restrict administration endpoints, and update dependencies and base images.
- Rotate model keys, OAuth secrets, Agent Tokens, and trading credentials regularly.
See production hardening for the deployment baseline and observability for operational monitoring.
Agents and automation¶
Agent Tokens should use minimum scopes, expirations, rate limits, and notional limits. Human JWTs and Agent Tokens are not interchangeable. Every side-effecting Agent request should use a unique Idempotency-Key. Keep the global live-trading switch disabled unless an operator explicitly enables it after completing the live-trading safety checklist.
Untrusted indicators and strategies¶
- Use the official Linux-based deployment for any installation that accepts code from users. The sandbox requires a supported
x86_64oraarch64kernel with seccomp and Landlock and fails closed when those controls are unavailable. - Do not add database URLs, application secrets, broker credentials, cloud keys, host sockets, or secret-bearing mounts to indicator or strategy child processes.
- Indicator execution and strategy discovery use disposable processes. Each backtest uses a disposable runtime process, while each running live deployment owns a persistent callback process. None of these processes can submit exchange orders directly.
- Keep
STRATEGY_RUNTIME_SANDBOX_TIMEOUT_SECONDS,STRATEGY_RUNTIME_SANDBOX_MEMORY_MB,STRATEGY_BACKTEST_SANDBOX_TIMEOUT_SECONDS, andSTRATEGY_BACKTEST_SANDBOX_MEMORY_MBat bounded values appropriate for the host. The live request defaults to 120 seconds; the retiredSTRATEGY_SCRIPT_CALLBACK_TIMEOUT_SECsetting is ignored. Raising a limit increases resource exposure; it does not grant additional strategy capabilities. - After an upgrade that changes the sandbox, rebuild or pull the backend image and restart the API, trading, evaluator, and backtest workers. Existing processes do not acquire a new kernel policy in place.
See the indicator guide, Strategy API V2 guide, and process ownership model for the exact execution contract.
If exposure or suspicious activity is found¶
- Stop affected strategies and new trading.
- Revoke related tokens, API keys, and sessions.
- Verify orders, positions, and permissions at the venue or broker.
- Preserve the necessary logs without spreading secrets or personal data.
- Restore service only after remediation and credential rotation.
Report a vulnerability¶
Do not disclose exploitable details, credentials, or account data in a public issue. Follow the repository security policy to report privately. Include the affected version, reproduction conditions, impact, and any practical mitigation.
