Virus scan

How it works

The scan runs after the bytes land and before the notify. Encrypted archives often cannot be scanned. A failed scan is a failed delivery even if the hash matched. Quarantine is a separate bucket.

A client uploads a 30 MB ZIP. The hash matches. The scanner flags a macro. The portal shows quarantined, not received. They ask for a PDF instead. An auto-forward that ignored the flag would have sent the macro on.

How it differs

A virus scan is not a checksum. One looks for known bad content. The other checks you got the bytes you were sent.

Scanners lag new malware. A clean result is not a promise.

Still do not disable it.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For virus scan, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive virus scan files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.