The PingIntelligence software components handle all artificial intelligence (AI) processing and dashboard reporting. The component responsible for collecting API traffic metadata is called the API Security Enforcer (ASE). The ASE connects to the PingIntelligence software to deliver the API traffic metadata collected from the TIBCO Cloud Mashery gateways for the AI processing.

PingIntelligence consists of the following components:

  • The ASE is deployed on-premise as a virtual machine or Docker container. It captures the metadata of the monitored APIs and sends it to the PingIntelligence service for processing.

    Payload data is never sent to the cloud. The ASE is deployed in sideband mode with TIBCO Mashery API gateways. It connects to one or more gateways through a sideband policy deployed on the gateways. For more information, see Sideband Connector for TIBCO Cloud Mashery.

  • The AI engine processes the metadata sent by ASE to identify new APIs, deliver increased visibility, and detect abnormal API traffic patterns. It builds machine learning models that self-train based on the API traffic. When an abnormal situation or attack needs to be blocked, it communicates with the ASE to block the clients from which the traffic originates.
  • The PingIntelligence dashboard provides rich analytics on API activities. It tracks API activity across all API gateway clusters and clouds to deliver a single pane of glass used to monitor the API infrastructure. Newly discovered APIs are surfaced and are tracked once selected. All tokens or cookies used and IP addresses are associated with each user identity. The dashboard provides information on the training status of the APIs and delivers deep insights on abnormal situations and attacks detected.

To integrate your TIBCO Cloud Mashery gateway with PingIntelligence:

  1. Go to and click Try Ping on the right side of the page.

    A screenshot of the Ping Identity website menu.
  2. To deploy the Mashery connector, see the TIBCO connector documentation.

    For more information on sideband connectivity, see API Security Enforcer.