If your service is running an Agent with Remote Configuration enabled and a tracing library version that supports it, you can block attacks and attackers from the Datadog UI without additional configuration of the Agent or tracing libraries.

App and API Protection (AAP) Protect enables you to slow down attacks and attackers by blocking them. Security traces are blocked in real-time by the Datadog tracing libraries. Blocks are saved in the Datadog platform, automatically and securely fetched by the Datadog Agent, deployed in your infrastructure, and applied to your services.

Prerequisites

To use protection capabilities with your service:

• Update your Datadog Agent to at least version 7.41.1.
• Enable AAP.
• Enable Remote Configuration.
• Update your tracing library to at least the minimum version needed to turn on protection. For details, see the AAP capabilities support section of Compatibility for your service’s language.
• If you plan to use authenticated user blocking, add user information to traces.

Blocking attackers (IPs and authenticated users)

You can block attackers that are flagged in AAP Security Signals temporarily or permanently. In the Signals Explorer, click into a signal to see what users and IP addresses are generating the signal, and optionally block them.

From there, all AAP-protected services block incoming requests performed by the blocked IP or user, for the specified duration. All blocked traces are tagged with security_response.block_ip or security_response.block_user and displayed in the Trace Explorer. Services where AAP is disabled aren’t protected. See Investigate Security Signals for more information.

Respond to threats in real time by automating attacker blocking

In addition to manually blocking attackers, you can configure automation rules to have AAP automatically block attackers that are flagged in Security Signals.

To get started, navigate to Security > App and API Protection > Protection > Detection Rules. You can create a new rule or edit an existing rule with type App and API Protection. For example, you can create a rule to trigger Critical severity signals when Credential Stuffing attacks are detected, and automatically block the associated attackers’ IP addresses for 30 minutes.

Note: You must instrument your services to be able to block authenticated attackers. See User Monitoring and Protection for more details.

Block attackers at the perimeter - integrate AAP with your existing WAF deployments

Datadog AAP enables customers to block attackers at the perimeter, directly from the Security Signal. AAP integrates with Workflows to push the attackers’ IP addresses to perimeter Web Application Firewalls (AWS WAF, Cloudflare, Fastly) and ensure requests from these attackers are blocked at the edge even before they enter the customer’s environment. Create workflows from the available blueprints and run them directly from AAP’s Signal side panel.

Denylist

Attackers’ IP addresses and authenticated users that are permanently or temporarily blocked are added to the Denylist. Manage the list on the Denylist page. A denylist supports blocking individual IPs as well as a range of IPs (CIDR blocks).

Passlist

You can use the Passlist to permanently allow specific IP addresses access to your application. For example, you may wish to add internal IP addresses to your passlist, or IP addresses that regularly run security audits on your application. You can also add specific paths to ensure uninterrupted access. Manage the list from the Passlist page.

Blocking attack attempts with In-App WAF

AAP In-App WAF (web application firewall) combines the detection techniques of perimeter-based WAFs with the rich context provided by Datadog, helping your teams protect their systems with confidence.

Because AAP is aware of an application’s routes, protection can be applied granularly to specific services, and not necessarily across all applications and traffic. This contextual efficiency reduces your inspection effort, and it reduces the false positive rate compared to a perimeter WAF. There is no learning period, because most web frameworks provide a structured map of routes. AAP can help your team roll out protections against zero-day vulnerabilities automatically soon after the vulnerability is disclosed, while targeting vulnerable applications, limiting the risk of false positives.

How In-App WAF blocks security traces

In addition to the monitoring and disabled modes offered for each of the 130+ In-App WAF rules, rules also have blocking mode. Each rule specifies conditions on the incoming request to define what the library considers suspicious. When a given rule pattern matches an ongoing HTTP request, the request is blocked by the library.

Managed policies define the mode in which each of the In-App WAF rules behave on match: monitoring, blocking, or disabled. Because it has the full context of your applications, AAP knows which rules to apply to protect your applications while limiting the number of false positives.

For fine-grained control, you can clone a Datadog managed policy or create a custom policy and set the mode to meet your needs. If you set the policy to auto-updating, your applications are protected by the latest detections rolled out by Datadog. You also have the option to pin a policy to a specific version of the ruleset.

