## API Pentest Methodologies

Review methodologies for APIs. Includes microservices.


:::info
Our pentesters test your assets rigorously.

:::

Cobalt follows an industry-standard methodology based primarily on the OWASP Application Security Verification Standard (ASVS), the OWASP Testing Guide, and the OWASP Top 10 risks. Cobalt’s approach combines manual and automated testing techniques, using best-in-class security tools to ensure comprehensive coverage.

This methodology focuses on identifying and mitigating security risks in API authentication, authorization, input validation, access control, cryptographic security, session management, and business logic flaws. The Core Pentesters evaluate the target API against these controls to uncover security weaknesses, including those cataloged in CVE databases and the OWASP API Security Top 10.

For details on what is out of scope, please refer to the [Out of Scope Testing](https://cobalt-io.brainfish.ai/en-us/articles/cobalt-methodologies-LTfYQiQvzV#h-out-of-scope-testing) documentation.

Penetration testing of an API includes the following stages:

* Target Scope Reconnaissance
* Business and Application Logic Mapping
* Automated API Enumeration and Scanning
* Authenticated Vulnerability Scanning and Manual Crawling
* Manual API Vulnerability Testing and Exploitation
* Ongoing Security Assessments and Continuous Testing
* Reporting, Triaging, and Retesting

## Target Scope Reconnaissance

During this phase, Cobalt’s pentesters gather and analyze publicly available information about the target application, including:

* **Endpoint Discovery:** Identify and catalog all API endpoints—both publicly documented and covertly exposed—to establish the complete attack surface.
* **Authentication & Session Workflows:** Map user and machine-level authentication flows and session management mechanisms, ensuring comprehensive validation of access controls.
* **Business Logic & Data Classification:** Chart critical workflows and classify data sensitivity, enabling prioritized testing of high-risk operations.
* **Reachability & Filtering:** Validate endpoint accessibility under varying network conditions and assess any applied filtering or throttling controls.

We do not perform any third-party testing during the engagement. This means functionality like third-party logins (e.g., “Login with Google,” “Login with Facebook”) is out of scope.


:::info
#### Tools

Cobalt pentesters may use tools such as:

* Burp Suite (Professional or Community)
* Zed Application Proxy (ZAP) Scanner
* Postman

:::

## Business and Application Logic Mapping

Cobalt’s pentesters conduct a manual assessment to map API functionalities, workflows, and security boundaries, which includes:

* **Access Control Matrix Construction:** Systematically define user roles and their permissible actions across each API endpoint and HTTP method, ensuring alignment between intended access policies and actual enforcement.
* **Sensitive Endpoint Identification:** Classify high-risk API operations that handle critical business functions or sensitive data, prioritizing them for in-depth security evaluation.
* **Business Logic Flaw Analysis:** Examine application workflows for deviations or gaps that can be exploited to bypass intended security controls or manipulate system state.

## Automated API Enumeration and Scanning

Cobalt’s pentesters use commercial and open-source API security tools to perform:

* **Schema-Driven Scanner Configuration:** Initialize automated tools with formal API specifications to guarantee exhaustive and structured testing.
* **Automated Endpoint Crawling:** Use crawler engines and collection runners to traverse every accessible path, both authenticated and unauthenticated.
* **Payload Generation & Fuzzing:** Inject both generic and context-specific inputs to provoke anomalous behavior or uncover hidden logic.
* **Contract & Schema Validation:** Automatically verify request and response structures against their formal definitions to detect deviations.
* **Misconfiguration Detection:** Identify common security oversights in API deployments through pre-configured or custom rule sets.


:::info
#### Tools

Cobalt pentesters may use tools such as:

* Burp Suite (Professional or Community)
* Zed Application Proxy (ZAP) Scanner
* Ffuf
* sslscan

:::

## Authenticated Vulnerability Scanning and Manual Crawling

Cobalt conducts authenticated vulnerability scanning using valid API credentials or tokens, allowing our pentesters to test your API from the perspective of a legitimate user. Within this phase, Cobalt pentesters focus on:

* **Session Token Handling:** Evaluate token lifecycle, integrity, and invalidation mechanisms to prevent unauthorized access and replay attacks.
* **Parameter Discovery:** Uncover undocumented or optional inputs that could expose hidden functionality or elevate privileges.
* **Deep Crawling:** Manually orchestrate chained and iterative requests to traverse complex workflows and trigger mass data exposure.
* **Parallel Session Crawling:** Operate multiple authenticated sessions concurrently to surface race conditions or state desynchronization issues.
* **Authentication Bypass Testing:** Manipulate request and environment parameters to circumvent intended authentication controls.

## Manual API Vulnerability Testing and Exploitation

Cobalt’s pentesters conduct manual API testing, using specialized tools to check for vulnerabilities related to:

* **Authentication & Authorization:** Manually verify authentication flows and enforce access controls, ensuring only authorized users can perform each operation.
* **Injection & Parsing:** Test untrusted inputs against backend interpreters to detect common flaws like SQL, command, or XML/JSON injection vulnerabilities.
* **Business Logic Abuse:** Assess application workflows for exploitable deviations that could compromise business rules or allow for abuse.
* **Data Exposure & Error Handling:** Evaluate response content and error messages to ensure sensitive data isn’t inadvertently disclosed.
* **Access Control Evasion & Privilege Escalation:** Exploit misconfigurations or logic gaps to elevate privileges or perform unauthorized operations.
* **Forced Parameter Switching:** Swap parameter values between requests (e.g., accountFrom ↔ accountTo) to test transaction logic for vulnerabilities.


:::info
**Tools**

Cobalt pentesters may use tools such as:

* Burp Suite (Professional or Community)
* Zed Application Proxy (ZAP) Scanner
* Postman

:::

## Ongoing Security Assessments and Continuous Testing

Cobalt provides real-time security feedback throughout the engagement, enabling:

* Collaboration with developers and security teams
* Ongoing risk analysis & vulnerability triaging
* Proactive remediation guidance

## Reporting, Triaging, and Retesting

Cobalt pentesters report and triage all vulnerabilities during the assessment. You can review details of all [findings](https://cobalt-io.brainfish.ai/en-us/articles/findings-6prkG67iav), in real time, through the Cobalt platform. In these findings, as well as in any [report](https://cobalt-io.brainfish.ai/en-us/articles/reports-YkC2da1roR), Cobalt’s pentesters include detailed information, including:

* Step-by-step remediation guidance
* Recommendations on how to improve your overall security posture

You can [remediate findings](https://cobalt-io.brainfish.ai/en-us/articles/remediate-findings-22WPR0Fnlv) during and after the pentest. Then you can submit findings for retest. Our pentesters test the updated components and retest vulnerabilities to ensure that there are no security-related residual risks.

API Methodologies

Cobalt Methodologies Overview

Web 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

Secure Code Review Methodologies

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

API Methodologies

Share

Share

API Methodologies

Share

Share