Apigee Sense vs. Salt Security API Protection Platform

Deployment is very easy and the configuration is excellent and the Apigee Sense is ready to go. The platform has an effective centralized Cloud monitoring capabilities and the data visual analytics that are generated are useful to the business production. Excellent portals and the features are easy to custom when starting with the platform and the project documentation tools are reliable.

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.

• Data integration is excellent.
• Secure environment for the organization data management.
• Traffic monitoring.

Incentivized

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

• The Apigee Sense deployment to the new users is not an easy operation.
• Visualization analytics for complex project data.
• Cloud multiple services management.

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.

• Using the software is quite easy to monitor network traffic.
• Application performance management.
• Cloud data management functionalities.

Incentivized

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