- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`App and API Protection (AAP) provides observability into application-level attacks, and evaluates the conditions in which each trace was generated. AAP trace qualification then labels each attack as harmful or safe to help you take action on the most impactful attacks.
Filter by the Qualification facet in the AAP Traces Explorer to view the possible qualification results:
AAP runs qualification rules (closed-source) on every trace. There are four possible qualification outcomes, as listed in the facet menu:
Qualification result | Description |
---|---|
Unknown | AAP has qualification rules for this attack, but did not have enough information to make a qualification decision. |
None successful | AAP determined that attacks in this trace were not harmful. |
Harmful | At least one attack in the trace was successful. |
No value | AAP does not have qualification rules for this type of attack. |
The qualification result can also be seen when viewing the details of an individual trace.Example of a trace that AAP has qualified as safe:
Example of a trace that AAP has qualified as harmful: