> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/security-and-governance/malware-scanning.md).
# Malware Scanning
Learn about Malware Scanning in Couchdrop
## Introduction
Couchdrop can scan files for malware before they are uploaded to their destination storage.
Malware scanning is an additional paid add-on and is configured at the folder level. This lets you enable scanning only for locations where files need to be checked rather than applying it across your entire Couchdrop account.
If Malware Scanning is not enabled for your account, contact [**sales@couchdrop.io**](mailto:sales@couchdrop.io).
## Enabling Malware Scanning
Once Malware Scanning has been enabled for your account, you can enable it on individual folders.
Scanning must be enabled on a folder before files uploaded to that location will be scanned.
Malware Scanning can be used with any storage platform that can be connected to Couchdrop.
## How Malware Scanning works
Couchdrop uses **ClamAV** to scan files for malware.
Files larger than **1 GB** cannot be scanned.
Scanning behavior is managed by Couchdrop and cannot be customized by administrators.
## Malware Scanning events
If a malware scan fails, Couchdrop records an event in the reporting section of the [Admin Portal](/administration/admin-panel-and-user-mode.md).
These events appear as:
`malware_scan_failed`
Use these events when reviewing malware scanning activity or investigating failed scans.
## Frequently Asked Questions
Why should I use Couchdrop Malware Scanning?
Malware Scanning provides an additional layer of protection when receiving files from external parties.
It can be particularly useful when files are entering internal storage or automated file pipelines and you want them scanned before they reach their destination.
How do I enable Malware Scanning?
Malware Scanning is an additional paid add-on. If it is not enabled for your account, contact [**sales@couchdrop.io**](mailto:sales@couchdrop.io).
Once enabled, Malware Scanning can be configured on individual folders.
What malware scanning engine does Couchdrop use?
Couchdrop uses [ClamAV](https://www.clamav.net/) for malware scanning.
Is there a file size limit?
Yes. Malware Scanning is limited to files that are **1 GB or smaller**.
Can administrators modify the scanning behavior?
No. Malware scanning behavior cannot be customized by administrators.
Where can I find Malware Scanning events?
Malware scanning failures appear in the reporting section of the Admin Portal as `malware_scan_failed` events.
Which storage platforms support Malware Scanning?
Malware Scanning can be enabled for folders backed by any storage platform that can be connected to Couchdrop.
After connecting the storage platform, enable Malware Scanning on the folder where scanning is required.
---
# 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.couchdrop.io/security-and-governance/malware-scanning.md?ask=&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.