Akamai App & API Protector vs. Salt Security API Protection Platform

Akamai Kona Site Defender KSD, works fine for any website or mobile application (Native/JDK), it can be used as a WAF, a rate limiting tool, or a bot management tool all in one, plus you will get all the benefits of the Akamai CDN (Content distribution network) as well

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.

• Web Security
• Bot managment
• Rate Control

Incentivized

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

• Custom rules might be hard to configure
• For some cases you will need to contact the Akamai team to adjust the backend
• Interface might feel laggy if used in a non-powerful PC

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.

• Fair Security investment
• An attack impact would be higher
• Support contract is not cheap

Incentivized

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