Salt Security API Protection Platform vs. Vulcan Cyber (discontinued)

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.

It's really challenging at times to contend with multiple vulnerabilities on a daily basis, and having a way to make sense of what actually needs to be prioritized and what can be shifted further down the task list is extremely helpful. Because the solution suggests what your next step should be in mitigating a specific vulnerability, it helps us save time and research by enabling us to immediately take action after being informed about an issue.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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

• Identifies vulnerabilities and they are easily understood.
• Easy to identify remedies in an instant.
• Campaign feature is a true time saver
• Our CSM, Nino, is the best I have ever worked with!

Incentivized

Invited by the Vendor

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• 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.

• Deduping of assets could be better.
• The weighting of vulnerabilities is hard to describe to non technical executives.
• The Business Groups and Tagging needs improvement. Or at least allow tags to be removed if not needed. Now they are static from the API feed.

Incentivized

Invited by the Vendor

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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.

I wasn't here at the time when the company compared different vulnerability management platforms so I'm not sure on the reasoning and difference between the 2. It could be that the team went through different choices and found Vulcan to be the best fit. It's hard for me to say why Vulcan was specifically chosen

Incentivized

Invited by the Vendor

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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

• Allows much better prioritizing of which assets are most vulnerable
• Allow a better understanding of what assets are actually under real threat vs. what is assumed to be vulnerable, but the real world fact is the system would be hard to reach internally, so it's not as vulnerable.

Incentivized

Invited by the Vendor

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info