Which is an all in one very powerful solution... With near wire speed transfer.
I don't know why I should get that?
31–40 of 90 posts
Which is an all in one very powerful solution... With near wire speed transfer.
I don't know why I should get that?
I have never heard someone pronounce nginx "n-jinks" before like they did in their video. It's a minor thing, but it hurts their credibility in my eyes.
Wallarm looks like a fairly good WAF, and focused on developers / DevOps. We ( https://www.tinfoilsecurity.com ) have the same focus, but are focused on helping you find and fix the vulnerabilities rather than cloaking them / trying to catch them being exploited in real-time. "Detect anomalies and block attacks with no latency" seems hard to believe - minimal latency, maybe, but none? On the other hand, good luck to…
http://modsecurity.org/ is an open source option with free and commercial rules. I remember reading that CloudFlare used ModSecurity at one point and then moved to their own WAF.
I have never heard someone pronounce nginx "n-jinks" before like they did in their video. It's a minor thing, but it hurts their credibility in my eyes.
To be fair, this is due to the horrible branding on NginX's part. Nearly every non-technical person I know has pronounced it njinks, because using 'n' phonetically as 'en' is not exactly commonplace. Watching our PM get to their name in a story and pause for a few seconds and just say "that word" instead should give you some idea of how counter-intuitive it is. You don't have to work hard to parse good branding.
I really like this idea and I've started using Wallarm. - Integration is amazingly easy if you use nginx... basically an apt-get. - Unlike most security packages that just block certain ports or apply predefined rules, Wallarm feels like I have a dev-ops team looking at traffic patterns 24/7. They're always learning and they identify when things seem irregular. This is definitely the next level of network security
> Integration is amazingly easy if you use nginx... basically an apt-get.
What about the Wallarm Cloud?
> Unlike most security packages that just block certain ports or apply predefined rules, Wallarm feels like I have a dev-ops team looking at traffic patterns 24/7. They're always learning and they identify when things seem irregular.
What exactly does this mean? Are you implying that Wallarm uses machine learning and what criteria / data would it use in such a case? Alternatively is this referencing the Wallarm Cloud?
Typically infrastructure pieces are very, very well defined in what they do as they're critical (if it's too slow or not working correctly then you're business goes too slow or stops). If you have specifics of any of your claims it would be great to read.
One may also want to see NAXSI [0]. NAXSI is an open-source, high performance, low rules maintenance WAF for NGINX. [0] https://github.com/nbs-system/naxsi
I have never heard someone pronounce nginx "n-jinks" before like they did in their video. It's a minor thing, but it hurts their credibility in my eyes.
I mean, I know it's pronounced like engine-ex (just like it's Oh-Ess Ten, not Oh-Ess-Ex, or jif not gif), but when I'm just reading the word to myself it comes out n-jinks because fewer syllables.
2/10 troll, try harder.
I have never heard someone pronounce nginx "n-jinks" before like they did in their video. It's a minor thing, but it hurts their credibility in my eyes.
Might be due to the fact that for lots of ESL speakers, the "ine" in "engine" makes little sense when you consider "quine", "spine", "spline", "brine", etc. The cognitive load to recognize that nginx is really engine-x is that much bigger. As I like to say, "Give someone a ghoti, he can speak English for a day, tell them how to ghoti, and they can speak English for a lifetime".