I'm kind of partial to kestrel myself. ;)
Printable View
I'm kind of partial to kestrel myself. ;)
Blasphemy! :lolQuote:
Originally Posted by jcoehoorn
Im trying to find a way to implement this in our company but i dont know how...
At this moment we have a business licence with Untangle that works totally fine. Behind untangle is our web server but i dont have internet ip to the web server, i just port forward some ports to it and is working fine.
How i can implement WAF in the middle of untangle and the webserver? or i dont need it and untangle allready does the same job?
never mind. I understood how it works. I changed the port forwards in Untangle firewall to the WAF appliance and then in the appliance i said that upstream server is the internal web server and is working fine.
Yes that's right. Unlike NG Firewall, Untangle Web Application Firewall does not require multiple interfaces. It can reside anywhere, it just needs an IP address. By directing traffic through the WAF you are processing requests through the OWASP ModSecurity set of rules, which is something like IPS but specifically for web services.Quote:
Originally Posted by bluechris
As i see it, it can control http and https requests correct? i dont see ftp or anything else for example.
Also 1 day now everything is passed, i mean i see no blocking in something but i assume since i have untangle infront with threat prevention and intrusion prevention on, any kind of attack stops in Untangle.
I will bypass the web server from untangle to see if it blocks anything today.
So when and how can I beta test this :-)
https://forums.untangle.com/web-appl...you-think.htmlQuote:
Originally Posted by WebFooL
And so to confirm, the thinking is this will NOT be an add-on app to the UT Firewall? Meaning this will go to production as a standalone software that could be a VM.
WAF is a separate product which uses docker as a platform. It will not be part of UT NGFW.