An application programming interface (API) has recently undergone a new release, and sensitive functions are no longer restricted appropriately. Which of the following is the MOST likely reason?

The correct answer is A. Broken object-level authorization. The most likely reason for sensitive functions no longer being restricted appropriately after a new API release is broken object-level authorization. This occurs when the API fails to properly enforce access controls, allowing unauthorized users to access or perform actions on…

Submitted by ricky.ec· Apr 18, 2026Information Systems Acquisition, Development, and Implementation

Question

Options

ABroken object-level authorization
BTrojan horses
CPortability flaws
DErratic version control

How the community answered

(27 responses)

A
81% (22)
B
11% (3)
C
4% (1)
D
4% (1)

Explanation

The most likely reason for sensitive functions no longer being restricted appropriately after a new API release is broken object-level authorization. This occurs when the API fails to properly enforce access controls, allowing unauthorized users to access or perform actions on sensitive functions or data. This is a common security vulnerability, often resulting from improperly handled access checks or missed authorization logic during the development or release of new API

Topics

#API Security#Authorization#Security Vulnerability#Application Security

Community Discussion

No community discussion yet for this question.

Full CISA Practice