Go Getting Started with ASM

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

You can monitor application security for Go apps running in Docker, Kubernetes, and AWS ECS.

In general, setting up Application Security Management (ASM) involves:

  1. Identifying which services to enable ASM on.
  2. Updating to the latest Datadog library (the most recent APM tracing library).
  3. Enabling the library to collect the application security data from the services and send it to Datadog.
  4. Triggering security signals in your application and seeing how Datadog displays the resulting information.

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.

Get started

  1. Update your program’s dependencies with the latest version of the Datadog Go library (version 1.36.0 or later):

    $ go get -v -u gopkg.in/DataDog/dd-trace-go.v1
    

    For information about which language and framework versions are supported by the library, see Compatibility.

  2. Recompile your program and enable ASM and CGO:

    $ env CGO_ENABLED=1 go build -v -tags appsec my-program
    
  3. Redeploy your Go service and enable ASM by setting the DD_APPSEC_ENABLED environment variable to true:

    $ env DD_APPSEC_ENABLED=true ./my-program
    

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

    Add the following environment variable value to your Docker command line:

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

    Add the following environment variable value to your application container’s Dockerfile:

    ENV DD_APPSEC_ENABLED=true
    

    Update your application’s deployment configuration file for APM and add the ASM environment variable:

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

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

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

    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.

  4. To see Application Security Management 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<=200;i++)); 
    do
    # Target existing service’s routes
    curl https://your-application-url/existing-route -A Arachni/v1.0;
    # Target non existing service’s routes
    curl https://your-application-url/non-existing-route -A Arachni/v1.0;
    done

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

Security Signal details page showing tags, metrics, suggested next steps, and attacker IP addresses associated with a threat.

Further Reading