|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
Putting the Tools to Work: How to Succeed with Source Code Analysis
May/June 2006 (vol. 4 no. 3)
pp. 80-83
| ASCII Text | x | ||
| Pravir Chandra, Brian Chess, John Steven, "Putting the Tools to Work: How to Succeed with Source Code Analysis," IEEE Security & Privacy, vol. 4, no. 3, pp. 80-83, May/June, 2006. | |||
| BibTex | x | ||
| @article{ 10.1109/MSP.2006.77, author = {Pravir Chandra and Brian Chess and John Steven}, title = {Putting the Tools to Work: How to Succeed with Source Code Analysis}, journal ={IEEE Security & Privacy}, volume = {4}, number = {3}, issn = {1540-7993}, year = {2006}, pages = {80-83}, doi = {http://doi.ieeecomputersociety.org/10.1109/MSP.2006.77}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Security & Privacy TI - Putting the Tools to Work: How to Succeed with Source Code Analysis IS - 3 SN - 1540-7993 SP80 EP83 EPD - 80-83 A1 - Pravir Chandra, A1 - Brian Chess, A1 - John Steven, PY - 2006 KW - code analysis KW - debugging KW - security VL - 4 JA - IEEE Security & Privacy ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MSP.2006.77
Code analysis tools can play an essential role in creating secure software. They can help catch common coding mistakes such as buffer overflow, cross-site scripting, SQL injection, and a variety of race conditions. With a certain amount of customization, they can also provide for deeper, application-specific inspection as well as a general audit against custom coding standards.
Index Terms:
code analysis, debugging, security
Citation:
Pravir Chandra, Brian Chess, John Steven, "Putting the Tools to Work: How to Succeed with Source Code Analysis," IEEE Security & Privacy, vol. 4, no. 3, pp. 80-83, May-June 2006, doi:10.1109/MSP.2006.77
Usage of this product signifies your acceptance of the Terms of Use.

