LANs, WANs, and other network scopes
Use LAN, WAN, campus, and wireless network labels to explain scope while drawing the actual trust and access boundaries separately.
The idea
Network scope labels include local area, wide area, metropolitan, personal, campus, and wireless local area networks. A storage area network describes a specialized purpose rather than just geographical scale. These categories help explain an environment, but implementation and trust boundaries vary. A wide-area link may connect offices, while a local network may contain untrusted guests. Security depends on actual access and controls.
In practice
A campus has multiple local networks connected by routing, while remote branches join through wide-area services.
A common misunderstanding
A LAN is not automatically a trusted zone, and geographical proximity does not justify broad access.
Check your understanding
What should a security diagram show beyond scope labels?
Think it through: Resources, identities, permitted flows, enforcement points, and relevant dependencies.
Scale describes one dimension
Imagine a fictional academy has classrooms in one building and remote staff in another city. The classrooms may contain several local networks, while a wide-area service connects locations. A wireless network describes an access technology; a storage network describes a specialized purpose. These labels answer different questions.
A useful description states both scope and role. “The campus network” might include student access, administration, labs, guests, and equipment management. Treating all of these as one trusted group hides distinctions that matter to security decisions.
Draw people and services into the picture
For the academy, identify which users and devices need each service. A nearby guest device should not gain administrative access simply because it is physically on campus. A remote employee may legitimately need a narrowly scoped internal service through an authenticated path.
Geography therefore cannot decide authorization by itself. The diagram should distinguish the connectivity arrangement from the identity and permission requirements. A local link can carry hostile traffic; a long-distance path can carry a correctly protected, authorized exchange.
Account for the links between scopes
Branch connections introduce dependencies such as service providers, gateways, routing, and name resolution. If a branch loses its wide-area connection, locally available services may behave differently from centrally hosted applications. Availability planning needs that distinction rather than a single “network down” assumption.
For a paper exercise, sketch two classrooms and one remote worker. Label the local networks, the inter-site path, and the applications each user needs. Add one resource that guests must not reach and show where the restriction applies.
Then describe the effect of losing one inter-site link. State which activities continue and which depend on the affected path. The value of the network-type vocabulary is making the environment understandable; the security value comes from adding specific identities, resources, permitted journeys, and failure boundaries.
Keep exploring
References & further reading
Original explanations, with primary references for deeper study.
Cisco: Networking basics