DOCSEARCHbyAlgolia
Submit Docs

Glasswall Halo and Embedded Engine Library

website·Indexed 30 days ago

https://glasswalldocs.z6.web.core.windows.net

Documentation for Glasswall Halo version 2.9.0, including deployment guides for GKE, OKE, Hyper-V, and Proxmox VE, as well as Python API documentation for the Embedded Engine Library covering content management, security tagging, and rebuild processes.

Tokens
320.9K
Snippets
1.4K
Records
2.2K
Agent score
45%

What's inside Glasswall

  1. Overview of Glasswall Meteor Zero-Trust File Protection

    Glasswall Meteor implements a zero-trust approach to file protection using Content Disarm and Reconstruction (CDR). Rather than scanning for known malicious content, it treats all files as untrusted by validating, rebuilding, and cleaning each file to a safe, compliant standard to automatically remove potential threats. It supports connectivity with over 200 cloud and network providers, which can be further enhanced using the Meteor Connect tool for secure file transfers within existing environments.

  3. Overview of Glasswall Embedded Engine CDR

    The Glasswall Embedded Engine provides zero-trust file protection using Content Disarm and Reconstruction (CDR). Instead of searching for known malicious content, it treats all files as untrusted and validates, rebuilds, and cleans them against the manufacturer's 'known-good' specification. It is delivered as a software development kit (SDK) with an API for integration into applications.

  4. Overview of Glasswall Halo ICAP-based CDR

    Glasswall Halo provides an ICAP (Internet Content Adaptation Protocol) server that integrates with existing security infrastructure (such as proxy servers, firewalls, or VPNs) to perform Content Disarm and Reconstruction (CDR). The ICAP server acts as an intermediary: when an ICAP-enabled client detects a file, it sends it to Glasswall Halo for sanitization—removing potentially harmful elements and reconstructing the file—before returning the safe version to the client. This allows for real-time threat removal and automated file sanitization without user intervention.

  5. Overview of Glasswall CDR Content Management Policies

    Content management policies in the Glasswall CDR Platform allow developers to define configuration flags that govern the treatment of files and their contents during the CDR process. Policies enable the application of different security settings for diverse system scenarios and edge cases without requiring manual intervention or code changes between versions.

  6. Overview of Glasswall Meteor Zero-Trust File Protection

    Glasswall Meteor is an application that provides zero-trust file protection using Content Disarm and Reconstruction (CDR). Unlike traditional security tools that search for known malicious content, Meteor treats all files as untrusted. It validates, rebuilds, and cleans each file to a safe and compliant standard, automatically removing potential threats. For extended connectivity, Meteor Connect can be used to integrate with over 200 cloud and network providers to enable secure file transfers within existing environments.

  7. Introduction to Glasswall Meteor Zero-Trust File Protection

    Glasswall Meteor is a zero-trust file protection application that utilizes advanced Content Disarm and Reconstruction (CDR) technology. Unlike traditional security tools that search for known malicious content, Meteor treats all files as untrusted. It validates, rebuilds, and cleans every file to a safe and compliant standard, automatically removing potential threats before they can enter the environment.

  8. Overview of Glasswall Halo ICAP-based CDR

    Glasswall Halo provides an ICAP (Internet Content Adaptation Protocol) server that integrates with existing security infrastructure (like proxies, firewalls, or VPNs) to perform Content Disarm and Reconstruction (CDR). The solution sanitizes files by removing potentially harmful elements and reconstructing them to ensure they are safe before they enter or leave an organization. This allows for real-time threat removal and automated file sanitization without user intervention.

  9. Overview of Glasswall Halo ICAP-based CDR

    Glasswall Halo provides an ICAP (Internet Content Adaptation Protocol) server that integrates with existing security infrastructure (proxies, firewalls, VPNs) to perform Content Disarm and Reconstruction (CDR). The system sanitizes files by removing potentially harmful elements and reconstructing them to ensure they are safe before they enter or leave an organization. This allows for real-time threat removal and automated file sanitization without user intervention.

  10. Interpret Glasswall API response headers for Analyse and Rebuild

    When calling the Analyse and Rebuild API, the response headers provide critical metadata about the processing outcome, file integrity, and security reputation. These headers are returned with HTTP status codes 201 (Created), 206 (Partial Content), or 500 (Internal Server Error).

    Processing & File Metadata

    • x-processing-id: UUID representing the transaction/processing ID.
    • x-processing-status: The outcome of the file processing. Possible values: Rebuilt, Failed, Error, Allowed.
    • x-hash-{algo}-input: Hash value of the input file (where {algo} is the chosen algorithm).
    • x-hash-{algo}-output: Hash value of the output file (where {algo} is the chosen algorithm).
    • x-file-size: Size of the original input file in bytes.
    • x-applied-policy: The policy applied during Glasswall Halo processing.
    • x-error-reason: (Returned with 206) The reason why the file failed to be rebuilt.

    File Reputation Service

    • x-filereputation-responsecode: Response code from the reputation service.
    • x-filereputation-status: Response status from the reputation service.
    • x-filereputation-threatname: Malware family name if the file is detected as Malicious or Suspicious.
    • x-filereputation-threatlevel: Threat severity (0 = no threat, 1 = lowest, 5 = highest).
    • x-filereputation-trustlevel: Trust factor for detection results (0 = most trusted, 5 = least trusted).

    PDF Specifics

    • x-pdf-conform: Boolean indicating if the file was processed via Glasswall Conform.
    • x-pdf-conform-mode: The specific PDF conform mode used.

    Security Headers

    • x-content-type-option: Indicates MIME types in Content-Type headers should be respected.
    • x-frame-options: Indicates if a browser should be allowed to render the page in a frame/iframe.