Overview
    • PDF

    Overview

    • PDF

    Article summary

    Halo Storage Monitoring is a powerful service that enables automatic sanitization of supported file types at the point of upload. It can continuously monitor a wide range of cloud storage resources and sanitize files in real time.

    When a file is uploaded to a monitored resource, Storage Monitoring automatically:

    1. Downloads the file
    2. Sends it to the Glasswall Embedded Engine for sanitization
    3. Re-uploads a clean version of the file back to the original location

    Prerequisites

    • Halo v2.11.0 or later
    • A valid Glasswall Halo license
    • Publicly reachable cluster ingress address
      • Alternatively, you may whitelist the IPs of your chosen storage solution to ensure proper connectivity
    • Monitor must be configured for each storage resource
    • For SharePoint integration, Storage Monitoring must be registered with Microsoft Graph API

    Using Storage Monitoring

    To get started, follow our Storage Monitoring Setup Guide.
    The setup process differs for new and existing Halo installations.

    More technical details are available in the Storage Monitoring API documentation.


    Supported Cloud Storage Solutions

    Currently, Halo Storage Monitoring supports:

    More integrations will be added soon.


    Additional Information

    Glasswall Halo is powered by the Glasswall Embedded Engine, which rebuilds files to a safe standard while preserving usability.

    Learn more about how it works and why it's different from traditional detection-based tools.


    Licensing and Limits

    Accessing Storage Monitoring

    A valid Glasswall Halo license is required to access the Storage Monitoring API.

    Please contact us to obtain or upgrade your license.

    Daily Usage Limits

    Use of Storage Monitoring contributes to your daily file and data usage limits within Halo.

    • If the file processing limit is exceeded:
      • By default, the original file is re-uploaded unchanged
      • If configured to replace failed files, an error report is uploaded instead, explaining that the usage limit was exceeded.

    Was this article helpful?

    What's Next