If you really need to secure your APIs then you need Salt
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
Most Important Features
- Constant monitoring and alert for possible attacks based on API consumption baseline
Return on Investment
- Salt can positively impact the API availability SLA by helping to accelerate the detection of attacks that can compromise the availability of your infrastructure.
