---
schema_version: "1"
id: 084c7d433c4ca01fa0b60e1cbabad3674eb5e862e64eee333e659823e192abad
title: Run Vulnerability Assessment and Penetration Tests
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/cloudhub/penetration-testing-policies.md
canonical_url: https://docs.mulesoft.com/cloudhub/penetration-testing-policies
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 02723ce58de0de0bec2246c43c76a89478d36398fb8676ba462a2615efd6a80f
description: MuleSoft Documentation Site
latest: true
---
---
product: CloudHub
---

# Run Vulnerability Assessment and Penetration Tests

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

If your company security policies require that you perform vulnerability and penetration testing
against Anypoint Platform, you can commence testing without notifying Salesforce beforehand.

All assessments must be performed in accordance with the
[Security Assessment Agreement](https://help.salesforce.com/s/articleView?id=000392845&type=1).

## Run Penetration and Vulnerability Tests

Because penetration testing can interfere with other tenants, MuleSoft allows penetration testing on
your workers but not on other Anypoint Platform services.

> [!IMPORTANT] Salesforce does not address vulnerabilities found with custom development. You must
> validate and fix any findings with your custom development.

### Prerequisites

Before initiating penetration testing:

- Enable static IPs for the app.

  By default, CloudHub workers don’t use static IP addresses, so you can’t test them because their
  IP addresses might change. For information about how to enable static IPs, see
  [Static IPs Tab Settings](https://docs.mulesoft.com/cloudhub/deploying-to-cloudhub#static-ips-tab-settings).

- Assign a security resource at your company to review and validate findings from the tests.

### Steps

1.  Run the penetration tests.

    The Security Assessment Agreement includes restrictions and requirements for testing.

2.  Have your security resource use the following documents to identify common false positives and
    security issues related to settings:

    - [Platform Security FAQ](https://help.salesforce.com/s/articleView?id=000383448&type=1)

    - [Salesforce Help](https://help.salesforce.com/s/)

3.  If your assessment generates vulnerability findings, complete validation for any automated
    finding. Send all outstanding validated security vulnerability findings to the Salesforce
    Security Team at [security.salesforce.com/contact](https://security.salesforce.com/contact).

    Include the following information in your email:

    - Confirmation number for your Security Assessment approved by Salesforce

    - Summary of all findings and the associated severity level of each finding

    - Detailed assessment report that notes each finding

    - Steps to reproduce the vulnerability

    - All applicable HTTP requests and responses

    - Explanation of why the example is considered a finding

### Reporting Security Vulnerabilities

To report security vulnerability findings, follow the
[Security Vulnerability Finding Submittal Guide](https://help.salesforce.com/s/articleView?id=000384043&type=1).
Security vulnerability reports that do not follow the required steps are rejected.

Salesforce does not address any security vulnerabilities in the following categories:

- Scan output from automated vulnerability scanning tools without a valid proof of concept

- Security bugs without valid proof of concept

- Vulnerabilities identified in old or deprecated versions of Mule runtime engine

- Vulnerabilities introduced via code customization made by your company

- Known security issues that don’t pose any risk

## See Also

- [Manage Applications on CloudHub](https://docs.mulesoft.com/cloudhub/managing-applications-on-cloudhub)

- [CloudHub](https://docs.mulesoft.com/cloudhub/)

- [Develop Applications for CloudHub](https://docs.mulesoft.com/cloudhub/developing-applications-for-cloudhub)

- [Deployment Options](https://docs.mulesoft.com/runtime-manager/deployment-strategies)