> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/configure/custom-feeds.md).
# Custom feeds
You can supplement the Prisma Cloud Intelligence Stream with your own custom data, including:
* Suspicious or high-risk IP addresses
* Malware signatures
* Trusted executables
* [Custom vulnerabilities for proprietary software components](/admin-guide/vulnerability-management/scan-images-for-custom-vulnerabilities.md)
* Allowed CVEs
For each data type, you can add individual entries to a table from the Console web interface, bulk upload a list from a CSV file, or submit a JSON object using the Prisma Cloud API.
## Supplementing the IP reputation list
You can supplement the Prisma Cloud Intelligence Stream with your own list of suspicious or high-risk IP addresses that you want to ban on your network.
1. Open Console.
2. Go to **Manage > System > Custom Feeds**.
3. Click **IP Reputation Lists**, and either click **Add IP** or **Import CSV**.
Your list of banned IP addresses is immediately enforced when your data is imported. A default runtime defense rule, **Default - detect suspicious runtime behavior**, logs an alert when a container tries to connect to a banned IP address.
You can manually add one entry at a time, or do a bulk upload from a CSV file. The maximum file size for a csv is 20MB.
The first line in your CSV file must be a header record that contains the field names. Specify one IP address per line. For example:
```
ip
99.104.125.48
101.200.81.187
103.19.89.118
```
4. Review the default rule
Go to **Defend > Runtime > {Container Policy | Host Policy}**, then click manage for the **Default - detect suspicious runtime behavior** rule. You should see that **Prisma Cloud Advanced Threat Protection** is set to **On**.
## Create a list of malware signatures and trusted executables
You can supplement the Prisma Cloud Intelligence Stream with your own custom malware signatures and trusted executable list. The trusted executable list is a mechanism to address potential misidentification of legitimate files as malware.
You can add MD5 hashes of custom malicious executables to the malware signatures list, it enables you to monitor malware that you want to alert or block in runtime rules.
Malware scanning and detection is supported for Linux container images and hosts only. Windows containers and hosts are not supported.
When you add MD5 hashes (signatures of binaries) to the trusted executables list, it enables you to ensure that a legitimate binary is not potentially identified as malicious by file system based defense capability in runtime rules.
The trusted executable list does not apply to other runtime defense capabilities, such as process runtime protection. To exclude files from other runtime detection capabilities use the allowed list in the [runtime defense section](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/compute-edition/34/admin-guide/runtime-defense/runtime-defense.md).
1. Open Console.
2. Go to **Manage > System > Custom Feeds**.
3. Select **Malware signatures** or **Trusted executables**.
4. Choose how to add the MD5 hashes for malware signatures or trusted executables.
The MD5 hashes you add to either list of custom feed, are used in all subsequent image scans. It is also used immediately by the runtime defense file system sensor, which assesses all writes to the host and container file system.
1. For **Add MD5**, you can manually add one entry at a time.
2. For **Import CSV**, you can bulk upload from a CSV file.
The maximum file size is 20MB.
The first line in your CSV file must be a header record that contains the field names.
Specify one entry per line. Each entry must include the MD5, followed by a good description to identify why the MD5 is trusted ( in the case of trusted executables) or is known to be malicious (in the case of malware signatures).
For example:
```
md5,name
194836fbe0f121a25b145e55e80cef22,legitimate binary built in-house
0aeb0cac186a81a6ac45776d6b56dd70,test file
33cc273ae3aa8bce6a22c92e7d11f63a,benign file
```
5. Review the default rule.
A default runtime defense rule, **Default - detect suspicious runtime behavior**, logs an alert when malware is detected using signatures from the Prisma Cloud data set or your custom data set.
To review the default rule, go to **Defend > Runtime > {Container Policy | Host Policy}**, then click manage for the **Default - detect suspicious runtime behavior** rule. You should see that **Prisma Cloud Advanced Threat Protection** is set to **On**.
## Allowing CVEs globally
Some organizations have have very sophisticated CI pipelines that encompass many teams and products. When your security team concludes that a CVE doesn’t impact the organization, they want to dismiss it globally without having to manage individual rules or exceptions.
The CVE Allow List lets you allow CVEs system-wide. Any entry in the CVE Allow List affects all flows in the product, including twistcli, the Jenkins plugin, registry scanning, deployment blocking, Vulnerability Explorer, and so on. Adding a CVE to this list effectively filters it out from the data in the Prisma Cloud Intelligence Stream before it’s used by the scanner.
The CVE Allow List takes precedence over any rule that’s been created under **Defend > Vulnerabilities**. It is a feature designed to complement rules. Rules also let you allow a CVE, but more granularly, by scoping them to specific resources or parts of your environment.
1. Open Console.
2. Go to **Manage > System > Custom Feeds**.
3. Click **CVE Allow List**, and either click **Add CVE** or **Import CSV**.
You can set an expiration date for the CVE, if you want to set a time restriction for when it should no longer be allowed.
## Test Prisma Cloud malware detection capabilities
Safely simulate malware in your environment to test the malware detection capabilities on Prisma Cloud.
### Configure a custom malware feed
Set up a custom feed by uploading the provided CSV file to Prisma Cloud Console. This file specifies the MD5 signature for a file that will be considered malware for the purposes of this demo.
1. Download [*malware.csv*](https://cdn.twistlock.com/docs/attachments/malware.csv).
2. In Console, go to **Manage > System > Custom Feeds > Malware Signatures**.
3. Click **Import CSV**, and upload *malware.csv*.
### Detect malware at runtime
Test how Prisma Cloud detects malware being downloaded into a container at runtime.
**Prerequisites:** The default runtime rule, **Default - alert on suspicious runtime behavior** under **Defend > Runtime > Container Policy** is in place. If you have deleted or changed the default rule, create a new one.
1. Go to **Defend > Runtime > Container Policy**, and click **Add rule**.
2. Enter a name for the rule.
3. In the **General** tab, verify **Prisma Cloud Advanced Threat Protection** is **On**.
4. In each of the **Process**, **Networking**, **File System**, and **System Calls** tabs, set **Effect** to **Alert**.
5. Run a container and download malware into it.
```
$ docker run -ti alpine sh
/ # wget https://cdn.twistlock.com/docs/attachments/evil
```
6. Look at resulting audit. Open Console and browse to **Monitor > Events > Container Audits**. You will see a file system audit that says malware was detected.
---
# 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://docs.prismacloud.io/admin-guide/configure/custom-feeds.md?ask=&goal=
```
`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.