이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Overview

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:

Qualification outcomes

AAP runs qualification rules (closed-source) on every trace. There are four possible qualification outcomes, as listed in the facet menu:

Qualification resultDescription
UnknownAAP has qualification rules for this attack, but did not have enough information to make a qualification decision.
None successfulAAP determined that attacks in this trace were not harmful.
HarmfulAt least one attack in the trace was successful.
No valueAAP does not have qualification rules for this type of attack.

Trace sidepanel

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:

Further Reading