Enabling ASM for .NET

이 페이지는 아직 한국어로 제공되지 않으며 번역 작업 중입니다. 번역에 관한 질문이나 의견이 있으시면 언제든지 저희에게 연락해 주십시오.

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

사전 필수 조건

1-클릭 활성화
서비스가 원격 구성이 활성화된 Agent와 이를 지원하는 추적 라이브러리 버전으로 실행 중인 경우 ASM 상태 열의 Not Enabled 표시 위로 마우스를 가져간 다음 Enable ASM를 클릭합니다. DD_APPSEC_ENABLED=true 또는 --enable-appsec 플래그를 사용하여 서비스를 다시 시작할 필요가 없습니다.

Enabling threat detection

Get started

  1. Update your Datadog .NET library to at least version 2.2.0 (at least version 2.16.0 for Software Composition Analysis detection features) for your target operating system architecture.

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

  2. Enable ASM by setting the DD_APPSEC_ENABLED environment variable to true. For example, on Windows self-hosted, run the following PowerShell snippet as part of your application start up script:

    $target=[System.EnvironmentVariableTarget]::Process
[System.Environment]::SetEnvironmentVariable("DD_APPSEC_ENABLED","true",$target)

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

      In a Windows console:

      rem Set environment variables
SET CORECLR_ENABLE_PROFILING=1
SET CORECLR_PROFILER={846F5F1C-F9AE-4B07-969E-05C26BC060D8}
SET DD_APPSEC_ENABLED=true

rem Start application
dotnet.exe example.dll

      Run the following PowerShell command as administrator to configure the necessary environment variables in the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment and restart IIS.

      $target=[System.EnvironmentVariableTarget]::Machine
[System.Environment]::SetEnvironmentVariable("DD_APPSEC_ENABLED","true",$target)
net stop was /y
net start w3svc

      Or, for IIS services exclusively, on WAS and W3SVC with Powershell as an administrator, run:

      $appsecPart = "DD_APPSEC_ENABLED=true"
[string[]] $defaultvariable = @("CORECLR_ENABLE_PROFILING=1", "CORECLR_PROFILER={846F5F1C-F9AE-4B07-969E-05C26BC060D8}", $appsecPart)

function Add-AppSec {

    param (
        $path
    )
    $v = (Get-ItemProperty -Path $path).Environment
    If ($v -eq $null) {
        Set-ItemProperty -Path $path -Name "Environment" -Value $defaultvariable
    }
    ElseIf (-not ($v -match $appsecPart)) {
        $v += " " + $appsecPart;
        Set-ItemProperty -Path $path -Name "Environment" -Value $v
    }
}
Add-AppSec -path "HKLM:SYSTEM\CurrentControlSet\Services\WAS\"
Add-AppSec -path "HKLM:SYSTEM\CurrentControlSet\Services\W3SVC\"

net stop was /y
net start w3svc

      Or, to avoid editing registry keys, edit the application settings in the web.config file of your application:

      <configuration>
  <appSettings>
        <add key="DD_APPSEC_ENABLED" value="true"/>
  </appSettings>
</configuration>

      This can also be done at the IIS application pools level in the applicationHost.config file, usually in C:\Windows\System32\inetsrv\config\:

      <system.applicationHost>

    <applicationPools>
        <add name="DefaultAppPool">
            <environmentVariables>
                <add name="DD_APPSEC_ENABLED" value="true" />
            </environmentVariables>
            (...)

      Add the following to your application configuration:

      DD_APPSEC_ENABLED=true

      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 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 ECS task definition JSON file, by adding this in the environment section:

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

      Add the following line to your container Dockerfile:

      ENV DD_APPSEC_ENABLED=true

    • Restart the application using a full stop and start.

    이 구성을 완료하면 라이브러리가 애플리케이션에서 보안 데이터를 수집해 에이전트로 전송하고, 이 데이터는 다시 Datadog로 전송됩니다. 그러면 기본 감지 규칙에 기반해 공격자 기술과 잠재 구성 오류가 플래그되며, 이를 기반으로 문제 해결 단계를 진행할 수 있습니다.

    1. 애플리케이션 보안 관리에서 감지 활동을 잘 하고 있는지 확인하려면 알려진 공격 패턴을 애플리케이션으로 보내세요. 예를 들어 다음 curl 스크립트가 포함된 파일을 실행해 보안 스캐너 감지됨 규칙을 트리거할 수 있습니다.

      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에 취약 정보가 표시됩니다.

    Further Reading

    추가 유용한 문서, 링크 및 기사:

    Adding user information to tracesDOCUMENTATION more more .NET Datadog library source codeSOURCE CODE more more OOTB Application Security Management RulesDOCUMENTATION more more Troubleshooting Application Security ManagementDOCUMENTATION more more