Week 5 Blog Post
This week i decided to read the article Walking the Tight Rope of REST API Security: Best Practices Will Hold You Steady by Harsh Upreti.
This article discusses REST APIs and the security that is involved when dealing with them. APIs are a large part of the development process and the REST framework has been gaining a great deal of popularity. It is due to this that understanding the security revolving around this framework becomes highly important.
This article discusses how the best way to maintain security especially when working with the REST framework is to maintain good programming practices even in the most dire of situations. Time crunches happen a lot and sometimes taking a shortcut seems like the only route available, however in the long run the damage this could cause is catastrophic.
The security of the REST API is what takes a hit from these shortcuts and security is exceedingly important in this digital world. The article states how REST standards are often “massaged, misinterpreted, and sometimes even mauled beyond recognition (Upreti 1)”. These things can end up resulting in sensitive information residing directly in the URL which is a very big no no.
“Why is it not a good idea to have informaton in the URL? Well, because:
- Your URL goes places, it is very much exposed to the whole world, it’s embedded in emails, in third party code, it gets shortened and gets tossed around pretty much everywhere. You do not want anything even remotely sensitive there.
- Attacks like cross site scripting can use URL parameters to introduce malicious scripts in your API calls. (Upreti 1)”
These above listed reasons seem like more than enough to maintain food programming practices even in the worst of timecrunches. REST has a very well documented set of practices for using the framework and sticking to them is essential to the quality as well as the security of your code. The article also suggests testing for security as much as possible throughout the development process as well as understanding the REST framework well enough to know what you need to test for.
Here are 4 other articles that i found interesting:
http://www.mkltesthead.com/2016/10/in-that-moment-of-terror-evolution.html
From the blog CS@Worcester – Computer Science Journal by jtassone93 and used with permission of the author. All other rights reserved by the author.
