About this interactive
Sometimes the thing connecting to a server is not a person viewing a page but another application. A SaaS company selling contact lists, for example, wants its customers' servers to request, submit and change information. It publishes an application programming interface (API): the credentials to use, the calls to make, and the format of the answers.
That deeper connection needs securing, and the lesson names three controls. Authorization: most APIs should not let just anybody connect, so it decides who may call and what they may do. Logging: record the activity, so if anything goes wrong you can go back and see what happened. Rate limiting: if a client dumps all of the contents at once, it can fill the bandwidth, spike the CPU and fill memory, so each client is held to a certain amount at a time.
An API gateway is the front door for all this: essentially a reverse proxy out front, perhaps a hardened bastion host, that clients connect to and that fetches the answers from the servers behind.
About TechKnowSurge
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →