API Pentest Methodologies

Review methodologies for APIs. Includes microservices.

Our pentesters test your assets rigorously.

We use the penetration testing methodologies listed on the page. If you want to know more about each methodology, navigate to the page associated with your asset.


The Cobalt team of pentesters do not need access to the underlying web application source code, unless you specify it as a requirement.

When you set up a pentest for an API asset in the UI, you’ll see the following in the Objectives text box:

Coverage of OWASP top 10, ASVS and application logic.

Learn more about these objectives from OWASP:

We look at application logic by working with your app.

Methodology Details

We base our methodology primarily on the OWASP Application Security Verification Standard (ASVS) and Testing Guide. Our team takes the following steps to ensure full coverage:

Select the key for more information on each step.

Target scope reconnaissance
Business and application logic mapping
Automated web crawling and web scanner configuration tweaking
Authenticated vulnerability scanning and manual crawling
Manual API vulnerability testing and exploitation
Ongoing assessments
Reporting, triaging, and retesting

API pentest flow

Additional Requirements

You’re welcome to define additional test objectives. If you follow best practices other than OWASP, ASVS, or OSSTMM, let us know. Include a link or other documentation. If it’s a “well-known” security practice, our pentesters probably already know them!

If you have special instructions for a pentest, add them later, under Special Instructions.

Was this page helpful?

Create an Issue

Last modified June.06.2023