---
title: "Cosmos Bishop Fox Continuous Penetration Testing"
slug: "cosmos-continuous-penetration-testing"
updated: 2025-03-18T22:50:01Z
published: 2025-03-18T22:50:01Z
canonical: "docs.databee.buzz/cosmos-continuous-penetration-testing"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.databee.buzz/llms.txt
> Use this file to discover all available pages before exploring further.

# Cosmos Bishop Fox Continuous Penetration Testing

Cosmos Continuous Penetration Testing, developed by Bishop Fox, automates data collection and analysis for networks, domains, and applications. By integrating with various tools, it streamlines vulnerability assessments, enhances threat intelligence, and offers customizable features and reporting, making it an asset for security professionals.

**Integration Method**: API

**Tables**: Detection Finding (2004), Vulnerability Finding (2002)

This integration supports the following events.

| **Event** | **Description** |
| --- | --- |
| Findings | Retrieves a list of findings, which includes details of exposed services, misconfigurations, vulnerable software, credential reuse, information disclosures, subdomain takeovers, and more. |

This integration supports the following versions.

| Cosmos Continuous Penetration Testing Version | v2.0 |
| --- | --- |
| Cosmos Continuous Penetration Testing API version | v1.0 |

## Prerequisites

- The user should have access to the Cosmos platform to generate API clients.
- The user should have access to the DataBee console.

## Configuration Overview

1. Generate client credentials with the required scopes.
2. Add the [Cosmos Continuous Penetration Testing data feed](/user-manual/docs/cosmos-bishop-fox-continuous-penetration-testing#databee-configuration) in the DataBee console with the below parameters.

| **DataBee Parameter** | **Cosmos Continuous Penetration Testing Parameter** |
| --- | --- |
| Client Key | Client Key |
| Client Secret | Client Secret |
| Organization UID | Unique ID |

## Cosmos Continuous Penetration Testing Configuration

Before you start configuring the data feed on DataBee UI, you will need to create the API Client and get the necessary information for API authentication such as Client ID and Client Secret. Follow these steps:

1. Logon to **Cosmos** Platform.
2. Click your **username** from the top right corner > Select **My profile**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/cosmos-bishop-fox-continuous-penetration-testing-mar2025-image-x8x9xrgr.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A01%3A30Z&se=2026-10-30T13%3A01%3A30Z&sr=c&sp=r&sig=32IioooSU0Rswt6AqLxgi%2FmOn2QdZAoHYOPhR%2BCj%2FD8%3D)
3. Navigate to the **API KEYS** tab, copy the **Unique ID** from the **Organization** section, **API** **URL** from **API Keys** section and then click the **Generate New API Keys** button to create API key. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/cosmos-bishop-fox-continuous-penetration-testing-mar2025-image-jcr4b6pa.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A01%3A30Z&se=2026-10-30T13%3A01%3A30Z&sr=c&sp=r&sig=32IioooSU0Rswt6AqLxgi%2FmOn2QdZAoHYOPhR%2BCj%2FD8%3D)
4. Copy the **Client Key** and **Client Secret**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/cosmos-bishop-fox-continuous-penetration-testing-mar2025-image-of645fqc.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A01%3A30Z&se=2026-10-30T13%3A01%3A30Z&sr=c&sp=r&sig=32IioooSU0Rswt6AqLxgi%2FmOn2QdZAoHYOPhR%2BCj%2FD8%3D)

> [!NOTE]
> Note:
> 
> The user needs to re-create the client secret when it expires (90 days). Additionally, once this step is completed, the user will not be able to view the API credentials again. Ensure the keys are stored in a secure location before proceeding.

## DataBee Configuration

1. Login to the DataBee UI, navigate to **Data** > **Data Feeds** and click the **Add New Data Feed** button. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/cosmos-bishop-fox-continuous-penetration-testing-mar2025-image-0o4cbwaz.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A01%3A30Z&se=2026-10-30T13%3A01%3A30Z&sr=c&sp=r&sig=32IioooSU0Rswt6AqLxgi%2FmOn2QdZAoHYOPhR%2BCj%2FD8%3D)
2. Search for the **Cosmos Continuous Penetration Testing** and click it as shown below**.** ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/cosmos-bishop-fox-continuous-penetration-testing-mar2025-image-5wleqyd5.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A01%3A30Z&se=2026-10-30T13%3A01%3A30Z&sr=c&sp=r&sig=32IioooSU0Rswt6AqLxgi%2FmOn2QdZAoHYOPhR%2BCj%2FD8%3D)
3. Click on the **API Ingest** option for the collection method. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/cosmos-bishop-fox-continuous-penetration-testing-mar2025-image-d8qjqllt.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A01%3A30Z&se=2026-10-30T13%3A01%3A30Z&sr=c&sp=r&sig=32IioooSU0Rswt6AqLxgi%2FmOn2QdZAoHYOPhR%2BCj%2FD8%3D)
4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/cosmos-bishop-fox-continuous-penetration-testing-mar2025-image-nyk75by6.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A01%3A30Z&se=2026-10-30T13%3A01%3A30Z&sr=c&sp=r&sig=32IioooSU0Rswt6AqLxgi%2FmOn2QdZAoHYOPhR%2BCj%2FD8%3D)
5. In the configuration page, confirm the following:

- Authorization Method: OAuth2
- API Base URL: paste the Base URL.
- Client Key: paste the **Client Key.**
- Client Secret: paste the **Client Secret.**
- Organization UID: paste the Unique ID.
- Event Types: preselected for all the event types that integration pulls.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/cosmos-bishop-fox-continuous-penetration-testing-mar2025-image-mmr4n6rr.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A01%3A30Z&se=2026-10-30T13%3A01%3A30Z&sr=c&sp=r&sig=32IioooSU0Rswt6AqLxgi%2FmOn2QdZAoHYOPhR%2BCj%2FD8%3D)

1. Click **Submit**.

## Troubleshooting Tips

- If you’re facing **invalid_client** or **unauthorized_client** issues this might be possibly due to incorrect credentials. Ensure the token is pasted correctly. Since you cannot view the token after the 1st time, re-create the token, paste it on a text editor to ensure no spaces or unexpected characters are included and reconfigure the DataBee feed.