Kong Konnect vs. Salt Security API Protection Platform

Using Kong [Konnect]'s declarative settings, a user may control traffic, automate deployment, and maintain container-based software after it's deployed. In addition, it handles the whole lifecycle of service management. Installation, management, and operation of Kong [Konnects]'s cloud-native connection runtimes may be performed in any cloud or Kubernetes provider environment, as well as on-premises environments. In order to optimise their services and transactions, users may keep track of their services and transactions in real-time via real-time monitoring.

Incentivized

Salt is highly recommended for anyone who wants to discover, monitor and protect their APIs against various types of attacks. Salt should not be used as a SIEM.

• Application orchestration
• Error tracing
• Analyzing traffic
• Load balancing

Incentivized

• PII identification in API traffic.
• Divergence between API traffic and documentation (swagger files).
• Potential attacks with information to take counter measures.

• Community support
• Sample projects for easy integration

Incentivized

• The platform could have more options for exporting detailed data from attackers' dashboards.
• The Attackers dashboard could also have more options of filters in order to support the investigations of the attack.
• The OAS analysis could present a more detailed view of the found issues.

We tried controls offered by the IaaS providers but these were hard to manage and did not provide the visibility we wanted. We also protected APIs with a normal WAF but this was only helpful for assets we knew about and API attacks were not caught by the WAF.

• Increased application efficiency
• Reduced system downtown
• Significantly improved error resolution

Incentivized

• Salt Security API Protection Platform has provided detailed information that is helping us to identify and investigate attacks in our environment