Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions docs/docs/Support/security.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
---
title: Security notice
slug: /security
---
Comment thread
aimurphy marked this conversation as resolved.
Outdated

The Langflow UI is an IDE and code execution platform, which means that Langflow is inherently capable of executing arbitrary, developer-provided code.
By design, the Langflow UI includes a code editor allowing developers to author and execute arbitrary Python with full access to the host Langflow backend process, filesystem, and network.
In addition, various components wrap and make use of code execution, in some cases using AI models to generate the code to be executed based on user input.

Given these product features, the Langflow application makes no attempt to prevent malicious activity between different users of a given Langflow process, or to secure the execution environment of the Langflow process, such as preventing access to portions of the local disk. To the extent that limitations are imposed on the access provided to different users, such as limiting flow visibility to a user's flows, these limitations are intended to improve usability, not to impose secure access policies.
For example, users of Langflow can always access the underlying database connection directly.

The security of code and flows written using Langflow is the developer’s responsibility.
Comment thread
mendonk marked this conversation as resolved.
Outdated
Langflow does not and can not prevent developers from building insecure applications.
Comment thread
mendonk marked this conversation as resolved.
Outdated
In the same way that Python can’t prevent developers from writing services with SQL-injection vulnerabilities, Langflow can’t prevent developers from writing flows that leak user’s PII, fail to sanitize input, etc.
Comment thread
mendonk marked this conversation as resolved.
Outdated
Langflow makes efforts to ensure that components and flows are secure by default and behave as expected, but application behavior is ultimately the developer’s responsibility. 
Comment thread
mendonk marked this conversation as resolved.
Outdated

Langflow’s cloud security flows from infrastructure.
Comment thread
mendonk marked this conversation as resolved.
Outdated
Cross-tenant isolation is provided by isolating instances of Langflow to individual tenants, not by the Langflow application itself.
Within a Langflow cloud container, users are given full access to the process, disk, and network.
Security restrictions are enforced between cloud containers, and between containers and the host instance and network.
Comment thread
mendonk marked this conversation as resolved.
Outdated
Authentication and authorization are provided and enforced outside of the Langflow container.
To the extent that services are shared across tenants, such as a shared PostgreSQL database, access limitations are enforced externally, for example by providing DB credentials associated with external security policies.
Comment thread
mendonk marked this conversation as resolved.
Outdated
5 changes: 5 additions & 0 deletions docs/sidebars.js
Original file line number Diff line number Diff line change
Expand Up @@ -460,6 +460,11 @@ module.exports = {
id: "Support/luna-for-langflow",
label: "IBM Elite Support for Langflow",
},
{
type: "doc",
id: "Support/security",
label: "Security",
},
],
},
{
Expand Down
Loading