Directory / Dify
Dify
Code nodes run in a separate sandbox service, outbound HTTP goes through an SSRF proxy, and stored credentials are encrypted per workspace. Human Input nodes can pause a workflow, but only where you add them.
Lock this down first
Set a strong SECRET_KEY before first launch and add Human Input nodes before any step with side effects.
Scorecard
| Criterion | Rating | Notes |
|---|---|---|
| Permission granularity | Unverified | Not confirmed in the docs we checked. |
| Human approval gates | 1/3 | A Human Input node pauses a workflow for review, but only where the builder adds one. Agents don't pause by default. |
| Sandboxing | 2/3 | Code and Template Transform nodes run in a separate sandbox service. Other tools run in the main service. |
| Secrets handling | 3/3 | OAuth credentials are encrypted with AES-256 using SECRET_KEY. Model provider keys and tool credentials are encrypted with per-workspace RSA keys, kept locally or in Azure Key Vault. |
| Audit logs | 2/3 | Logs cover every channel, including an Agent's tool iterations and a node-by-node trace, with configurable retention. |
| Kill switch / interrupt | Unverified | Not confirmed in the docs we checked. |
| Network egress control | 1/3 | An SSRF proxy blocks requests to internal and private IP ranges. No allowlist for public destinations. |
Sources
Vendor? Request a correction. We review corrections within 7 days.
