Title
Create new category
Edit page index title
Edit category
Edit link
Known Limitations
MetaDefender Core (Central Hub related features)
Is supported? | Support plan | |
|---|---|---|
A MetaDefender Core refuse tasks from RabbitMQ if staying unheathy | Yes | |
Download processed files from the file storage server (NAS) | Yes | |
Send quarantined files to MetaDefender Cloud in Central Hub model | TBD | |
Delete quarantined files in the file storage server (NAS) from MetaDefender Core instance | TBD | |
Multiple MetaDefender Core instances share the same session ID on Redis cache | Yes | |
Load shared among MetaDefender Core instances in extraction | Yes | |
Load shared among MetaDefender Core instances in compression | Yes |
Hub features
Is supported? | Support plan | |
|---|---|---|
Installer support | Yes | |
Docker container support | Yes | |
Authentication with local user account POST /login | Yes | |
Authentication with AD/LDAP account | TBD | |
Download Hub configuration | Yes | |
Upgrade MetaDefender Core instances & Central Hub | Dec 2024 | |
Asynchronous file analysis POST /file | See details | See details |
a. Attach file content in body for scanning | Yes | |
b. Validate user by session ID | Yes | |
c. Validate user by API key | Yes | |
d. Support webhook callbackurl | Yes | |
e. Support sanitized webhook callbackurl | Q1 2025 | |
f. Support scan by download link | Q1 2025 | |
g. Scan file in batch | Yes | |
h. Support skip by hash | Yes | |
i. Validate workflow rule | Yes | |
j. Validate payload size | Yes | |
Fetch processing result by data ID GET /file/<data_id> | See details | See details |
a. Fetch processing result by data ID | Yes | |
b. Validate user by session ID | Yes | |
c. Validate user by API key | Yes | |
d. Fetch scanning result of extracted files in an archive file | Yes | |
e. Return outdated details | TBD | |
f. Return | Yes | |
Fetch processing result by hash GET /hash/<hash> | See details | See details |
a. Fetch processing result by hash (md5, sha1, sha256, sha512) | Yes | |
b. Validate user by session ID | Yes | |
c. Validate user by API key | Yes | |
d. Fetch scanning result of extracted files in an archive file | Yes | |
e. Return outdated details | TBD | |
f. Return | Yes | |
Fetch processing history GET /stat/log/scan | See details | See details |
a. Fetch processing history | Yes | |
b. Validate user by session ID | Yes | |
c. Validate user by API key | Yes | |
Fetch Webhook status GET /file/webhook/<data_id> | See details | See details |
a. Fetch webhook status | Yes | |
b. Validate user by session ID | Yes | |
c. Validate user by API key | Yes | |
Download either sanitized or DLP processed files GET /file/download/<data_id> | See details | See details |
a. Download processed file | Yes | |
b. Validate user by session ID | Yes | |
c. Validate user by API key | Yes | |
Download quarantined file GET /quarantine/<file_id>/download | See details | See details |
a. Download quarantined file | Yes | |
b. Validate user by session ID | Yes | |
c. Validate user by API key | Yes | |
Download converted file GET /file/converted/<data_id> | ||
a. Download sanitized file only | Yes | |
Fetch available analysis rules GET /file/rules | ||
a. Fetch all available analysis rules | Yes | |
Batch processing | See details | See details |
a. Create batch | Yes | |
b. Close batch | Yes | |
c. Fetch batch result / status | Yes | |
d. Cancel batch | Yes | |
e. Download signed batch result | Yes | |
Cancel ongoing scan POST /file/<data_id>/cancel | Yes | |
Integration with MetaDefender Ecosystem | See details | See details |
a. Integrate with MetaDefender ICAP | Yes | |
b. Integrate with MetaDefender Email Security | Yes | |
c. Integrate with MetaDefender Kiosk | Dec 2024 | |
d. Integrate with MetaDefender Storage Security | Dec 2024 | |
Encrypt data at rest | Yes | |
Periodically clean up files and records (data retention) | Dec 2024 | |
Log rotation policy | Q1 2025 | |
Download SBOM report with new format | Q1 2025 |