Citrix Blogs

How can Citrix help protect your APIs?

We live in an app and API economy. According a report from Akamai, 83 percent of all web traffic today is API traffic. Though API usage grown exponentially, adoption of security practices to protect APIs lags.

APIs face a unique set of security risks and challenges that go beyond a traditional web application. For example, attackers can gain access to an account by either brute force or stolen credentials. And because APIs, by design, enable automation, they can be prone to automated attacks, especially by attackers using stolen credentials obtained through a third-party breach.

Another area of concern? Broken authorization. Attackers can leverage broken authorization flaws in APIs to obtain sensitive user information after a successful legitimate login. Rate limiting, in combination with stronger authentication and authorization policies for APIs, can help mitigate such automated attacks.

To help security admins address these unique security risks, the Open Source Web Application Security Project (OWASP) recently began publishing top threats facing APIs — the OWASP API Security Top 10. In this blog post, we’ll look at each of the Top 10 threats and how Citrix ADC can help to protect your APIs.

API1:2019 Broken Object Level Authorization

APIs tend to expose endpoints that handle object identifiers, creating a wide attack surface level access control issue. Object level authorization checks should be considered in every function that accesses a data source using an input from the user.

How Citrix ADC can help:

API2:2019 Broken User Authentication

Authentication mechanisms are often implemented incorrectly, allowing attackers to compromise authentication tokens or to exploit implementation flaws to assume other users’ identities temporarily or permanently. This can compromise a system’s ability to identify the client/user and the overall API security posture.

How Citrix ADC can help:

API3:2019 Excessive Data Exposure

Looking forward to generic implementations, developers tend to expose all object properties without considering their individual sensitivity, relying on clients to perform the data filtering before displaying it to the user.

How Citrix ADC can help:

API4:2019 Lack of Resources and Rate Limiting

Frequently, APIs impose no restrictions on the size or number of resources that can be requested by the client/user. This can have an impact on API server performance, leading to denial of service (DoS) and leaves the door open to attacks such as brute force.

How Citrix ADC can help:

API5:2019 Broken Function Level Authorization

Complex access control policies with different hierarchies, groups, and roles, as well as an unclear separation between administrative and regular functions, tend to lead to authorization flaws. By exploiting these issues, attackers gain access to other users’ resources and/or administrative functions.

How Citrix ADC can help:

API6:2019 Mass Assignment

Binding client-provided data (e.g., JSON) to data models without sufficient property filtering based on a permit list usually leads to mass assignment. Guessing an object’s properties, exploring other API endpoints, reading the documentation, or providing additional object properties in request payloads allows attackers to modify object properties they aren’t supposed to.

How Citrix ADC can help:

API7:2019 Security Misconfiguration

Security misconfiguration is a common result of unsecure default configurations, incomplete or ad-hoc configurations, open cloud storage, misconfigured HTTP headers, unnecessary HTTP methods, permissive cross-origin resource sharing (CORS), and verbose error messages containing sensitive information.

How Citrix ADC can help:

API8:2019 Injection

Injection flaws such as SQL, NoSQL, and command injection occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s malicious data can trick the interpreter into executing unintended commands or accessing data without proper authorization.

How Citrix ADC can help:

API9:2019 Improper Assets Management

APIs tend to expose more endpoints than traditional web applications, making proper and updated documentation highly important. Proper hosts and deployed API versions inventory also play an important role in mitigating issues such as deprecated API versions and exposed endpoints.

How Citrix ADC can help:

API10:2019 Insufficient Logging and Monitoring

Insufficient logging and monitoring, coupled with missing or ineffective integration with incident response, enables attackers to further attack systems, maintain persistence, pivot to more systems to tamper with, and extract or destroy data. Most breach studies demonstrate the time to detect a breach is over 200 days, and they’re typically detected by external parties rather than internal processes or monitoring.

How Citrix ADC can help:

If you would like to learn more about how Citrix can help manage and protect your APIs, please reach out to your account team to schedule a demo. If you are an existing Citrix Application Delivery Management service customer and would like to enable API Gateway features on your instance, please reach out to the Citrix Application Security Product Management team at appsec-pm@citrix.com.

Exit mobile version