Salt Security API Protection Platform vs. SoapUI Open Source, supported by SmartBear

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.

If you are making system upgrade project and you have existing system working and you want to imitate messages that are going in production but without making any data loads or switch it’s very suitable and convenient software. It serves well in manual test scenarios but wouldn’t be as good in case of mass tests.

Incentivized

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

• SOAP
• REST
• Authentication

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.

• I actually like SoapUI as it is, I have not found things to improve, except for the speed of response is very complex services.

Incentivized

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.

Every application has its own features and UI design but SoapUI is also very good at testing. All features are awesome.

Incentivized

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

• Saves time in web service testing
• Make it easy
• No need to code much

Incentivized