Malware scanning
Checking a file somebody uploaded before anyone else can download it — where the scan runs, what happens to the file meanwhile, and who is told when it fails.
Overview
The Malware Scanning service scans a file over a REST call with ClamAV behind it. In CAP the attachments plugin submits every upload to it and withholds the download until the scan is clean.
No community artifact is documented here.
The answer in CAP is the same BTP service: the attachments plugin@cap-js/attachmentsAn official CAP Node.js plugin for attachment handling, with local database storage and AWS S3, Azure Blob or GCP Object Store integration.sap official, cap submits every upload to the Malware Scanning serviceSAP Malware Scanning serviceScans an uploaded file over a REST call, with ClamAV behind it — the check an attachments plugin runs before a file is served back.sap official, btp over REST, with ClamAV behind it, and withholds the download until the scan comes back clean.
Not covered: The service returns only a scan verdict; the plugin around it decides what happens next — retrying against the service's 30-concurrent-request limit, rescanning attachments older than three days, and marking an oversize file failed rather than resubmitting it.
No community artifact is documented here.
Artifacts
Content
Details
Coverage
For your agent
- Ref
capability:malware-scanning- JSON
- /capabilities/malware-scanning.json
- MCP
- Connecting an agent