You can monitor App and API Protection for Ruby apps running in Docker, Kubernetes, Amazon ECS, and AWS Fargate.

Prerequisites

• The Datadog Agent is installed and configured for your application’s operating system or container, cloud, or virtual environment.
• Datadog APM is configured for your application or service, and traces are being received by Datadog.
• If your service is running with an Agent with Remote Configuration enabled and a tracing library version that supports it, you can block attackers from the Datadog UI without additional configuration of the Agent or tracing libraries.

Enabling threat detection

Get started

1. Update your Gemfile to include the Datadog library:

   gem 'datadog', '~> 2.0' # Use 'ddtrace' if you're using v1.x
   

   To check that your service’s language and framework versions are supported for AAP capabilities, see Compatibility.

   For more information about upgrading to v2 from a dd-trace 1.x version, see the Ruby tracer upgrade guide.

2. Enable AAP by enabling the APM tracer. The following options describe a quick setup that covers the most common cases. Read the Ruby tracer documentation for more details.

   You can enable AAP either in your code:

   Enable the APM tracer by adding an initializer in your application code:

   # config/initializers/datadog.rb
   
   require 'datadog/appsec'
   
   Datadog.configure do |c|
     # enable the APM tracer
     c.tracing.instrument :rails
   
     # enable AAP
     c.appsec.enabled = true
     c.appsec.instrument :rails
   end
   

   Or enable the APM tracer through auto-instrumentation by updating your Gemfile to auto-instrument:

   gem 'datadog', '~> 2.0', require: 'datadog/auto_instrument'
   

   And also enable appsec:

   # config/initializers/datadog.rb
   
   require 'datadog/appsec'
   
   Datadog.configure do |c|
     # the APM tracer is enabled by auto-instrumentation
   
     # enable AAP
     c.appsec.enabled = true
     c.appsec.instrument :rails
   end
   

   Enable the APM tracer by adding the following to your application’s startup:

   require 'sinatra'
   require 'datadog'
   require 'datadog/appsec'
   
   Datadog.configure do |c|
     # enable the APM tracer
     c.tracing.instrument :sinatra
   
     # enable AAP for Sinatra
     c.appsec.enabled = true
     c.appsec.instrument :sinatra
   end
   

   Or enable the APM tracer through auto-instrumentation:

   require 'sinatra'
   require 'datadog/auto_instrument'
   
   Datadog.configure do |c|
     # the APM tracer is enabled by auto-instrumentation
   
     # enable AAP for Sinatra
     c.appsec.enabled = true
     c.appsec.instrument :sinatra
   end
   

   Enable the APM tracer by adding the following to your config.ru file:

   require 'datadog'
   require 'datadog/appsec'
   
   Datadog.configure do |c|
     # enable the APM tracer
     c.tracing.instrument :rack
   
     # enable AAP for Rack
     c.appsec.enabled = true
     c.appsec.instrument :rack
   end
   
   use Datadog::Tracing::Contrib::Rack::TraceMiddleware
   use Datadog::AppSec::Contrib::Rack::RequestMiddleware
   

   Or one of the following methods, depending on where your application runs:

   Update your configuration container for APM by adding the following argument in your docker run command:

   docker run [...] -e DD_APPSEC_ENABLED=true [...]
   

   Add the following environment variable value to your container Dockerfile:

   ENV DD_APPSEC_ENABLED=true
   

   Update your configuration yaml file container for APM and add the AppSec env variable:

   spec:
     template:
       spec:
         containers:
           - name: <CONTAINER_NAME>
             image: <CONTAINER_IMAGE>/<TAG>
             env:
               - name: DD_APPSEC_ENABLED
                 value: "true"
   

   Update your ECS task definition JSON file, by adding this in the environment section:

   "environment": [
     ...,
     {
       "name": "DD_APPSEC_ENABLED",
       "value": "true"
     }
   ]
   

   Initialize AAP in your code or set DD_APPSEC_ENABLED environment variable to true in your service invocation:

   env DD_APPSEC_ENABLED=true rails server
   

   The library collects security data from your application and sends it to the Agent, which sends it to Datadog, where out-of-the-box detection rules flag attacker techniques and potential misconfigurations so you can take steps to remediate.

3. To see App and API Protection threat detection in action, send known attack patterns to your application. For example, trigger the Security Scanner Detected rule by running a file that contains the following curl script:

   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

   Note: The dd-test-scanner-log value is supported in the most recent releases.

   A few minutes after you enable your application and exercise it, threat information appears in the Application Trace and Signals Explorer in Datadog.

Using AAP without APM tracing

If you want to use Application & API Protection without APM tracing functionality, you can deploy with tracing disabled:

1. Configure your tracing library with the DD_APM_TRACING_ENABLED=false environment variable in addition to the DD_APPSEC_ENABLED=true environment variable.
2. 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

Más enlaces, artículos y documentación útiles:

Adding user information to tracesDOCUMENTATION Ruby Datadog library source codeSOURCE CODE OOTB App and API Protection RulesDOCUMENTATION Troubleshooting App and API ProtectionDOCUMENTATION