> 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/33/vulnerability-management/malware-scanning.md).

# Scan for Malware

Besides detecting software vulnerabilities (CVEs) and compliance issues (such as images configured to run as root), Prisma Cloud also detects malware in your container images. No special configuration is required to enable this feature.

To perform malware analysis, Prisma Cloud uses the inputs from:

* [Intelligence Stream](/admin-guide/33/vulnerability-management/prisma-cloud-vulnerability-feed.md)—Searches the feed for a match against the hash for the executable.
* [Wildfire service](/admin-guide/33/configure/wildfire.md)—Queries the WildFire service for a match against the hash for the executable. If there is no match and upload is enabled, the file is uploaded for analysis.

  WildFire is only supported for image scanning when used in CI.
* Custom feeds—Searches for a match for the executable hash against any [custom malware data you import](/admin-guide/33/configure/custom-feeds.md#malware-signatures) for image scanning.

Malware scanning and detection is supported for Linux container images only. Windows containers are not supported.

## Detecting malware

The image scanner looks for malware in binaries in the image layers, including the base layer. When Prisma Cloud detects malware in an image, it includes the malware information as a compliance violation in the image scan report.

To review the results of an image scan:

1. Open Console, then go to **Monitor > Vulnerabilities > Images**.
2. Click on an image to get a detailed report from the last image scan.
3. In the detailed report, click on the **Compliance** tab.

   Issues with vulnerability ID 422 means that your image contains a file with an md5 signature of known malware.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.prismacloud.io/admin-guide/33/vulnerability-management/malware-scanning.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.