> For the complete documentation index, see [llms.txt](https://doc.keepnetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.keepnetlabs.com/next-generation-product/miscellaneous/allow-listing/allow-listing-in-other-security-solutions.md).

# Allow Listing in Other Security Solutions

## Allow Listing in Content Filtering (Proxy)

### Allow Listing Platform Addresses

Platform administrators must allow list **dash.keepnetlabs.com** and **api.keepnetlabs.com** on content filtering proxy solutions to use the products successfully.

{% hint style="warning" %}
If you have completed white labeling, it is sufficient to allow list the platform domain name that will be used to access to platform and api.keepnetlabs.com address.
{% endhint %}

### Allow Listing Phishing Simulation Domain Addresses

The domain names of the [Phishing Simulator](https://keepnetlabs.com/products/phishing-simulator) should be allow listed with content filtering (proxy) solutions to make sure that the domains can be accessed by the target users. If the target users can't access the phishing link in the network, the simulated phishing campaign might not be successful.

You can find the phishing simulation domains by logging into the platform and then go to **Phishing Simulator > Settings > Domains** page.

### Allow Listing in Data Loss Prevention (DLP)

System administrators may upload the target users' first name, last name, email address, department, or such other information to the platform; however, because [DLP](https://digitalguardian.com/blog/what-data-loss-prevention-dlp-definition-data-loss-prevention) can be very sensitive, the platform domain information should be allow listed to ensure DLP allows you to upload these pieces of information to the platform.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://doc.keepnetlabs.com/next-generation-product/miscellaneous/allow-listing/allow-listing-in-other-security-solutions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.