You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/security/application_security/setup/nginx/ingress-controller.md
+38Lines changed: 38 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,9 +73,47 @@ the oTel and Datadog modules.
73
73
74
74
To disable OpenTelemetry, set `enable-opentelemetry: false`.
75
75
76
+
## Enabling AppSec
77
+
78
+
You can enable the WAF provided by AppSec to protect your applications from security threats. To do so, update your Helm values to include the AppSec configuration:
- `thread_pool waf_thread_pool`: Creates a dedicated thread pool for AppSec processing. Adjust `threads` and `max_queue` based on your traffic patterns and available resources.
104
+
- `datadog_appsec_enabled on`: Enables the Application Security module for threat detection and protection. This can be omitted so that AppSec can be enabled/disabled through Remote Configuration.
105
+
- `datadog_waf_thread_pool_name waf_thread_pool`: Associates the matching requests with the configured thread pool.
106
+
107
+
Refer to [the configuration reference][7] for more configurable options.
108
+
109
+
<div class="alert alert-info">
110
+
For production environments, monitor the thread pool performance and adjust the <code>threads</code> and <code>max_queue</code> parameters based on your traffic volume and latency requirements.
0 commit comments