TrustRadius: an HG Insights company
Back to Overview
Salt Security API Protection Platform Logo

Salt Security API Protection Platform Reviews and Ratings

Rating: 8.5 out of 10
Score
8.5 out of 10

Community insights

TrustRadius Insights for Salt Security API Protection Platform are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Easy Deployment: Multiple users have expressed their appreciation for the easy deployment process of the product, which allowed them to set it up smoothly and without any hassle.

Excellent Visibility into API Activity: Many reviewers have specifically mentioned that the product offers excellent visibility into activity on APIs. This feature enables them to easily track and monitor how their APIs are being used.

Valuable Insights into Inventory: Some users have found great value in the product's ability to provide insights into their inventory. By using this tool, they were able to discover items that they were previously unaware of, resulting in a better understanding of their inventory.

Reviews

6 Reviews

If you really need to secure your APIs then you need Salt

Rating: 9 out of 10

Use Cases and Deployment Scope

We use Salt to have a realistic view of the entire API infrastructure and possible threats to which these APIs are being subjected. We were able to have a faster and more appropriate response to potential attacks that use APIs as an attack vector. Salt addresses the need to have visibility and control over what APIs we have and how these APIs are being consumed. I consider Salt a precious platform for security teams considering the massive and constant increase in the use of APIs in the architecture of new applications.

Pros

  • Detect possible attacks on APIs
  • Gain visibility into all APIs in your infrastructure

Cons

  • Access to requests and responses from all APIs (baseline), not only those related to attacks

Likelihood to Recommend

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.

JM
Jose Michael Henrique
Security Specialist at Banco Pan (5001-10,000 employees)
Vetted Review
Salt Security API Protection Platform
1 year of experience

Detailed Attacks information and good sensitive data flow control

Rating: 8 out of 10

Use Cases and Deployment Scope

Use Case: Identify anomalies and support incident response. Salt Security API Protection Platform security is integrated with SOC/SIEM tools, reporting the found attacks in order to investigate and respond. The purpose is to have a faster incident response and provide data that supports attacks investigations and sensitive data flow control.

Pros

  • Sensitive data mapping
  • Detailed Attacks Reporting
  • Integration with SOC/SIEM tools

Cons

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

Likelihood to Recommend

Useful for detailing attacks and showing the sensitive data flow on APIs.

MA
Marcel Amorim
Senior Security Analyst in Information Technology at Banco BV (1001-5000 employees)
Vetted Review
Salt Security API Protection Platform
1 year of experience

Salt review

Rating: 9 out of 10

Use Cases and Deployment Scope

We use a Salt Security API Protection Platform as our provider of information about data consumption via API and call management at application end-points, considering PII tracking and access patterns of eventual attackers (by IP address, authorization type, etc). In addition, Salt Security API Protection Platform provides us with a productivity gain related to the alerts generated and intelligence embedded in the analysis of possible vulnerabilities or threats.

Pros

  • List of Apis callers
  • Alert triagens about suspicious behaviors
  • PII identificaton

Cons

  • Consolidation reports about Apis accessing profiles.
  • Swagger to programming Apis.

Likelihood to Recommend

Salt Security API Protection Platform is particularly well addressed to occasions when a park of endpoints is under attack and needs the identification of their origin, as well as the interpretation of their patterns related to the properties of the call header, helping to understand the type of attack that is taking place and the countermeasure to be taken.

VU
Verified User
Analyst in Information Technology (5001-10,000 employees)
Vetted Review
Salt Security API Protection Platform
2 years of experience

API traffic compliance and security visibility

Rating: 10 out of 10

Use Cases and Deployment Scope

Salt provides visibility on our API traffic, allowing us to proactively identify PII, differences in API documentation (swagger files) and real traffic, alerts in situations that indicate a potential attacker allowing us to take countermeasures and suggestions on improvements (missing important HTTP headers, endpoints lacking authorization, etc.). Given the number of endpoints we have and the traffic we have would be really difficult to get these insights without Salt.

Pros

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

Cons

  • Reporting - more flexible ways to get information.
  • API documentation in order to interact with the platform.

Likelihood to Recommend

If you have a large number of API endpoints and a dynamic scenario where teams create and change API endpoints and you want to get visibility on key information to keep your API traffic secure and compliant with privacy regulations.

VU
Verified User
Manager in Information Technology (5001-10,000 employees)
Vetted Review
Salt Security API Protection Platform
1 year of experience

Salt Security Review

Rating: 9 out of 10

Use Cases and Deployment Scope

We have implemented Salt in our in-house developed applications to identify and protect publicly accessible APIs.

Pros

  • Identifies APIs
  • Identifies attacks against the APIs
  • Identifies the type data that is accessible through the APIs

Cons

  • Better correctly identify the data that is accessible through the APIs.

Likelihood to Recommend

It is great at identifying APIs that are being used within your custom developed applications. Once the APIs are identified, it also identifies all of the endpoints associated with those APIs. For a security team that is separate from the DEV team, this is very helpful.

VU
Verified User
Contributor in Information Technology (1001-5000 employees)
Vetted Review
Salt Security API Protection Platform
1 year of experience

API Security made easy with Salt [Security API Protection Platform]

Rating: 10 out of 10

Use Cases and Deployment Scope

We have deployed Salt [Security API Protection Platform] across the entire enterprise to have better visibility around all of our APIs. This is including several different cloud architectures and both in house and 3rd party applications. Salt [Security API Protection Platform] has helped us inventory our APIs and see any attacks and type of data being accessed through these APIs.

Pros

  • Easy deployment
  • Excellent visibility into activity on APIs
  • Inventory! It helps you find things you didn't know you had

Cons

  • Some customized deployments can be difficult
  • Reporting functionality across the enterprise and not just per environment needs improved
  • Better attack handling options needed

Likelihood to Recommend

Easy deployment for common cloud API architectures, so it's very easy to at least get visibility into what you have. In house developed apps with a custom infrastructure could be a difficult integration.

TW
Tyler Warren
Director, IT Security in Information Technology at Prologis (1001-5000 employees)
Vetted Review
Salt Security API Protection Platform
1 year of experience