To perform a secure code scan, we must define the scanning rules based on common security issues and the programming language in question. It's fundamental to use keyword-driven expressions, regular expressions, or string operations for the scanning rules. The following table shows common risky APIs which may introduce security vulnerabilities and secure coding patterns which are indicators for potential security issues for various programming languages.
The false positive column indicates whether the search result requires further manual verification. For example, Low means that once the keyword is matched in the source code, the security issue can be confirmed without the need for further verification. Med means the identified patterns still require further verification:
|
Programming language |
Risky API or insecure code patterns... | |