As In-App WAF rules are toggled between modes, the changes are reflected in near real-time for services with Remote Configuration enabled. For other services, you can update the policy on the In-App WAF page and then define In-App WAF rules for the change in behavior to be applied.

Manage In-App WAF by navigating to Security –> App and API Protection –> Configuration –> In-App WAF.

View blocked security traces in the Trace Explorer by filtering on the facet Blocked:true.

Configure In-App WAF

1. Enable Remote Configuration so that your AAP-enabled services show up under In-App WAF. This is required to securely push In-App WAF configuration from your Datadog backend to the tracing library in your infrastructure.

2. Associate your AAP/Remote Configuration-enabled services with a policy. After Remote Configuration is enabled on a service, navigate to Security > App and API Protection > Protection > In-App WAF. The service appears under the Datadog Monitoring-only policy by default. Datadog Monitoring-only is a managed policy and is read-only, meaning you cannot modify the status (monitoring, blocking, or disabled) for individual rules.

   If you need granular control, clone one of the available policies to create a custom policy where rule statuses can be modified. Associate one or more of your services with this custom policy.

   To change the policy applied by default to your services, you can update your default policy. From the In-App-WAF, click the policy you would like to set as default, then click Actions > Set this policy as default.

Customize protection behavior

Customize response to blocked requests

ブロックされたリクエストは JSON または HTML のコンテンツを特徴としています。HTTP ヘッダーの Accept]103 が text/html のように HTML を指している場合、HTML コンテンツが使われます。そうでない場合は JSON が使われます。

どちらのコンテンツも Datadog Tracer ライブラリパッケージに埋め込まれ、ローカルにロードされます。GitHub 上の Datadog Java トレーサーのソースコードで HTML および JSON のテンプレートの例をご覧ください。

HTML と JSON のコンテンツは、アプリケーションのデプロイメントファイル内の DD_APPSEC_HTTP_BLOCKED_TEMPLATE_HTML と DD_APPSEC_HTTP_BLOCKED_TEMPLATE_JSON 環境変数を使って変更することができます。

例:

DD_APPSEC_HTTP_BLOCKED_TEMPLATE_HTML=<path_to_file.html>

または、構成エントリを使用することもできます。

Java の場合は、以下を追加します。

dd.appsec.http.blocked.template.html = '<path_to_file.html>'
dd.appsec.http.blocked.template.json = '<path_to_file.json>'

Ruby の場合は、以下を追加します。

# config/initializers/datadog.rb

Datadog.configure do |c|
  # text/html ブロックページを構成するには
  c.appsec.block.templates.html = '<path_to_file.html>'
  # application/json ブロックページを構成するには
  c.appsec.block.templates.json = '<path_to_file.json>'
end

PHP の場合は、以下を追加します。

; 98-ddtrace.ini

; ブロックされたリクエストで提供される HTML 出力をカスタマイズします
datadog.appsec.http_blocked_template_html = <path_to_file.html>

; ブロックされたリクエストで提供される JSON 出力をカスタマイズします
datadog.appsec.http_blocked_template_json = <path_to_file.json>

Node.js の場合は、以下を追加します。

require('dd-trace').init({
  appsec: {
    blockedTemplateHtml: '<path_to_file.html>',
    blockedTemplateJson: '<path_to_file.json>'
  }
})

デフォルトでは、ブロックされたアクションに応答して表示されるページは次のようになります。

The default HTTP response status code while serving the deny page to attackers is 403 FORBIDDEN. To customize the response, navigate to Security > App and API Protection > Protection > In-App Waf > Custom Responses.

You can optionally mask the fact that the attacker has been detected and blocked by overriding the response code to be 200 OK or 404 NOT FOUND when the deny page is served.

You can also optionally redirect attackers to a custom deny page and away from your critical services and infrastructure. Specify a redirect URL and the type of redirect, for example permanent (301 response code) or temporary (302 response code).

Disable protection across all services (Disabling protection mode)

Protection mode is on by default and is a toggle available to quickly disable blocking across all your services. Requests can be blocked from two sections in Datadog: all attacker requests from Security Signals, and security traces from In-App WAF.

As important as it is for you to be able to apply protection granularly and reduce the likelihood of legitimate users getting blocked, you sometimes need a simple off switch to quickly stop all blocking across all services. To turn off protection, navigate to Security > App and API Protection > Protection > In-App WAF and toggle Allow Request Blocking to off.

Further reading