Introduction to Computer Networks
Trace how an order travels from a customer's phone across LANs, a WAN and the internet to a server, and name the links that must be protected.
How one tap reaches a pharmacy
At 7:40 in the evening, Mrs. Lata Gokhale opens the Tulsi Health app on her phone, taps "Repeat last order" for her blood-pressure tablets, and two seconds later sees "Order confirmed". The next morning Farida Shaikh, the senior pharmacist at the Kothrud store, finds the same order waiting on her billing screen and packs it. Nothing physical travelled between the phone, the app and the store; only data did, passed along a chain of connected machines. A computer network is exactly that: two or more devices joined so they can exchange data, following shared rules about how to do it. Almost every attack you will meet in security travels over a network, so knowing how the pieces are joined tells you where things can go wrong and where to put the locks.
One order touches four networks: a home network, the internet, the cloud, and a store's own network. Every line in the picture is a connection that has to work, and a path that has to be protected.
Devices, links and shared rules
Every network, however large, is made of three ingredients. First, the devices that send and receive data, such as phones, laptops, printers and servers; network people call each one a node. Second, the links that carry data between them: copper cables, fibre-optic lines that carry light, Wi-Fi radio waves, or mobile phone signals. Third, the agreed rules, called protocols, that decide how a message is packed, addressed and checked, so that a phone made in one country can talk to a computer built in another.
Indian Railways is a good picture of this. The stations are the nodes, the tracks are the links, and the timetable and signalling rules are the protocols that let trains from different zones share the same tracks safely. A station with no track leading to it is useless, however grand it is. In the same way, a device is only useful on a network if it has network connectivity: a working path, link by link, to the device it needs to reach.
When connectivity breaks, nothing may be wrong with the devices themselves. A cable cut by road works, a router someone switched off at night, or a Wi-Fi password changed without telling the staff is enough to make the billing laptop and the cloud unable to reach each other. To the person at the counter, the service is simply "down". This is why security people care about connectivity at all: one of the three things they protect is availability, which means systems are usable when people need them, and a broken link is one of the most common ways availability is lost.
Small networks and wide ones: LAN and WAN
A local area network (LAN) connects devices in one place: a home, an office floor, a single shop. At the Nashik Road store, the billing laptop, the receipt printer and the staff phones on the store Wi-Fi together form a LAN. The devices are close together, belong to the same organisation, and are joined by cables and Wi-Fi inside the building. Data moves inside a LAN very quickly because it never leaves the premises.
A wide area network (WAN) connects networks that are far apart, across a city, a state or the world. Tulsi Health has LANs in 14 stores in Pune and Nashik plus one at the Kothrud head office, and the long-distance links that join them into one company network form its WAN. Tulsi Health does not lay its own cables between Pune and Nashik; it rents those links from an internet service provider (ISP), a company that sells connections to the wider world, just as you pay a company for home broadband or mobile data.
An apartment society shows the difference. The intercom in the society lets any flat ring the watchman or the secretary instantly, and it only works inside the compound: that is a LAN. Calling a cousin in Nagpur uses the telephone company's long-distance lines, which you do not own and cannot see: that is a WAN.
A LAN is the network inside one building; a WAN joins buildings far apart. Each has its own security worry, so each needs its own protection.
The security worries differ too. Inside a LAN, devices tend to trust each other, so one infected laptop can often reach the printer, the other laptops and any shared folder nearby. That is why a store's guest Wi-Fi for customers is kept separate from the staff network. On a WAN, your data passes through cables and equipment owned by other companies, so anything sensitive must be scrambled (encrypted) before it leaves the building.
The internet: a network of networks
The internet is not one network owned by one company. It is tens of thousands of separate networks, belonging to homes, colleges, companies, mobile operators and cloud providers, that have agreed to connect to each other and carry each other's traffic using the same protocols. ISPs link these networks together, and large ISPs link to each other, so that a message can travel from any connected device to any other. Nobody runs the whole thing, in the same way that nobody owns every road in India: colony lanes, city roads, state highways and national highways belong to different authorities, yet a delivery van can drive from any doorstep to any other.
That openness is what makes the internet useful, and it is also the root of most network risk. The same connection that lets Mrs. Gokhale reach the Tulsi Health app from her home lets anyone, anywhere, try to reach it. Automated programs scan the internet all day looking for devices with weak passwords or missing updates, and a new server is usually probed within minutes of being switched on. Anything connected to the internet should be treated as reachable by strangers unless something deliberately blocks them.
Clients ask, servers answer
Most conversations on a network follow one simple pattern. A client is a device or program that asks for something, and a server is a computer that waits for requests and answers them. Mrs. Gokhale's app is a client; the Tulsi Health app server in the cloud is a server, and it stores orders in a database, an organised store of records such as customers, medicines and orders. The billing laptop at Kothrud is a client too, asking the same server every few minutes whether new orders have arrived. This pattern is called client-server communication.
The phone and the store laptop never talk to each other directly. Both are clients of the same server, which is why the server and its database are the most valuable thing to protect.
A chemist's counter works the same way. Customers walk up and ask; the pharmacist behind the counter answers each one in turn, serves many people a day, and never goes out looking for customers. Because the server answers strangers all day and holds everyone's data in one place, it is the prize attackers want most. It must check who is asking (a login), give each client only that client's own data, and stay available when the evening rush arrives. Clients can be attacked too, for example a phone with a harmful app installed, but one weak server can expose all 2.4 lakh customers at once.
Sort the Tulsi Health connections below by the kind of network they mainly use. For each card, ask whether the data stays inside one building, travels between Tulsi Health's own sites, or goes out to the wider internet.
When the links matter: connectivity and safety
Thinking in links helps in two ways. When something stops working, you can ask which link broke and what still works on either side of it. When you are deciding what to protect, you can ask who else is able to use each link. A store whose internet line is cut can still print bills on its LAN but cannot see app orders; a link that a stranger can join is a link that needs a password, a separate network, or encryption.
Play Neha Kulkarni, the IT and security lead, through four everyday situations below. Each one asks you to think about which link is involved and what keeps it working or keeps it safe.