Baseline network diagram requirements
Overview
Diagrams are living documents, not marketing wallpaper. Minimum set speeds triage and renewal conversations.
Layers
- Physical: sites, WAN links, demarc, UPS.
- Logical: VLANs, firewall zones, VPN paths, SD-WAN overlays as appropriate.
- Cloud: landing zones, peering/transit, identity flow—not just a generic Azure logo blob.
Conventions
Consistent coloring for VLANs; IP schema table appendix; no secrets on diagrams—reference vault IDs instead.
Tooling
Draw.io / Lucid / CADE—pick one stack per client; version control exports quarterly.
Validation
Quarterly diff against live configs (VLAN export, route tables); discrepancies become tickets with owners.
SLA tie-in
“Accurate within 5 business days of material change” clause in MSA prevents endless drift excuses.
Related Articles
EDR deployment checklist for new workstations
## Overview Use this runbook when onboarding a new Windows workstation or re-imaging a device that...
Handling Defender for Business false positives
## Overview False positives waste analyst time and train users to ignore alerts. This article stand...
Application allowlisting with Windows Defender ASR rules
## Overview Attack Surface Reduction (ASR) rules reduce exploit surface by constraining Office macr...