APPS- 3 Static Code Analysis

What is APPS- 3 Static Code Analysis Control?

Static code analysis is a method of examining source code before a program is run. This is a best practice usually performed as part of the code review process.

The most important factor is ensuring that the tool used to perform the analysis is running automatically every time and that follow-up actions are taken promptly (within a reasonable timeframe) to remediate any issues that arise. As an organization, you must prioritize issues to remediate and define the timeline for resolving them yourself; there are no strict mandatory timelines or prioritization requirements.

Available tools in the marketplace

The following listing is “crowdsourced” from our customer base or from external research. TrustCloud does not personally recommend any of the tools below, as we haven’t used them.

Vulnerability Scanning Tools

Veracode

Snyk

Reshift Security

SonarQube

Bandit

Brakeman

Available templates

TrustCloud has a curated list of templates, internally or externally sourced, to help you get started. Click on the link for a downloadable version.

• N/A: no template recommendation is made for this control.

Control implementation

NOTE: This control is automated by TrustCloud. Connect your system to enjoy the benefits of automation.

To implement this control manually,

1. You need to install a tool to scan and analyze all production code for vulnerabilities.
   1. The tool must be configured to run continuously or on a frequent schedule (the schedule is up to each organization to determine).
   2. The tool must be configured to send a notification or alert when issues are found.
2. Implement a formal and repeatable way to resolve any issues identified. The issues must be resolved promptly (timeliness is up to each company to define).

What evidence do auditors look for?

Most auditors, at a minimum, are looking for the below-suggested action:

1. Provide screenshots of the tool’s settings screen(s), showing that it is configured to continuously or frequently analyze your code.
2. Provide a remediation ticket or document outlining issues found through the tool that shows that actions were taken to remediate the issue.

Evidence example

For the suggested action, an example is provided below:

1. Provide screenshots of the tool’s settings screen(s), showing that it is configured to continuously or frequently analyze your code.
   The following screenshot shows an example of a tool.
   
2. Provide a remediation ticket or document outlining issues found through the tool that shows that actions were taken to remediate the issue.
   The following screenshot shows an example of remediation configuration (This can include more detailed evidence of remediation)