Felipe Zipitría
Felipe Zipitría
There are two problems: - how we create the container image, which for the nginx case needs to write files around. - the logs must be written somewhere The second...
The [nginx ingress controller](https://docs.nginx.com/nginx-ingress-controller/configuration/security/) solves the first part by ... copying everything to a mounted directory: ``` # volumes: # - name: nginx-etc # emptyDir: {} # - name: nginx-cache...
Latest pushed images should include the fix (E.g. ghcr.io/coreruleset/modsecurity-crs:3.3.5-nginx-202402070602), so please check and come back if something is not working.
You are right. Why I thought this was fixed? 🤔 Nevermind. Thanks for bringing this one back.
Maybe we can add a similar chart with examples for k8s?
It this going to be merged? I think most windows users will benefit from it.
I do not think we will have lots of rules getting data from remote monitoring. If we have remote monitoring, they will be GETting correct URLs with a reasonable User-Agent....
We are going to use only 127.0.0.1. Forget about anything else. I'm changing the text above.
Done. Also, I'm not comfortable with using ``` ctl:ruleEngine=Off,\ ctl:auditEngine=Off" ``` for these cases. I think we need to see the common rules that will match, likely 920350, and add...
Will push soon some of the data I've got for this one.