# Static Code Scanning

- Source: https://support.icompaas.com/support/solutions/articles/62000225122-static-code-scanning
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [CyberSecurity Taxonomy](https://support.icompaas.com/support/solutions/62000112345) › [CyberSecurity-Topics](https://support.icompaas.com/support/solutions/folders/62000168169)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Static code scanning is the process of analyzing source code to look for security vulnerabilities. It can be done manually or using automated tools. Static code scanning is a form of code review.

  

**Steps in Code Review:**

  

1\. Gather information about the code - See the code and try to understand what it does.

  

2\. Check for errors and inconsistencies - Check for errors and inconsistencies in the code.

  

3\. Check for proper use of language and structure - Check for proper use of language and structure.

  

4\. Check for logical consistency and correctness - Check for logical consistency and correctness.

  

**Some of the most popular code review scanners include:**

  

1\. Checkmarx

  

2\. Veracode

  

3\. Whitehat Security

  

4\. Appscan

  

5\. Fortify

  

6\. Arachni

  

7\. Brakeman

  

8\. Ratproxy

  

9\. W3af

  

10\. N-Stalker

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.