MetaDefender™ Storage Security 4.5.0

Release date: July 22, 2026

End of support: January 22, 2028

Highlights

MetaDefender Storage Security 4.5.0 introduces a redesigned user interface, centralized management through OPSWAT Central Management (OCM) v10, a new autoscaling engine, significant security enhancements, and multiple platform and storage integration improvements.

New Features

Redesigned User Interface

The application has been rebuilt using the Blue Line design system, delivering a modern user experience with:

• Updated Dashboard, Reports, Inventory, Jobs, Workflows, Settings, and Users pages

• Improved reporting with dedicated Threats, Sanitization, and Data Loss Prevention views

• Guided onboarding for first-time deployments

• Dark theme support

• Backward-compatible legacy URL redirects

OPSWAT Central Management (OCM) v10 Integration

MetaDefender Storage Security now supports centralized management through OCM v10, including:

• Instance enrollment and license management

• Remote configuration

• Deployment ID synchronization across managed environments

Autoscaling Engine

A new autoscaling engine dynamically adjusts system resources based on workload.

Key capabilities include:

• CPU, memory, and file throughput monitoring

• Scaling recommendations

• /healthz endpoint for health monitoring

• Dashboard visibility into scaling status

Supported deployment models include MetaDefender Core, Cloud and Distributed Cluster.

New SMB Service for Windows deployments

The Windows SMB Service is a new, fully in-house SMB client implementation for Windows deployments. Built with no third-party dependencies, it delivers improved reliability and resolves the connection issues found in earlier versions.

Security Improvements

This release includes multiple security enhancements, including:

• Fixes for OData injection vulnerabilities

• License forgery protection

• Penetration testing remediations, including JWT secret removal, improved SSO security, and sensitive data protection

• Non-root container enforcement for Kubernetes deployments

• Improved Windows file permission security

Platform Improvements

Platform updates include:

• Updated infrastructure components (RabbitMQ, Garnet, Alpine Linux)

• Improved job dispatcher with automatic recovery for orphaned scan jobs

• Configurable scan result retention policies

• Database growth monitoring and protection

• Decoupled scanning service architecture for cross-product reuse

• Prevention of overlapping scans within storage groups

• Optimized scanning and results storage for archives

Storage and Integration Improvements

Storage connectors have been enhanced with improved reliability and functionality, including:

• Better error reporting for NFS and SFTP

• Improved SharePoint Cloud real-time protection

• Microsoft Graph connection throttling for OneDrive and SharePoint

• NetApp ONTAP enhancements

• Autodiscovery support for all S3-compatible storage providers

• Updated Diode integration documentation

Telemetry

Telemetry has been renamed Usage Report and now includes:

• Kubernetes containerized collector

• Improved usage reporting accuracy

Resolved Issues

This release resolves several issues, including:

• Scheduled scans starting at incorrect times due to timezone offsets

• Recovery of cancelled or stuck scan jobs after service restart

• Dashboard threat counts matching report data

• Improved stability when scanning large file volumes

• RabbitMQ startup synchronization issues

• Improved error handling across storage integrations

Known limitation: Remediation counters on reports for scans performed before version 4.0.0

After upgrading from a version earlier than 4.0.0, reports for scans that completed on the older version may display inconsistent remediation counters:

• The Keep counter may show 0 even when files were kept.

• The Remediated counter excludes kept files, so it may show 0 when keeping files was the only configured remediation action.

All other values on these reports remain accurate, including the allowed and blocked file totals and the Move, Copy, Delete, and Tagging counters.

This limitation applies only to scans completed before the upgrade. Scans performed after the upgrade display all counters correctly.