Timeline for How to limit the impact of and reduce the risk of SQL injection for existing website?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 21, 2018 at 6:59 | history | suggested | Pang | CC BY-SA 4.0 |
Corrected invalid link.
|
| Sep 21, 2018 at 5:03 | review | Suggested edits | |||
| S Sep 21, 2018 at 6:59 | |||||
| Jun 22, 2018 at 16:08 | comment | added | Nicolas | @Cubic Fair enough, the OP question itself was narrow. I was perhaps reading past the question itself: If someone is asking that type of question, then is seems that what they actually need is to gain a general understanding of best practices. (and, as Guy Schalat says above, best practices for your technology) | |
| Jun 22, 2018 at 14:53 | comment | added | Cubic | Actually, how to prevent SQL injection is a very narrow question with a very simple answer: Don't construct query strings from user controlled data. Avoiding this in the first place is easy enough, but of course finding places that do this in a large existing codebase can be tricky. | |
| S Jun 22, 2018 at 14:46 | history | suggested | Qsigma | CC BY-SA 4.0 |
nobody wants this to be a comment
|
| Jun 22, 2018 at 13:58 | review | Suggested edits | |||
| S Jun 22, 2018 at 14:46 | |||||
| Jun 21, 2018 at 19:23 | comment | added | Guy Schalnat | I love OWASP for understanding of why you are doing the right thing, but there are plenty of other resources that are specific to the OP's technology stack that are easier to start with. As with many security issues, the best thing is to not reinvent the wheel. The basic security practices of your chosen technology is the best start. | |
| Jun 21, 2018 at 18:05 | review | First posts | |||
| Jun 21, 2018 at 18:49 | |||||
| Jun 21, 2018 at 18:02 | history | answered | Nicolas | CC BY-SA 4.0 |