Cloudflare vs. NGINX vs. Salt Security API Protection Platform

Cloudflare works well as security measure that gives peace of mind without needing to work too hard to get it functioning well. It provides great tools to customize the security experience as well. This is all the same for the caching tools as well. They have a lot of built in tools that make using the caching easy right out of the box, but they provide the customization options to get things just right for your site.

Incentivized

Nginx is well-suited for any web server scenarios, such as web applications, backend or reverse proxy for both application and HTTP requests, and distribution. It is less appropriate for Windows-based applications that run directly on a Windows Server host. In any case, it is very easy to manage, through separate conf files for each application or site you want to host with it.

Incentivized

Salt is highly recommended for anyone who wants to discover, monitor and protect their APIs against various types of attacks. Salt should not be used as a SIEM.

• The best part is the content delivery network. Cloudflare has a large network of data centres around the world that helps cache and delivers content quickly to our customers.
• Cloudflare offers us with a fast and reliable DNS service and with the world class features such as Cloudflare workers, SSL verification, certificate management and web application firewall. When all of these are combined together, it provides very strict security for our organization.
• One of the most important feature that we use is the analytics and threat detection. It provides us with the real time insights of all the threats originating from multiple locations and landing on our websites.

Incentivized

• Very low memory usage. Can handle many more connections than alternatives (like Apache HTTPD) due to low overhead. (event-based architecture).
• Great at serving static content.
• Scales very well. Easy to host multiple Nginx servers to promote high availability.
• Open-Source (no cost)!

Incentivized

• PII identification in API traffic.
• Divergence between API traffic and documentation (swagger files).
• Potential attacks with information to take counter measures.

• In some cases, using Cloudflare can actually lead to slower website speeds if the network is congested or if the website's traffic is particularly heavy.
• Some website owners may find that the level of customization offered by Cloudflare is limited, especially in comparison to other solutions.
• While Cloudflare is easy to set up and manage, it may be too complex for users who are not familiar with web technologies.

Incentivized

• Customer support can be strangely condescending, perhaps it's a language issue?
• I find it a little weird how the release versions used for Nginx+ aren't the same as for open source version. It can be very confusing to determine the cross-compatibility of modules, etc., because of this.
• It seems like some (most?) modules on their own site are ancient and no longer supported, so their documentation in this area needs work.
• It's difficult to navigate between nginx.com commercial site and customer support. They need to be integrated together.
• I'd love to see more work done on nginx+ monitoring without requiring logging every request. I understand that many statistics can only be derived from logs, but plenty should work without that. Logging is not an option in many environments.

• The platform could have more options for exporting detailed data from attackers' dashboards.
• The Attackers dashboard could also have more options of filters in order to support the investigations of the attack.
• The OAS analysis could present a more detailed view of the found issues.

lower cost

Incentivized

Great value for the product

Incentivized

Everything is extremely concise and all settings apply immediately and take effect globally. There is no reason to explicitly plan/think in terms of individual regions as one would have to traditional cloud offerings (AWS, OCI, Azure). All Cloudflare products integrate seamless as part of a single pipeline that executes from request to response.

Incentivized

This tool is really easy to use and configure. Consumes very less system resources. It is highly modular and configurable. You can easily use it with other tools like certbot for SSLs. You can configure basic security with configuration and headers

Incentivized

In 6+ years of relying on Cloudflare, I think we experienced one or two brief outages that were Cloudflare's fault.

Incentivized

Their Argo for the global network is the core feature we love.

Incentivized

Excellent product, Cloudflare is a true pioneer of the modern Internet, providing tools, services, and expertise that vastly improve the performance and security of web services. Any issues are resolved quickly with detailed RCA and follow-ups published publicly. I'm thankful to Cloudflare and use their services both at work and at home.

Incentivized

Community support is great, and they've also had a presence at conferences. Overall, there is no shortage of documentation and community support. We're currently using it to serve up some WordPress sites, and configuring NGINX for this purpose is well documented.

Incentivized

Very well executed implementation where our team was able to handle the implementation with guidance.

Incentivized

They have the most generous free offering, and after the free offering limit is reached - you're still getting plenty of value for the buck.

They have very good reputation.

They have an ever expanding list of tools that can support multiple scenarios under one roof.

Incentivized

I have found that [NGINX] seems to perform better throughout the years with less issues although I've used Apache more. I would definitely recommend [NGINX] for any high volume site and I've seen this to usually be the case from most provided web hosts who will pick [NGINX] over alternatives

Incentivized

We tried controls offered by the IaaS providers but these were hard to manage and did not provide the visibility we wanted. We also protected APIs with a normal WAF but this was only helpful for assets we knew about and API attacks were not caught by the WAF.

They are built for scale and have the capacity to handle all the traffic we could ever expect to get.

Incentivized

• Immediate ROI on Registrar and DNS hosting while giving a single plane of glass to managing both with domain registrations at cost, and no cost DNS hosting
• WAF helped us move at risk servers/applications into a protected state allowing us to perform remediations at a measured pace and get them done right instead of band aide solutions.
• CDN proxying increase the speed of our website while simultaneously reducing server load.
• DMARC management and report interpretation allow use to identify weak points in our email systems, remediate and move to stricter policies without significantly increasing staff time spent managing it.

Incentivized

• By using Nginx, we can host multiple web services on a single server, keeping our infrastructure costs lower.
• Nginx maintains our HTTPS connections, allowing us to keep our promise to our customers that their data is safe in transit.
• Due to Nginx's extremely low failure rate, our web addresses always return something meaningful, even when individual services go down. In sense, this means we are "always online" and allows us to maintain brand and support our customers even in the face of catastrophe.

Incentivized

• Salt Security API Protection Platform has provided detailed information that is helping us to identify and investigate attacks in our environment