Network Interception and Security Threats
Explain how eavesdropping, spoofing, man-in-the-middle and ARP poisoning work, and identify what HTTPS and network separation do to stop them.
Who else can read what you send?
Riya Menon, Tulsi Health's intern, is finishing a stock report at a café near her college in Kothrud. She joins the café's free Wi-Fi and logs in to an old supplier portal whose address begins with http://, not https://. Her username and password pass through the café's Wi-Fi and several other machines before they reach the portal, and at any of those stops someone could read, copy or change them. Network interception is the family of attacks in which someone gets between you and the place you are talking to, and it is the reason the small "s" in https matters so much.
Anything you send over a network is cut into small pieces called packets, and each packet carries a slice of your data plus a label saying where it came from and where it is going. Those labels use IP addresses, numbers such as 142.250.1.10 that identify a device on a network, the way a PIN code and house number identify a home. A router is a device that reads the destination on each packet and passes it one step closer, like a sorting office passing letters along. A Wi-Fi access point is the box that lets phones and laptops join by radio instead of a cable.
Postcards in transit: eavesdropping and packet sniffing
Eavesdropping means secretly listening to a conversation you are not part of. On a network, it means reading packets that were meant for someone else. The usual tool is a packet sniffer, a program that records every packet it can see and shows what is inside. Network engineers use sniffers every day to find faults; the danger is what a sniffer reveals when traffic is not protected.
Unprotected traffic is like a postcard. Anyone who handles it on the way can read it without opening anything. Wi-Fi makes this easier, because radio signals spread in every direction: a laptop at the next table receives the same signals that Riya's laptop sends to the access point. If the café network has no Wi-Fi password, and so no Wi-Fi encryption, and the portal uses plain HTTP, Riya's password crosses the café as a postcard.
Plain HTTP is a postcard anyone on the path can read. HTTPS is a sealed envelope: the address on the outside still shows, but not what is inside.
HTTP is the language browsers and websites use to talk to each other, and HTTPS is the same language wrapped in encryption. Encryption scrambles data with a secret value called a key, so that only the two ends of the conversation can unscramble it. With HTTPS the postcard becomes a sealed envelope. An eavesdropper still learns which site you are talking to and roughly how much data moves, but not the pages, the passwords or the medicine names inside.
Encryption hides what you say, not the fact that you are talking to a particular site.
Pretending to be someone else: spoofing
Spoofing means faking an identity so that a message or device looks as if it comes from someone trusted. It is the network version of a caller who says "I am calling from your bank" while the screen shows a number that looks right. Many network messages carry a sender's address that the receiver simply believes, because the early internet assumed everyone on it was honest.
Attackers fake many kinds of label: the sender address on packets (IP spoofing), the 'From' line of an email, the name a Wi-Fi hotspot announces, or the answer to a directory lookup. DNS, the Domain Name System, is the internet's phone directory: your phone asks it "where is tulsihealth.in?" and gets back an IP address. A forged answer quietly sends you to the attacker's server instead. The defence against every kind of spoofing is to check a claimed identity with something that cannot be copied easily. For websites that check is the site's certificate, for email it is a set of sender checks run by the mail service, and for a phone call it is calling back on a number you already know.
The fake postman: man-in-the-middle attacks
A man-in-the-middle (MITM) attack puts the attacker between two parties, so that each believes it is talking directly to the other. Picture a fake postman who collects your letters, reads them, changes the account number on a cheque and reseals them before delivery, so nobody suspects a thing. On a network, spoofing is how the attacker gets into the middle: a hotspot with the café's name, a forged DNS answer, or a false claim to be the router. From then on, every packet passes through the attacker's device.
The attacker can read, change or drop anything in either direction, which threatens confidentiality, integrity and availability at once.
HTTPS defeats most of these attacks because of the certificate, a digital identity card that a trusted authority issues to a website and that only the real site can use. Your browser checks it on every visit. A man-in-the-middle cannot present the real portal's certificate, so the browser stops with a full-page warning. That warning is the moment the attack succeeds or fails: if you press "proceed anyway", you hand the attacker the conversation. Attackers also try to keep victims on plain HTTP, which is why using the official app or typing the https:// address yourself beats following links.
Step through the same café attack twice below, once against a plain HTTP portal and once against an HTTPS site. Some steps stop and ask what you expect, so decide before you reveal.
A wrong flat number in the society directory: ARP poisoning
Inside a local network, such as one store or one café, devices use a second kind of address. Every network card has a MAC address, a hardware ID such as 3C:52:82:1A:9F:04 set at the factory. Packets cross the internet using IP addresses, but on the last stretch inside a local network they are delivered to MAC addresses. The Address Resolution Protocol (ARP) is how a device asks the local network "who has the router's IP address?" and learns which MAC address to deliver to. Each device remembers the answers in a short list called its ARP table.
Think of the directory board at a housing society's entrance, listing each resident's flat. Couriers trust it completely. Now suppose someone pastes a slip over the main gate's entry so that it shows their own flat, C-9. Every parcel that should leave through the gate now goes to C-9 first, where it is opened, read and passed on. ARP poisoning, also called ARP spoofing, is this trick: a device on the local network sends false ARP answers claiming that the router's IP address belongs to its own MAC address. ARP has no way to check who is telling the truth, so the other devices update their tables and start sending their traffic through the attacker.
ARP poisoning is a wrong flat number pasted into a directory everyone trusts. Traffic still arrives, so nobody notices the detour.
ARP poisoning only works for someone already on the same local network: a guest on a store's Wi-Fi, an infected laptop, or a stranger at the café. Keeping the guest Wi-Fi separate from staff devices means a guest can never reach the billing laptops in the first place. Better network switches, the boxes that connect wired devices inside a building, can check every ARP answer against a list of known addresses and drop false ones. Monitoring tools can also alert when the router's address suddenly changes owner.
Keeping the envelope sealed
Every interception attack has the same weakness: an attacker in the middle gains little if the traffic is encrypted and the other end's identity is checked. For Tulsi Health staff and customers that becomes a few habits. Use HTTPS sites and the official Tulsi Health app, and never click past a certificate warning. On a network you do not trust, use mobile data or a VPN (virtual private network), which wraps all of your traffic in an encrypted tunnel to a trusted server. Turn on two-step login so that a stolen password is not enough on its own, and keep guests on a network of their own.
The sorting below checks the most important idea: what an eavesdropper on the café Wi-Fi can and cannot read. Decide for each item before you check it.