Review methodologies for a Secure Code Review Engagement.

Review methodologies for a Secure Code Review Engagement.

At Cobalt, we follow [OWASP Secure Coding Guidelines](https://owasp.org/www-project-secure-coding-practices-quick-reference-guide/) when it comes to Secure Code Review. Cobalt’s Secure Code Review is a systematic examination of source code. During the secure code review, Cobalt will take into consideration the risk the code presents, the purpose and context of code, the count of lines of code, and the programming language(s) used.

Here are some steps that can be included in a secure code review:

* Analyze the software composition: Inventory open-source components and flag potential issues using software composition analysis (SCA) tools.
* Perform Static Application Security Testing: Execute an automated SAST tool to identify common vulnerabilities.
* Manually validate the automated findings: Review and evaluate automated results to identify and validate true issues within critical functionality. **Note:** Some finding classes - such as code injection - cannot be validated without active engagement of the running application.
* Manually review business logic.
* Provide recommendations on reasonable mitigations that could address discovered issues or suggested code changes or upgrade paths to fix findings (when applicable).


:::info
**Note**

The tools that our pentesters use during each phase may vary from test to test.

:::

## **Software Composition Analysis**

During Software Composition Analysis (SCA), Cobalt analyzes open-source and third-party components for known vulnerabilities.

The six phases for SCA are:


1. Identification of Components
2. Vulnerability Detection
3. License Compliance
4. Version Analysis
5. Risk Assessment
6. Remediation Guidance


:::info
**Tools**

Cobalt pentesters may use Software Composition Analysis tools such as:

* Semgrep Pro
* OWASP Dependency-Check
* Snyk Open Source
* Trivy
* Sonatype
* Jfrog Xray

:::

## **Static Application Security Testing**

Cobalt leverages Static Application Security Testing (SAST) tools when performing secure code reviews which aids in the manual efforts when searching for patterns in large codebases. A benefit for using SAST tools is that it helps identify all instances of the vulnerability in the application. Some common findings found with a SAST tool are:

* SQL injection
* Cross-site scripting (XSS)
* Cross-site request forgery (CSRF)
* Insecure cryptographic storage
* Insecure communications
* Buffer overflows
* Authorization flaws


:::info
**Tools** Cobalt pentesters may use Static Application Security Testing tools such as:

* Semgrep Pro
* Bearer
* Checkmarx
* Fortify
* Snyk
* SonarQube
* Veracode

:::

## **Manual Review of Business Logic**

Performing manual secure code review is essential for discovering business logic flaws and to verify the results of the SAST tools. Below are some examples of the areas of focus during a manual Secure Code Review.

* Input Validation
* Output Encoding
* Authentication and Password Management
* Session Management
* Access Control
* Cryptographic Practices
* Error Handling and Logging
* Data Protection
* Communication Security
* System Configuration
* Database Security
* File Management
* Memory Management
* General Coding Practices




Secure Code Review Methodologies

Cobalt Methodologies Overview

Web Methodologies

API Methodologies

External Network Methodologies

Internal Network Methodologies

Mobile Methodologies

Cloud Configuration Review Methodologies

Cloud Pentest Methodology

Desktop Methodologies

AI/LLM Methodologies

Digital Risk Assessment Methodology

Methodologies

How to get started with Cobalt

Getting Started

Risk Advisories

Assets are what we pentest

Asset Types

Create an Asset

Assets

Pentests

Overview

Asset Details

Pentest Details

Scope & Test Period

Preparation

Create a Pentest

Pentest Process

Pentest States

Coverage Checklist

Pentest Expectations

Set Up an In-House Pentest

Complete an In-House Pentest (For Pentesters)

In House Pentests

Finding States

Severity Levels

Remediate Findings

Findings

Customize Your Report

Co-branded Reports

Contents of a Pentest Report

Reports

Engagements Overview

Digital Risk Assessment

Secure Code Review

Engagements

Insights

Planning

Attack Surface Monitoring (ASM)

Attack Surface

DAST Scanner Overview

Best Practices

Integrations

Partial Scans: Reduced Scope

Scans

Sequence recorder

Targets

Target Authentication

Extra Hosts

Blackout Period

DAST Scanner

Account Overview

Account Settings

Password Best Practices

Sign In to Cobalt

Troubleshoot Sign-in Issues

User Account

Collaboration Overview

Collaborate on Pentests

Groups

Manage Pentest Collaborators

Manage Notifications

User Roles and Permissions

Collaboration

Organization Overview

Manage Users

Your Cobalt Contract

Configure SAML SSO

How to Configure SAML 2.0 for Cobalt 

SAML Migration: Update Your Configuration

SCIM Provisioning Setup Guide

Configure Organization Settings

Organization

Track Your Credits

Cobalt Credits

Cobalt PtaaS Tiers

Credits

Cobalt Integrations Overview

Troubleshooting

Create Jira tickets for Findings

Send email notifications for Findings from Outlook

Create GitLab tickets for Findings

Create GitHub tickets for Findings

HTTP Connector

Import Assets from Google Sheets

Map Cobalt Pentest Finding Severity to Jira Issue Priority

Modify Jira Issue Summary to contain Pentest Title

Create Azure DevOps Work Item for Findings

Send MS Teams notifications for Findings

How to Guides

Connect your applications

Integration Builder

Synchronize Cobalt Severity Levels with Jira

Push Cobalt Findings to Jira

Jira Cloud Integration

Jira Data Center Integration

Troubleshoot Your Jira Integration

Switching to a New Jira Instance

Integrate Jira with Cobalt

Slack

Microsoft Teams

Webhooks

DefectDojo

Kenna Security

Vanta

Carried Over Findings

Create Test Finding

Cobalt API Overview

Create a Personal Cobalt API Token

Get an Organization Token

Revoke Your Personal Cobalt API Tokens

Create or Modify an Asset

Import Findings to Google Sheets

Cobalt API

Glossary

March 2026

February 2026

January 2026

November 2025 

August 2025

July 2025

June 2025

May 2025

April 2025

March 2025

January 2025

December 2024

November 2024

October 2024

September 2024

August 2024

July 2024

June 2024

May 2024

April 2024

March 2024

January 2024

What's New

Guide

Cobalt Product Documentation

Secure Code Review Methodologies

Share

Share

Secure Code Review Methodologies

Share

Share