Security overview: Flow runtimes
- Last UpdatedNov 02, 2026
- 2 minute read
Flow runtimes are often installed in environments that have access to sensitive systems. As a result, it’s important to understand the associated security concepts and potential threats for flow runtimes. To avoid introducing unintentional risk or malicious use, carefully review the information in this topic to ensure your flow runtimes are secure.
This topic covers the following information:
-
An overview of how flow runtimes work and the potential for security exposure
-
How flows affect each other
-
Using Code modules
Flow execution
A typical flow performs the following operations:
-
Collects data from an external system using a network connection.
-
Processes the data.
-
Sends results to an external system by network connection.
Most flows use outbound connections to communicate with external systems. The security exposure depends on the systems and resources that the flow runtime is permitted to access.
A flow runtime includes a built-in HTTP server and MQTT broker that accepts inbound requests. By default, inbound access is allowed only from localhost and authentication must be configured. Data sent to these endpoints is used only when a running flow explicitly consumes it through the HTTP Listener and MQTT Sub Client modules.
Each flow runs in its own process, which provides some isolation between flows, but not full isolation. We recommend that you treat the runtime as the security boundary. If a per-flow security separation is required, use one runtime per flow.
How flows affect each other
The following list provides examples of when flows can affect each other:
-
A flow can exhaust all resources available to the runtime (CPU, memory, disk), which may affect other flows on the same runtime.
-
Each flow has access to, and can modify, resource files used by other flows.1
-
Each flow has access to credentials used by other flows.
-
Each flow has access to and can modify logs for other flows and the host.
-
A flow can modify the runtime configuration files.1
-
A flow can modify the configuration of other flows.1
-
A single Python environment is shared by all flows. As a result, only a single version of external packages can be installed. The most recently installed version takes precedence over previous installations of external packages.
1These operations require restart of the runtime to take effect, which requires privileged access to the server hosting the runtime.
Code modules
Flows support execution of customer code, through the use of Code modules (C#, Python and JavaScript).
These are powerful tools that can be used to implement custom functionality, but can also be dangerous if not used properly or maliciously. In particular, the Python module must be used carefully because it provides access to a full standard Python environment where third-party libraries can be installed. The code in Code modules is executed with the same privileges as the runtime.