Network Flow Matrix
Document Source → Destination → Port → Protocol → Action → Justification communications, then export them.
Flux documentés
| Source | Destination | Port | Proto | Action | Justification |
|---|
Les data restent dans ce navigateur. N’utilisez pas la matrice pour stocker des secrets.
Use the result with confidence
Recommended workflow
- Use a non-sensitive representative input for documenting network flows.
- Run the operation and review the result before copying or exporting it.
- Validate the output in the target application or environment before relying on it.
What to verify
- Confirm the scope, units and input values before interpreting the output.
- Separate the observed result from the operational decision that follows from it.
- Validate the conclusion against the real target system, logs or configuration before changing production.
Questions about this tool
What should be documented when using documenting network flows?
Record names, identifiers, owners, addressing or flow direction and the technical dependency that makes each entry necessary.
How do I keep the result useful over time?
Use a clear source of truth, date changes and reconcile the document with real configuration during reviews.
What should I validate before production changes?
Compare the plan with routing, switching, firewall, DNS/DHCP and monitoring configuration that already exists.