Skip to content

Code Review

What is Code Review?

The systematic examination of source code to identify security vulnerabilities, coding errors, and deviations from secure coding standards before deployment.

Information Security

Each of these is named in at least one of the same controls as code review. The number is how many controls name both.

What the standards actually require on code review

Requirements naming code review across 6 standards, quoted from the control text.

PCI DSS 4.04 controls

Where bespoke and custom software is reviewed manually before it goes to production, each code change must be: examined by someone other than the person who wrote it, who is knowledgeable about secure coding practice and techniques for reviewing code;

6.2.3.1 · 6.2.3.1 Manual code review independence and approval →
BSIMM3 controls

Code Review. Code review is made mandatory for all projects so coverage is consistent.

CR1.5 · Make code review mandatory for all projects →

To minimise bugs and vulnerabilities the FI should adopt standards on secure coding, source code review and application security testing, covering secure programming, input validation, output encoding, access controls, authentication, cryptographic practices a...

monetary-authority-of-singapore-technology-risk-management-guidelines::6.1 · 6.1 Secure Coding, Source Code Review and Application Security Testing →
NIST SP 800-2182 controls

Perform the code review and/or code analysis based on the organization's secure coding standards, and record and triage the discovered issues.

SP800-218-PW.7.2 · Perform Code Review and Analysis →

Aim for every change merged into a product to go through a quality check, for example review by a second developer or deliberate error seeding.

secure-by-design-a-guide-for-manufacturers-cisa::DT-7 · Code review (SSDF PW.7.1, PW.7.2) →

Require peer review on every code change with explicit security review criteria, and use CodeGuru Reviewer or similar to augment human review.

SEC11-BP04 · Conduct code reviews →

Questions people ask about code review

What is Code Review?
The systematic examination of source code to identify security vulnerabilities, coding errors, and deviations from secure coding standards before deployment.
Why is Code Review important for compliance?
Code Review is a key concept in Information Security. Understanding code review helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 1,016 frameworks with 316K cross-framework control mappings.
Which compliance frameworks address Code Review?
Code Review appears in the requirement text of PCI DSS 4.0, BSIMM, Monetary Authority of Singapore Technology Risk Management Guidelines, NIST SP 800-218, Secure by Design: A Guide for Manufacturers (CISA). Across these standards we have identified 14 controls that name it directly, each linked to the control text on the compliance platform.
Where can I learn more about Code Review?
Explore our compliance framework pages to see how code review applies across different standards and regulations. Our implementation guides provide step-by-step guidance, and the compliance platform offers AI-powered analysis of how this concept maps across 1,016 frameworks.

See how Code Review applies across compliance frameworks

Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.

Written and maintained by Gerard Blokdyk, The Art of Service.