id-am-3 high Identify / Asset Management

Authorized network communication and data flow representations are maintained

Knowing what devices and software you own is not enough if you do not know how they talk to each other. Network diagrams and data flow maps let you spot unauthorized connections, scope firewall rules accurately, and explain your environment to auditors or incident responders. Without them, detecting lateral movement or a data exfiltration path becomes guesswork.

Estimated effort: 6h

networkdata-flowstopologyinventory

Complete first: id-am-1 , id-am-2

Implementation steps

1

Draw a logical network diagram

Capture all network segments (internal LAN, DMZ, cloud VPCs, remote access), how they connect, and the major systems that sit in each. Tools like Lucidchart or draw.io work well. For larger environments, use automated discovery tools that generate topology maps from live traffic or routing tables.

lucidchartdraw.ionetbrainauviknmap
2

Document internal and external data flows

For each application or service, record: what data it sends and receives, the protocol and port used, the source and destination (internal system, cloud service, or third party), and whether the data is encrypted in transit. Prioritize flows that carry sensitive or regulated data.

zeekwiresharkaws-vpc-flow-logsnetflow
3

Review and update diagrams on a defined schedule

Assign an owner and set a quarterly review cadence. Trigger an out-of-cycle update whenever a new system is deployed, a network segment is added or removed, or a major architecture change is made. Store diagrams in a version-controlled location so changes are traceable.

confluencesharepoint