![]() ![]() These should help you identify any WAF rule matches. Opción 2: Implementación manual de Azure Functions. To view these logs, use the following command: podman logs owasp-crs-demo-pod-0-owaspcrsexampleįrom here, it may seem like a lot of jibberish, but if you copy out the Nginx access logs, you can use Vim and python -m json.tool to parse the JSON so it's readable. Then I ran the bash script in the OP description. ![]() │ └── modsecurity-crs-finding-output.yaml │ ├── modsecurity-crs-finding-output.json My philflaskapp is located here: ➜ k8s-owasp-crs-examples git:(main) podman play kube -build -replace k8s-owasp-crs-setup.yaml I then used the following command to bring up the Pod. Image: docker.io/owasp/modsecurity-crs:nginx-alpine So, I created this Kubernetes Deployment Manifest to have Podman play. I used the solution proposed by here to figure out how to run the docker.io/owasp/modsecurity-crs:nginx-alpine container using Podman to test my calls. Why are these being blocked for seemingly innocent strings? Then the second example: #!/usr/bin/env bash The above curl command works if I remove the > and replace it with >. header 'Content-Type: application/json' \ I took the JSON document and put it into a function. Note: These curl commands were generated by Postman. So the question is, why are these requests being blocked by a WAF? I believe these are seen by the WAF as XSS or SQL Injection attacks, but I don't have a way to prove it. Since moving it to Azure, users and testers are now getting 403 Forbidden when attempting to send data to the service. I have an application running behind an Azure Web Application Firewall (WAF) on an Azure Application Gateway (AppGW) that was previously on an on-premises server.
0 Comments
Leave a Reply. |