Network flow matrix
Network Flow Matrix
Document Source → Destination → Port → Protocol → Action → Reason communications, then export them.
Documented flows
| Source | Destination | Port | Proto | Action | Reason |
|---|
Data stays in this browser. Do not use the matrix to store secrets.
Practical example: document a network flow
Describe application access
Enter VLAN10 as source, APP-TEST as destination, 443 as port and TCP as protocol. Choose Review and add the business reason before adding the flow. A precise row helps the network team compare the need with an existing rule or a planned change.
Separate documentation from applied rules
The matrix records a need or decision. Selecting Allow or Block does not modify a firewall. Check addresses, object scope, traffic direction and application dependencies. A name entered in the matrix does not replace DNS resolution or a connectivity test.
Review and approve the matrix
- Identify the service owner and justify the ports actually required.
- Compare each row with test results and with the relevant firewall configuration.
- Export CSV or JSON, date the version and record decisions and discrepancies in the change record.