Treat them as such. 3. Use a Secure Communication Channel The most common way to implement API security is through the use of HTTPS, which encrypts all traffic between users and the API endpoint usi ...
Continue Reading
July 29, 2021
Rate Limiting for the Win! So how do we prevent these issues? The first step is to implement rate-limiting on your APIs. Rate limiting can be implemented in many ways: by IP address, by user agent (b ...
Continue Reading
July 29, 2021
The Salt Labs team today released the latest edition of the pioneering State of API Security report. The data, drawn from a combination of survey responses and empirical data from Salt Security cu ...
Continue Reading
July 29, 2021
The advantage of this approach is that it allows me to check if two pieces of data are identical or not without actually having to store them both. This means that I can avoid storing duplicate copies ...
Continue Reading
July 29, 2021
The API economy is growing at an unprecedented pace, and organizations are increasingly relying on APIs to drive innovation https://t.co/Eg46lu5tzq ...
Continue Reading
July 29, 2021
The following example shows how an attacker could use a stolen users ID and password to access their bank account: A malicious user steals a valid users credentials from a compromised website, ...
Continue Reading
July 29, 2021
Treat them accordingly. 3. Require Transport Layer Security for All API Traffic While the use of HTTPS is a good first step, its not enough to protect all API traffic from eavesdropping and man-in ...
Continue Reading
July 29, 2021
I've been working on the Go team since before 1.0 shipped in March 2012. In that time we've released many new versions of the language, libraries, and tools; grown from a few dozen to hundreds of cont ...
Continue Reading
July 29, 2021
Back to Main
