\n
![](\"https:\/\/jirak.net\/wp\/wp-content\/uploads\/2019\/04\/API-management-security-patch-timeline.png\")
<\/p>\nIs Your API Management Solution Really Secure?
\n<\/p>\n
NGINX is the industry\u2019s most ubiquitous API gateway, an infrastructure component that processes API traffic in API management<\/a> solutions like those from Apigee, Axway, IBM DataPower, Kong, Red Hat 3scale<\/span>, and Torry Harris. Combine that with the fact that more than 40% of the users we surveyed in 2018 have deployed NGINX Plus as an API gateway<\/a>, it\u2019s fair to say that NGINX is processing most of the world\u2019s API traffic. That\u2019s not too shabby, considering that Akamai puts API traffic at 83% of the world\u2019s Internet traffic<\/a>.<\/p>\n Why is NGINX so ubiquitous in the world of APIs? Because NGINX delivers high performance, security, and authentication services – all critical to your API environment. NGINX prevents DDoS attacks by enforcing rate limits on requests or bandwidth limits on specific users, and NGINX Plus provides authentication and fine‑grained access control to protect API‑based services.<\/p>\n The bottom line is that an API gateway is a critical component in overall API security. But you need to ask yourself: how secure is your API gateway itself? This blog explains why the security of the API gateway is important and how to think about the risk of exploiting it. <\/p>\n All the API management solutions listed above either use a customized version of NGINX Open Source or (as in the case of Kong) are built on third‑party modules such as OpenResty. OpenResty is an extensible and flexible platform based on NGINX and LuaJIT that is widely used by developers for customization and for certain use cases. Although OpenResty is fast, it\u2019s not as fast as native NGINX with raw configuration files and no Lua modifications. <\/p>\n Further, solutions built using OpenResty can potentially leave you exposed to critical vulnerabilities. Consider a situation where the NGINX team discovers a critical vulnerability. Although rare, there have been five such vulnerabilities over the last three years. When such an issue is found in NGINX, all our customers using NGINX Plus receive a patch as soon as our engineering team fixes this issue. Our open source users receive this patch and the CVE notification usually within a week or two. <\/p>\n What about modified NGINX builds like OpenResty? Despite the best efforts of the OpenResty team, it is entirely reasonable to expect some delay as it takes time to qualify, port, and test bug fixes. Then this delay cascades through dependent products such as Kong which are even further from the base NGINX software. <\/p>\n As an example, for three CVEs (CVE-2018-16843<\/a><\/span>, CVE-2018-16844<\/a><\/span>, CVE-2018-16845<\/a><\/span>) discovered in fall 2018, we applied two security patches to NGINX Plus R16<\/span> on October 30, and to NGINX Open Source 1.15.6 on November 6. OpenResty issued a release candidate on March 3, 2019<\/span> that incorporated these patches. Solutions built on top of OpenResty such as Kong consequently take even longer to patch their codebase. In Kong\u2019s case, they don\u2019t even seem to share the same sense of urgency as OpenResty does in patching their core – the last CVE update incorporated by Kong was back in March 2018! <\/p>\n This leaves a substantial window of opportunity for bad actors to exploit these solutions, with your APIs, applications, and backend servers and processes all exposed. A key function of your API management solution – providing security – can be compromised. <\/p>\n The figure illustrates typical timeframes we’ve observed for recent CVE patches to API management solutions built on top of NGINX Open Source. Security patches are immediately applied to NGINX Plus and NGINX Open Source. The timeframe for integrating NGINX patches is completely up to OpenResty and API management solutions such as Kong that use NGINX Open Source. <\/p>\n With the rise of the API economy, trust becomes central to your API ecosystem consisting of third‑party developers, suppliers, distributors, resellers, and even customers. Trust is an important concern for API architects, developers, I&O, and DevOps teams, and a core tenet of the NGINX Controller API Management Module<\/a>. We provide you with the peace of mind and assurance that security issues discovered in NGINX Plus (the underlying gateway that handles API traffic in our API management solution) are addressed immediately. <\/p>\n Do you know if your API management solution is built on NGINX? If so, do you know if your solution has incorporated all the latest security patches? We\u2019d love to hear from you in the comments below. In the meantime, if you\u2019re ready to go with a more trusted and secure solution, then get started with a free 30‑day trial of NGINX Controller<\/a>.<\/p>\n The post Is Your API Management Solution Really Secure?<\/a> appeared first on NGINX<\/a>.<\/p>\n Source: Is Your API Management Solution Really Secure?<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Is Your API Management Solution Really Secure? NGINX is the industry\u2019s most ubiquitous API gateway, an infrastructure component that processes API traffic in API management solutions like those from Apigee, Axway, IBM DataPower, Kong, Red Hat 3scale, and Torry Harris. Combine that with the fact that more than 40% of the users we surveyed in 2018 have deployed NGINX Plus as an API gateway, it\u2019s fair to say that NGINX is processing most of the world\u2019s API traffic. That\u2019s not too shabby, considering that Akamai puts API traffic at 83% of the world\u2019s Internet traffic. Why is NGINX so ubiquitous in the world of APIs? Because NGINX delivers high performance, security, and authentication services – all critical to your API environment. NGINX prevents DDoS attacks by enforcing rate limits on requests or bandwidth limits on specific users, and NGINX Plus provides authentication and fine‑grained access control to protect [ more… ]<\/a><\/p>\n<\/div>","protected":false},"author":1,"featured_media":30641,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[169],"tags":[652],"class_list":["post-30640","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-nginx"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/30640","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/comments?post=30640"}],"version-history":[{"count":1,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/30640\/revisions"}],"predecessor-version":[{"id":30642,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/30640\/revisions\/30642"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/media\/30641"}],"wp:attachment":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/media?parent=30640"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/categories?post=30640"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/tags?post=30640"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Bare Naked API Management Solutions<\/h2>\n
![\"\"](\"https:\/\/www.nginx.com\/wp-content\/uploads\/2019\/04\/API-management-security-patch-timeline.png\")
<\/p>\nPeace of Mind with NGINX\u2019s API Management Module<\/h2>\n