<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Advanced Topics :: CRS Documentation</title><link>https://8192de7b.documentation-km5.pages.dev/5-advanced-topics/index.html</link><description>The content here doesn’t fit anywhere else just yet. This whole section will probably be reworked and is only temporary.</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://8192de7b.documentation-km5.pages.dev/5-advanced-topics/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-Contained Mode</title><link>https://8192de7b.documentation-km5.pages.dev/5-advanced-topics/5-1-self-contained-mode/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://8192de7b.documentation-km5.pages.dev/5-advanced-topics/5-1-self-contained-mode/index.html</guid><description>Self-Contained Mode Traditional Detection Mode (deprecated) The default mode in CRS 3.x is Anomaly Scoring mode, you can verify this is your mode by checking that the SecDefaultAction line in the crs-setup.conf file usees the pass action:
SecDefaultAction "phase:2,pass,log" Warning From version 3.0 onwards, Anomaly Scoring is the default detection mode. Traditional detection mode is discouraged.</description></item><item><title>Log Handling</title><link>https://8192de7b.documentation-km5.pages.dev/5-advanced-topics/5-2-log-handling/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://8192de7b.documentation-km5.pages.dev/5-advanced-topics/5-2-log-handling/index.html</guid><description>A 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.</description></item><item><title>Kubernetes Ingress Controllers</title><link>https://8192de7b.documentation-km5.pages.dev/5-advanced-topics/5-3-kubernetes-ingress-controller/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://8192de7b.documentation-km5.pages.dev/5-advanced-topics/5-3-kubernetes-ingress-controller/index.html</guid><description>A 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.</description></item></channel></rss>