From 40a9a7dc5c0b3da666669dc037d3d2fbb0b0aa3d Mon Sep 17 00:00:00 2001 From: Anil Mahtani <929854+Anilm3@users.noreply.github.com> Date: Fri, 20 Sep 2024 09:24:32 +0100 Subject: [PATCH 1/2] Update nginx ASM compatibility and limitations --- .../threats/setup/compatibility/nginx.md | 6 +++--- .../threats/setup/threat_detection/nginx.md | 5 +++-- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/content/en/security/application_security/threats/setup/compatibility/nginx.md b/content/en/security/application_security/threats/setup/compatibility/nginx.md index 13dd9ef8d0742..6e94a0e3ed2a7 100644 --- a/content/en/security/application_security/threats/setup/compatibility/nginx.md +++ b/content/en/security/application_security/threats/setup/compatibility/nginx.md @@ -13,14 +13,14 @@ specified tracer version: | Application Security capability | Minimum nginx module version | |----------------------------------------|------------------------------| | Threat Detection | 1.2.0 | -| Threat Protection | 1.2.0 | -| Customize response to blocked requests | 1.2.0 | +| Threat Protection | 1.3.0 | +| Customize response to blocked requests | 1.3.0 | | Software Composition Analysis (SCA) | not applicable | | Code Security | not applicable | | Automatic user activity event tracking | not supported | | API Security | not supported | -Please review nginx version 1.2.0 [limitations][1]. +Please review nginx version 1.3.0 [limitations][1]. ## Nginx support diff --git a/content/en/security/application_security/threats/setup/threat_detection/nginx.md b/content/en/security/application_security/threats/setup/threat_detection/nginx.md index 9c27c9b302df5..99098670c3c8e 100644 --- a/content/en/security/application_security/threats/setup/threat_detection/nginx.md +++ b/content/en/security/application_security/threats/setup/threat_detection/nginx.md @@ -63,11 +63,12 @@ The Datadog nginx tracing module has experimental support for threat detection a ## Limitations -As of version 1.2.0, the available functionality has the following important limitations: +As of version 1.3.0, the available functionality has the following important limitations: * The request body is not inspected, regardless of its content type. -- There is no remote configuration for AppSec. Consequently, AppSec excludes 1-click activation (AppSec must be explicitly enabled or disabled in the nginx configuration), rules cannot be updated/enabled/disabled, and blocking users by IP address is prevented, since the list cannot be transmitted to the nginx module. +- AppSec excludes 1-click activation (AppSec must be explicitly enabled or disabled in the nginx configuration). + * It's not possible to block the request based on characteristics of the response, such as its status code, headers, or body. From 53f340b7ec6d3088fe4fcde6cd9632c2b261ec16 Mon Sep 17 00:00:00 2001 From: Anil Mahtani <929854+Anilm3@users.noreply.github.com> Date: Fri, 20 Sep 2024 10:46:22 +0100 Subject: [PATCH 2/2] Remove 1-click caveat --- .../threats/setup/threat_detection/nginx.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/en/security/application_security/threats/setup/threat_detection/nginx.md b/content/en/security/application_security/threats/setup/threat_detection/nginx.md index 99098670c3c8e..95d528fb98d08 100644 --- a/content/en/security/application_security/threats/setup/threat_detection/nginx.md +++ b/content/en/security/application_security/threats/setup/threat_detection/nginx.md @@ -67,8 +67,6 @@ As of version 1.3.0, the available functionality has the following important lim * The request body is not inspected, regardless of its content type. -- AppSec excludes 1-click activation (AppSec must be explicitly enabled or disabled in the nginx configuration). - * It's not possible to block the request based on characteristics of the response, such as its status code, headers, or body.