Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
An API is a defined window through which software exchanges data. The name stands for application programming interface. The Ministry of Internal Affairs and Communications, in its Cybersecurity Site for the Public, describes it as a mechanism for input and output that one piece of software exposes to another. The NIST glossary defines it as an entry point that can be called with a defined syntax and used from an application's program.
How does an API work?
Think of a hotel front desk. A guest gets things done by asking the desk, through a fixed procedure, without entering the kitchen or the storeroom. The guest does not need to know what happens behind the scenes.
On a site, an API is used when a booking system pulls in information from a map or weather service, or when a smartphone app fetches member data. The side that provides it decides the operations that can be used and how to call them, and publishes them. For a window you publish, you also need to decide who is allowed to call it.
The OWASP API Security Top 10 (2023 edition) organizes the main risks to APIs into ten items. The first is broken object-level authorization, and the second is broken authentication.
The wider reasoning is in the page on API authentication. Pages as visitors see them can be looked at through the free URL check.
Why do APIs matter?
An API can be called directly, without a screen. If the screen hides something but the window itself performs no check, there is no protection.
The OWASP list also includes a weak grasp of the windows you expose, ranked ninth. It is worth listing once how many windows your company exposes, and whether any old ones remain.
Ask your production company for the list of windows exposed, the authentication method, and who can use them. If the answers are vague, treat that as a candidate for review.
Related terms
- REST API: a kind of window through which systems exchange data
- IDOR: a flaw where changing a number shows another person's information
- Rate limiting: a mechanism that refuses a flood of requests in a short time
- CORS: a mechanism that permits data use from another site
Frequently asked questions
Is API a word only programmers need to know?
Operators benefit from knowing it too. APIs sit behind booking and payment links and smartphone apps, and the safety of a window you expose is also the operating side's responsibility. Ask your production company which windows you expose.
Does exposing an API increase risk?
More windows mean more places to protect. OWASP lists weak inventory of the windows you expose among the main risks. Narrow what you publish, and decide who may call it.
Next step
Authentication and permission for each window are covered on the API authentication page. If you want to discuss the windows you expose, contact us.
Frequently asked questions
Is API a word only programmers need to know?
Operators benefit from knowing it too. APIs sit behind booking and payment links and smartphone apps, and the safety of a window you expose is also the operating side's responsibility. Ask your production company which windows you expose.
Does exposing an API increase risk?
More windows mean more places to protect. OWASP lists weak inventory of the windows you expose among the main risks. Narrow what you publish, and decide who may call it.