Defining Data Flows
The Flows page provides a visual canvas where you define the allowed communication paths between your security zones. This is the core of defining your high-level security policy.
The Flow Visualizer
The main part of the page is an interactive diagram showing your security zones as nodes. The goal is to create connections (edges) between these nodes to represent legitimate data flows.
For example, if your application servers need to communicate with your database servers, you would create a flow from your "Application Zone" to your "Data Zone".
Creating a New Flow
- Hover your mouse over the source zone (e.g.,
Application Zone). Connection handles will appear on the sides of the node. - Click and drag from one of the handles to the target zone (e.g.,
Data Zone). - Release the mouse button over the target zone. A dialog box will appear.
- In the dialog, specify the Protocol/Port that this flow should allow (e.g.,
TCP/5432for PostgreSQL). - Click Create Flow.
A new arrow will appear on the diagram, connecting the two zones and labeled with the protocol you defined.
Editing or Deleting a Flow
You can manage existing flows:
- Click on the flow's label on the arrow connecting two zones.
- The "Edit Flow" dialog will appear.
- From here, you can:
- Update the Protocol/Port -- Change the allowed protocol and save your changes.
- Delete the Flow -- Click the Delete Flow button to remove the connection entirely.
How Flows Translate to Rules
Every flow you define here is an abstract "allow" rule. When you move to the Deployment page, the system uses these flow definitions, combined with the resource assignments in your Zones, to generate concrete security rules for each cloud provider.
For instance, the flow from Application Zone to Data Zone on TCP/5432 will result in:
| Field | Value |
|---|---|
| Source | All IP/CIDR ranges of resources in the Application Zone |
| Destination | All IP/CIDR ranges of resources in the Data Zone |
| Protocol | TCP |
| Port | 5432 |
| Action | Allow |
This abstraction allows you to manage your security posture from a high-level, architectural perspective without getting bogged down in the details of each cloud provider's implementation.
Common Flow Patterns
| Pattern | Source | Destination | Protocol | Use Case |
|---|---|---|---|---|
| Web traffic | Public DMZ | Application Zone | TCP/443 | HTTPS from load balancers to app servers |
| Database access | Application Zone | Data Zone | TCP/5432 | PostgreSQL connections |
| Admin access | Management Zone | All Zones | TCP/22 | SSH bastion access |
| Monitoring | All Zones | Management Zone | TCP/443 | Metrics and health check export |