Overview
    • PDF

    Overview

    • PDF

    Article summary

    Glasswall provides our clients the option to use our Glasswall API for web content traffic and downloads, thanks to our seamless integration with the Menlo Security Platform.

    There are endpoints exposed by Glasswall that enable Menlo deployments to integrate with the Glasswall Embedded Engine. These endpoints internally call the Asynchronous API, which carries out work to rebuild files sent to it when Menlo intercepts file downloads by users.

    The Glasswall – Menlo Security integration ensures that users can safely browse the internet and receive files free from threats – without compromising on usability or speed.

    Use Cases

    • Browser isolation
    • File uploads or downloads to block malicious activity
    • Targeted spear-phishing or generic phishing attacks
    • Zero Trust architecture
    • Compromised websites
    • Privacy protection

    How it works

    The isolation-powered, zero-trust solution routes all online activity through a remote cloud-based browser and treats all content as malicious. Glasswall Halo provides sub-second threat-removal capabilities when enabled as part of the Menlo Security Platform.

    Menlo%20Security%20Middleware%20Interface%20

    Endpoints

    The Menlo Security API consists of several endpoints which carry out specific functions.

    The endpoints and their descriptions are listed below.

    • Submit File for Processing
      This endpoint handles the submission of files from Menlo. For example when a user downloads a file, it is first submitted to this endpoint. This leverages the Asynchronous API's existing functionality to start processing files with POST api/v1/cdr-async.
      POST /api/v1/submit

    • Determine Processing Status of File
      This endpoint handles tracking the current processing status of a file within the Glasswall System. Each time this endpoint is called, it will use the Async API to get the processing status of the file.
      GET /api/v1/result

    • File Details
      Similar to the result endpoint, this endpoint uses the Asynchronous API to retrieve details about the requested files. It takes the replacement file for Menlo, and returns the successfully rebuilt file.
      GET /api/v1/file

    Was this article helpful?