Short answer: No. Qumulo does not offer ICAP or CAVA, and Qumulo advises against inline ICAP scanning because it would add seconds of latency to file access. You protect Qumulo with antivirus on the clients, with scans from separate servers that read the shares, and, for near real-time coverage of new and changed files, with event-driven scanning based on Qumulo’s change notifications.
Why there is no ICAP on Qumulo
Many NAS systems pass each file to an external ICAP server before a client may open it. The file system waits for the verdict. On a scale-out system built for high throughput and low latency, that wait sits directly in the data path.
Qumulo’s security architecture paper discourages external ICAP agents for this reason: response times would typically rise to several seconds per file. Scaling ICAP to acceptable performance would also need a large fleet of scan servers. Instead, Qumulo points to the clients as the most likely point of an outbreak and recommends on-demand scans with established antivirus products.
If you are moving from a NAS that used ICAP or CAVA, you need a different design, not a different connector.
The four building blocks
1. Antivirus on the clients
Every Windows, macOS and Linux system that accesses Qumulo runs endpoint protection that scans files on open and on write. This catches most threats where they arrive and puts no load on the cluster.
The gap: storage admins can’t control or verify it. Unmanaged devices, servers without an agent, NFS clients and service accounts writing via applications are not covered. Files written before a signature existed are never rescanned unless someone opens them.
2. Scheduled or on-demand scans from scan servers
One or more servers mount the Qumulo shares via SMB or NFS and run a standard antivirus scan over them, at night or when you suspect an infection.
The gap: a full scan walks the entire tree. With hundreds of millions of files, a pass can take days and puts a heavy read load on the cluster. Anything written between two passes stays unscanned until the next one.
3. Event-driven post-change scanning
Qumulo can stream file system change notifications through its REST API. A scanning service subscribes to these events and scans each file shortly after it was created or modified, from separate scan servers.
Client access is never blocked, so there is no latency in the data path. Only changed files are scanned, so the load follows the actual change rate rather than the total file count. Scan capacity grows by adding scan servers.
The trade-off: scanning happens after the write, typically within seconds, not before the first read. Unchanged existing data is not scanned until it changes, so you combine this with an initial or occasional full scan.
4. Snapshots and snapshot locking for recovery
No scanner catches everything. Regular snapshots let you roll back after an incident, and locked snapshots cannot be deleted before they expire, even by an administrator, without a key held outside the cluster. This is your fallback, not a scanning method.
Comparison
| Client-side AV | Scheduled scans | Event-driven post-change scanning | ICAP | |
|---|---|---|---|---|
| Available on Qumulo | Yes | Yes | Yes, via change notifications | No |
| When files are scanned | On client access | Per scan window | Seconds after create or modify | Before access |
| Covers unmanaged clients | No | Yes | Yes | – |
| Load on the cluster | None | High during scans | Proportional to change rate | High, inline |
| Latency for users | None on the cluster | None, unless scans overlap work hours | None | Seconds per file |
| Storage admin can verify | No | Yes | Yes | – |
Which combination fits
- Baseline for everyone: endpoint protection on all clients plus regular, locked snapshots.
- Compliance requires storage-level scanning (“every file on the NAS is scanned”): add event-driven scanning for new and changed files, and one full scan when you start.
- Small or rarely changing data sets: scheduled scans can be enough, if the scan window and the gap between scans are acceptable.
How yuzuy does event-driven scanning
yuzuy’s Anti-Virus Integration is an event-driven post-change scanner for Qumulo. The yuzuy software receives Qumulo’s change notifications for the paths you protect and sends scan jobs to yuzuy Protection Clients on Windows servers. Each Protection Client runs your own antivirus engine via its command line and scans the file over SMB.
Detection, quarantine and reporting stay with your antivirus product and its management console. yuzuy adds no detection logic of its own. Customers run it with CrowdStrike, ESET, Microsoft Defender, Sophos, WithSecure and Bitdefender.
The Anti-Virus Integration is included in the yuzuy subscription at no additional cost.
Anti-Virus Integration · Event-driven malware scanning on Qumulo: architecture and sizing
FAQ
Does Qumulo support CAVA? No. CAVA is a Dell protocol for its own storage systems. Qumulo has neither CAVA nor ICAP.
Is client-side antivirus enough for Qumulo? It covers managed clients only. If policies require scanning at the storage level, or unmanaged systems and applications write to the cluster, add server-side scanning.
Does event-driven scanning slow down Qumulo? It adds no latency to file access, because it scans after the write. The cluster serves one additional read per changed file to the scan server.
