# Security Testing Overview

{% hint style="success" %}
🔥 Pynt's API Security Testing is fully available for **Business plan users**, and limited for **Starter plan users** (up to 10 API endpoints) 🆓.
{% endhint %}

## How Does Pynt Work?

Pynt leverages an **integrated shift-left approach** and **unique hack technology** using home-grown attack scenarios to:

* Detect real vulnerabilities 🔍
* Discover APIs 📚
* Suggest fixes for verified vulnerabilities 🛠️

{% hint style="info" %}
Pynt acts like a hacker: It deeply analyses normal API traffic to build a model and then generates simulated attacks, verifies if the attack succeeds, and determines whether your API is vulnerable.
{% endhint %}

***

## Why Use Your Functional Tests?

Unlike other platforms (e.g., fuzzing), Pynt uses traffic from your functional tests to create real attack scenarios. This approach allows Pynt to:

* Perform tests with **no configuration**, running in minutes ⚡.
* Provide an **accurate overview of vulnerabilities** with **near-zero false positives** 🎯.
* Leverage functional tests for **maximum API coverage**, as tests evolve with your APIs 🔄.

<figure><img src="/files/gjooGp9RIan99aQWyzQF" alt=""><figcaption><p>Pynt's testing flow</p></figcaption></figure>

## Getting Started

{% hint style="info" %}
🔗 **Get started with Pynt’s API Security Testing**: Pynt’s security engine goes beyond conventional measures, leveraging your existing API functional tests for proactive testing.
{% endhint %}

#### To get started quickly with Pynt, we recommend the following steps:

1. **Follow the** [**Prerequisites** ](/documentation/api-security-testing/prerequisites-for-running-pynt-scans.md)📋
2. **Run a single scan** - start directly from [here](https://docs.pynt.io/documentation/api-security-testing/www.pynt.io) or choose from the supported integrations [below](#available-integrations)🔍
3. **Integrate Pynt with your** [**CI/CD pipeline**](/documentation/security-testing-integrations/pynt-on-ci-cd.md) for continuous coverage 🔄&#x20;

***

### Available integrations&#x20;

Pynt leverages a sophisticated context-aware security engine that goes beyond conventional measures. By leveraging your existing tools and functional tests, it conducts proactive API security tests directly from your local machine:

* Get started with [**API testing tools**](/documentation/security-testing-integrations/pynt-with-api-testing-tools.md) 🛠️
* Get started with [**API testing CLIs**](/documentation/security-testing-integrations/pynt-with-api-testing-clis.md) 🖥️
* Get started with [**API testing frameworks**](/documentation/security-testing-integrations/pynt-with-testing-frameworks.md) ⚙️
* Get started with [**Burp Suite**](/documentation/security-testing-integrations/pynt-with-burp-suite.md) 🔍
* Get started with [**Browser testing**](/documentation/security-testing-integrations/pynt-with-browsers.md) 🌐

***

### Integrate API Security Testing Into Your CI/CD

{% hint style="success" %}
🔐 **Power of Continuous API Pentesting in CI/CD**: Integrating API security testing into your CI/CD pipeline ensures vulnerabilities are detected early in the development lifecycle.
{% endhint %}

We recommend to add Pynt into your CI/CD for continuous monitoring for API Security vulnerabilities. \
Pynt API security testing suite seamlessly integrates into existing development tools and CI/CD workflows.&#x20;

👉 [**Get started with integrating Pynt into your CI/CD**](/documentation/security-testing-integrations/pynt-on-ci-cd.md)**.**

<figure><img src="/files/1ewl9l2bpULxD1vZN1gG" alt=""><figcaption><p><a href="/pages/hSFiKgobe8gp7EOdc8TB"><em>Github Actions example</em></a>:</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pynt.io/documentation/api-security-testing/security-testing-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.