Meet the Expert: Updates to OWASP API Security Top 10

Michael Kan-Tor from Upstream Research covers the recent updates to the OWASP API Security Top Ten risks. Reviewing all ten risks, the new and the old as well as providing examples of how these risks can be leveraged in a cybersecurity attack using an API vulnerability to either disrupt business operations or access sensitive data. This much-awaited update to the list, whose last version was released in 2019, provides additional clarity on the API security threats that organizations relying on APIs must safeguard against.


API 1: Broken Object Level Authorization
Maintained from 2019 edition, this refers to cases where APIs expose objects to potential attackers that they are not authorized to access.

API 2: Broken Authentication
Same as 2019. It involves cases where a broken authentication mechanism allows potential attackers to bypass that mechanism and gain unwarranted authentication to the core API service.

API 3: Broken Object Property Level Authorization
A new category combining excessive data exposure and mass assignment categories from the old list. It relates to instances where APIs expose specific properties of objects to unauthorized consumers.

API 4: Unrestricted Resource Consumption
Unchanged from the 2019 list, this refers to cases where APIs allow consumers to consume excessive resources, potentially causing denial of service and high loads on the API.

API 5: Broken Function Level Authorization
A repeat category from the 2019 list. This category refers to instances where specific functionality in the API is vulnerable to potential attackers who can access it without proper authorization.

API 6: Unrestricted Access to Sensitive Business Flows
A new category, it relates to situations where a business flow is vulnerable to attacks.

API 7: Server Side Request Forgery (SSRF)
Previously part of the injection category, SSRF is now its own category and it’s a well-documented attack vector.

API 8: Security Misconfiguration
Retained from the 2019 edition, it covers instances where misconfigurations in the server can cause security vulnerabilities.

API 9: Improper Inventory Management
This category refers to cases where different versions of APIs or API assets are incorrectly managed, allowing potential attackers to exploit outdated API versions.

API 10: Unsafe Consumption of APIs
This category relates to instances where an API consumes other unsafe APIs, potentially compromising the core API.

Newsletter Icon

to our newsletter

Stay up-to-date on the latest trends, emerging risks, and updates

Watch: Scaling Software-Defined Vehicle Security, without Increasing Costs

In this webinar, Upstream and BlackBerry IVY's experts discuss the role of synthetic sensors in automotive cybersecurity and how to reduce cloud computing and data…

More Details

Secure Connected IoT Devices in the Mobility & Transportation Ecosystem

More Details

Scaling Software-Defined Vehicle Security, without Increasing Costs

Connected and software-defined vehicles generate vast amounts of data – upwards of 25 GB an hour per car. To help make sense of this data…

More Details

Watch: The automotive cybersecurity inflection point in 2024: from experimental to massive-scale attacks

In this webinar, Upstream experts share significant findings from Upstream’s 2024 Global Automotive Cyber Trends Report, providing insights and predictions for 2024.

More Details

The Upstream Platform

Monitor, secure, optimize, and enhance connected vehicles, fleets, and applications with a purpose-built, cloud-based data platform.

More Details

Canopy Selects Upstream to Safeguard Its Advanced Vehicle IoT Security Systems

More Details