このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、
お気軽にご連絡ください。
The Datadog nginx tracing module has experimental support for threat detection and blocking.
Enabling threat detection
Get started
Verify that your nginx build was compiled with the flag
--with-threads
. Most distributions ship with this flag enabled by default.
To check if your nginx installation was built with thread support, run nginx -V
and check the configure arguments
line. If you cannot find
--with-threads
in the output, you will need to rebuild nginx with this flag
enabled. For more information on how to build nginx from sources, see the
nginx documentation.
Update your nginx tracing library module to at least version 1.2.0. Visit
the GitHub releases page and select the artifact named according to the
pattern “ngx_http_datadog_module-appsec-<amd64/arm64>-<nginx
version>.so.tgz”. Note that this artifact includes “appsec” in the name.
Enable AAP in the nginx configuration.
You need to:
For example:
load_module /path/to/ngx_http_datadog_module.so;
thread_pool waf_thread_pool threads=4 max_queue=128;
http {
datadog_appsec_enabled on;
datadog_waf_thread_pool_name waf_thread_pool;
}
For more information, see the reference documentation.
この構成が完了すると、ライブラリは、アプリケーションからセキュリティデータを収集し、Agent に送信します。Agent は、そのデータを Datadog に送信し、すぐに使える検出ルールによって、攻撃者のテクニックや潜在的な誤構成にフラグが立てられるため、是正措置を講じることができます。
Application Security Management の脅威検出の動作を見るには、既知の攻撃パターンをアプリケーションに送信してください。例えば、次の curl スクリプトを含むファイルを実行して、Security Scanner Detected ルールをトリガーします。
for ((i=1;i<=250;i++));
do
# Target existing service’s routes
curl https://your-application-url/existing-route -A dd-test-scanner-log;
# Target non existing service’s routes
curl https://your-application-url/non-existing-route -A dd-test-scanner-log;
done
注: dd-test-scanner-log
の値は、最新のリリースでサポートされています。
アプリケーションを有効にして実行すると、数分後に Application Signals Explorer に脅威情報が表示され、Vulnerability Explorer に脆弱性情報が表示されます**。
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.
It’s not possible to block the request based on characteristics of the
response, such as its status code, headers, or body.
Using AAP without APM tracing
If you want to use Application & API Protection without APM tracing functionality, you can deploy with tracing disabled:
- Configure your tracing library with the
DD_APM_TRACING_ENABLED=false
environment variable in addition to the DD_APPSEC_ENABLED=true
environment variable. - This configuration will reduce the amount of APM data sent to Datadog to the minimum required by App and API Protection products.
For more details, see [Standalone App and API Protection][standalone_billing_guide].
[standalone_billing_guide]: /security/application_security/guide/standalone_application_security/
Further Reading