Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ASM] Update nginx compatibility and limitations #25355

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -63,11 +63,10 @@ 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.
* It's not possible to block the request based on characteristics of the
response, such as its status code, headers, or body.

Expand Down
Loading