Back to selected work

Network segmentation

FortiFlow2

Under validation

Turn traffic logs into understandable FortiGate policies, with checks before generation.

View source
  • Analyse observed traffic
  • Understand policy grouping
  • Check before generating
FortiFlow2 — Actual interface · fictional demo data
Actual interface · fictional demo data
01

The need

Logs show which machines communicate. On their own, they do not tell you which firewall policies to create. Grouping too broadly can allow communication that has never been observed.

02

My role

I define the requirements from my network experience, set the security rules and lead the design. I check proposed policies against test scenarios before command generation.

03

The design

  1. Trace each proposed policy back to observed traffic.
  2. Distinguish exact grouping from policies that allow additional traffic.
  3. Leave ambiguous cases to the engineer.
  4. Use the same checks for preview and command generation.
  1. 01Import logs
  2. 02Review traffic
  3. 03Check proposals
  4. 04Generate commands
04

What the tool delivers

The tool connects traffic analysis with policy preparation. Each proposal remains linked to the observations behind it, so the engineer can understand and check the result.

Scope & limitations

FortiFlow2 is still under validation. It prepares proposals and commands; the engineer decides whether a policy should be applied.

Validation notes

For the version documented in September 2026, 310 tests and the full analysis-to-generation workflow passed. Balanced and Compact strategies add no traffic in the reference scenario. Final review remains outstanding before pre-deployment use with engineer approval.

  • Node.js
  • JavaScript
  • Docker
  • FortiGate
  • FortiAnalyzer
  • Playwright
Reference architecture

100 %Scroll the diagram to explore the details.
Connections & trafficControls / logsProtection / blocking