> We share the source code of Wallarm Node (nginx-based filter instance) with the companies after signing NDA.

Is that because of the licensing terms of a certain underlying component that you use which forces you to share it?

It's because all the security guys (as we're) troll a lot and always skeptical (reasonably!) about blackboxes

> It's because all the security guys (as we're) troll a lot and always skeptical (reasonably!) about blackboxes

Why not open-source it then? In that event tt wouldn't be termed a blackbox either.

What do you mean "come up"? You made a commercial product and don't have a single use case or user story to pitch?

Why the negativity? I can think of a number of tech questions that no one but the deepest in the technical weeds on a team could provide actual answers to. Is deferring to someone else on a team to answer questions so bad?

There is quite a difference between technical questions and "what your product does, couple of examples where it's good at maybe?".

Lot's of stories happening right away. Don't get the reason for the negativity. Though here is a recent story — critical XXE with remote file reading at LinkedIn (http://blog.wallarm.com/post/145883562288/critical-linkedin-...)

This blog post has nothing to do with your product. Also, stopping a single request is very different from stopping an attack. A real attacker isn't going to stop the first time they get blocked, and if possible they'll probably end up evading your WAF.

It absolutely has. The vulnerability was detected with a vulnerability scanner built in Wallarm. As for detection of attacks, in many cases, it's much easier to identify the attacker when he runs several requests than to stop only one request with a ready-to-use 0day exploit. And what's even more important, you need help to fix vulnerability unless attacker discovers it and find the way to evade WAF