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 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. |
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
Additional helpful documentation, links, and articles:
