The PingIntelligence Dashboard pulls the API definition from Axway API Manager and converts it to a JSON format compatible with ASE.
The Dashboard needs certain tags to be configured in Axway API Manager for it to import the normal and decoy API definitions.
To configure tags in Axway API Manager and tags for the decoy API:
Configuring tags in API Manager
Tags are a medium to let ASE know which APIs from the API ecosystem need to be processed for monitoring and attack detection. Tags are also required for cookie and login URL parameters to be captured by the PingIntelligence Dashboard for adding to the ASE API JSON definition.
To tag APIs for artificial intelligence (AI) processing:
Configuring tags for decoy APIs
You can configure decoy APIs in Axway API Manager. A decoy API is an API for which
the traffic does not reach the backend API servers. The decoy API is deployed to
gather information about potential threats that your API ecosystem may face. Traffic
directed to a decoy API configured in Axway API Gateway is redirected to ASE, which
functions as the backend server. ASE sends a preconfigured response, such as
200 OK
, for requests sent to a decoy API.
You need to configure the following TAGS and VALUES in the API tab for in Axway API Manager:
Configuring Axway XFF policies for decoy APIs
PingIntelligence provides an X-Forwarded-For (XFF) policy for your decoy APIs.
The XFF policy adds an X-Forwarded-For
to the backend only if
it is not present in the original incoming request. If the
X-Forwarded-For
header is already present in the
incoming request, the policy takes no action