APIs are gateways in and out of our kingdom and thus they’re also great access points for malicious hackers. How the heck do we secure them without overwhelming ourselves?
Check out this post for the basis for our conversation on this week’s episode which features me, David Spark (@dspark), producer of CISO Series, co-host Allan Alford (@allanalfordintx), and sponsored guest, Roey Eliyahu, CEO, Salt Security.
Check out my previous article “25 API Security Tips You’re Probably Not Considering”.
Thanks to this week’s podcast sponsor, Salt Security
Got feedback? Join the conversation on LinkedIn.
On this episode of Defense in Depth, you’ll learn:
- The skill set needed to secure APIs is different than web security.
- The move towards the cloud, DevOps, and the need to have security tools talk to each other has brought a lot more attention to the need for API security.
- Like in all areas of security, just knowing what you’ve got is a struggle. Same is true with APIs.
- Just knowing what APIs you have is not enough. You must know their functionality. Map your APIs to the systems and the data their transmitting.
- How aware are your developers of the pitfalls of API misuse?
- There’s a myriad of security options but start with strong authenticate using hash-based message authentication.
- Much of the advice we got was simply shrinking the API attack surface. This can be done by either limiting the functionality of the API or removing unused APIs.
- The “review the code” advice that we heard often is sadly not realistic. APIs are resistant to both automatic and manual code review.
- API security seems like a 300 or 400 level security effort. Smaller companies that don’t have a security operations center (SOC) may simply not be able to handle it and will need to outsource their API security and SOC needs to a third party or managed security service.