Why security moves to the cloud
What you will learn
This track teaches you to run a cloud security service the way a Cloud Security Access Engineer does: send traffic to it, write policy, read logs and fix tickets. In this first module you learn the vocabulary and the portal. By the end of this chapter you can explain, in plain words, why companies stopped putting one big firewall at head office and started buying security as a cloud service.
Prerequisites: you know what an IP address is, what a browser does when you type a website name, and the idea of a firewall as a gatekeeper. Nothing else. We build the rest from scratch.
An analogy: one gate versus a checkpoint at every door
Old offices were like a walled fort with one gate. Everyone worked inside, guards at the gate checked everything, and anyone outside the wall was a stranger. Today the staff are in three cities and at home, and the work lives on websites run by other companies. Making everybody walk back to the fort gate for every request is slow. A cloud security service puts a checkpoint near each person, and the same rule book is used at every checkpoint.
Four words you must know
- Proxy
- A middleman. Your browser asks the proxy to fetch a page, the proxy talks to the website and hands the answer back. Because it sits in the middle, it can allow, block or log the request. A proxy that protects users on their way out to the internet is called a secure web gateway.
- Tunnel
- Packets placed inside other packets so they can cross a network to a chosen endpoint. Think of a sealed courier bag travelling inside a delivery van.
- DNS
- The phone book of the internet. It turns a name such as news.example into an IP address. Many security decisions start from the name or its category.
- TLS
- The encryption used by HTTPS. The server shows a certificate to prove who it is, then both sides encrypt the conversation. Encryption protects privacy but also hides content from a firewall. Module zs-sec returns to this in depth.
The old design: backhaul everything to head office
Sahyadri Logistics has Pune HQ, a Chennai branch and a Jaipur branch. In the old design every branch sent all internet traffic over a private link to Pune. One firewall and one proxy in the Pune server room inspected it, then released it to the internet. This worked while applications lived in the Pune server room.
It breaks in three ways. First, applications moved to websites on the internet, so the detour through Pune only adds delay. Second, people moved: vikram works from home and is not on any branch link. Third, most traffic is encrypted, and the old box could not afford to open all of it.
The checkpoint moves from the Pune server room to a cloud edge near every user.
Worked example. A Jaipur user opens a software-as-a-service site. Direct, the round trip is about 25 ms. Backhauled, Jaipur to Pune adds about 45 ms and Pune to the site adds 25 ms: 70 ms for every request, and a page makes dozens. With a nearby cloud node the path stays close to the direct time plus a few milliseconds of inspection. These numbers are examples; yours depend on the circuits.
The new design for Sahyadri
Each location chooses a way to forward traffic to the cloud service: Pune uses an IPsec tunnel, Chennai a GRE tunnel, Jaipur a PAC file (an explicit proxy setting) and vikram a client program on his laptop. Module zs-fwd teaches these four. Policy no longer lives in the Pune firewall; it lives in one admin portal and applies to everybody.
What does this change on the wire/policy? Moving a site from backhaul to cloud security changes where its web traffic exits. Before, it left through the Pune firewall, which logged it. After, it leaves through a cloud node, and the Pune firewall sees only a tunnel. If you forget to forward a site, its traffic goes direct: no policy, no inspection and no logs.
Common mistakes. (1) Thinking cloud security means "no firewall at the site"; the edge firewall still exists and decides what may leave. (2) Believing the cloud service sees traffic that was never forwarded to it. (3) Mixing up a proxy (a middleman for one application protocol) with a tunnel (a carrier for any packets).
Exam trap. "Does cloud security remove the need for a firewall?" No. The device at the site still protects the LAN; cloud security adds a shared checkpoint for internet and private-application access.
The Jaipur page that took ten seconds
Sales in Jaipur complained that the quotation website was slow every afternoon. The engineer found all branch traffic crossing the Pune link, which was busy with backups. Moving Jaipur to the cloud service took the web traffic off that link. The same page now opened in under two seconds, and the Pune link became free for the ERP.
Lesson: backhaul turns one busy link into everyone's bottleneck.
"Why are companies moving from data-centre firewalls to cloud security?"
Strong answer: applications and users are now outside the data centre, so backhauling traffic adds latency and cost and leaves home users out. A cloud service puts the checkpoint near the user and keeps one policy for all locations. Mention encryption: more traffic is TLS, so inspection capacity matters. Add that you still need an edge firewall at each site.
Key takeaways
- A proxy is a middleman; a tunnel is a carrier; DNS maps names to IPs; TLS encrypts HTTPS.
- Backhaul sends all branch traffic to head office, which adds delay and ignores remote users.
- Cloud security puts one shared checkpoint near every user, with one policy.
- Sahyadri forwards Pune by IPsec, Chennai by GRE, Jaipur by PAC and vikram by client connector.
- Traffic that is not forwarded goes direct and is completely unprotected.