Code audit
Guidelines
High-risk vulnerabilities
Low-risk vulnerabilities
not available
Tools
Source code auditing tools generally look for common vulnerabilities and only work for specific programming languages. Such automated tools could be used to save time, but should not be relied on for an in-depth audit. Applying such tools as part of a policy-based approach is recommended.[1]
See also
- Information technology audit
- Defensive programming
- Remote File Inclusion
- SQL injection
- Buffer overflow
- List of tools for static code analysis
References
- ^ "Static analysis at the end of the SDLC doesn't work" by Wayne Ariola, SearchSoftwareQuality.com, September 22, 2008
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |
 | This computer security article is a stub. You can help Wikipedia by expanding it. |