https://79653653.documentation-km5.pages.dev/5-advanced-topics/index.htmlThe content here doesn’t fit anywhere else just yet. This whole section will probably be reworked and is only temporary.Hugoen-ushttps://79653653.documentation-km5.pages.dev/5-advanced-topics/5-1-self-contained-mode/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://79653653.documentation-km5.pages.dev/5-advanced-topics/5-1-self-contained-mode/index.htmlSelf-Contained Mode Traditional Detection Mode (deprecated) The default mode in CRS is Anomaly Scoring mode. You can verify this is your mode by checking that the SecDefaultAction lines in the crs-setup.conf file use the pass action. Since CRS 4.28.0 a default is set for every phase:https://79653653.documentation-km5.pages.dev/5-advanced-topics/5-2-log-handling/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://79653653.documentation-km5.pages.dev/5-advanced-topics/5-2-log-handling/index.htmlA full operational guide on how to handle and consume the logs emitted by CRS and its compatible WAF engines will be written in the future.https://79653653.documentation-km5.pages.dev/5-advanced-topics/5-3-kubernetes-ingress-controller/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://79653653.documentation-km5.pages.dev/5-advanced-topics/5-3-kubernetes-ingress-controller/index.htmlA Kubernetes cluster can use different types of ingress controllers to expose Kubernetes services outside the cluster. Some ingress controllers include built-in support for using CRS, as this page outlines. NGINX Ingress Controller The NGINX Ingress Controller is built around the Kubernetes Ingress resource. It uses a ConfigMap to store the controller configuration. Refer to the official Kubernetes documentation to learn more about using the Ingress resource.