Contents x
- Glasswall CDR
- Embedded Engine
- About Embedded Engine
- Overview
- Getting Started
- API
- Embedded Engine Library
- Rebuild Library [Legacy]
- API Overview
- Configuration
- Additional Features
- XML Schema Definitions
- Glasswall Library - Modules
- Dependencies
- Glasswall Configuration Functions
- Glasswall Document Processing
- Glasswall Resource Management
- Glasswall Analysis Report
- Supporting Tools
- Engine Release Notes
- Appendix
- Terms of Service
- Halo
- About Halo
- Glasswall Halo FAQs
- Overview
- Getting Started
- Evaluation via minikube
- Deployment
- Deployment Overview
- Shared Responsibility Model
- Glasswall Artifact Registry
- Configuration Changes
- Authentication
- AKS
- AKS Setup Guide
- Prerequisites
- Step 1 - Set your Kubernetes context to AKS
- Step 2 - Create Glasswall Halo namespace
- Step 3 - Add secrets in Key Vault
- Step 4 - Enable your AKS cluster to access Key Vault
- Step 5 - Enable access to Glasswall's Artifact Registry
- Step 6 - Pull Helm charts
- Step 7 - Install and configure prerequisite components
- Step 8 - Install CDR components
- Amazon EC2
- EKS
- EKS Setup Guide
- Prerequisites
- Step 1 - Set your Kubernetes context to EKS
- Step 2 - Create Glasswall Halo namespace
- Step 3 - Create secrets in Secrets Manager
- Step 4 - Enable access to Glasswall's Artifact Registry
- Step 5 - Pull Helm charts
- Step 6 - Install and configure prerequisite components
- Step 7 - Install CDR components
- GKE
- GKE Setup Guide
- Prerequisites
- Step 1 - Set your Kubernetes context to GKE
- Step 2 - Create Glasswall Halo namespace
- Step 3 - Enable your GKE cluster to access Secrets
- Step 4 - Manage Secrets
- Step 5 - Enable access to Glasswall's Artifact Registry
- Step 6 - Pull Helm charts
- Step 7 - Install and configure prerequisite components
- Step 8 - Install CDR components
- OKE
- Single Node VM
- License Management
- Functionality
- Using Halo
- Halo Release Notes
- v2.7.0
- v2.6.2
- v2.6.1
- v2.6.0
- v2.5.4
- v2.5.3
- v2.5.2
- v2.5.1
- v2.5.0
- v2.4.15
- v2.4.13
- v2.4.12
- v2.4.11
- v2.4.10
- v2.4.9
- v2.4.8
- v2.4.7
- v2.4.6
- v2.4.5
- v2.4.4
- v2.4.3
- v2.4.2
- v2.4.1
- v2.4.0
- v2.3.0
- v2.2.1
- v2.2.0
- V2.1.4
- v2.1.3
- v2.1.2
- v2.1.1
- v2.1.0
- v2.0.7
- V2.0.6
- V2.0.5
- v2.0.4
- v2.0.3
- v2.0.2
- Single Node VM
- v2.6.2 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.6.1 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.6.0 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.5.4 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.5.3 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.5.2 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.5.1 RHEL9.4 RKE1.28.10+rke2r1 [Full]
- v2.4.13 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.12 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.11 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.10 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.9 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.8 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.7 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.5 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.4.5 RHEL8.8 RKE1.25.9+rke2r1
- v2.4.4 RHEL8.8 RKE1.25.9+rke2r1
- v2.4.4 RHEL8.8 RKE1.25.9+rke2r1 [Full]
- v2.3.0 RHEL8.8 RKE1.25.9+rke2r1
- v2.2.1 RHEL8.8 RKE1.25.9+rke2r1
- Appendix
- Terms of Service
- Constellations
- About Constellations
- Constellations FAQs
- Overview
- Getting Started
- Architecture
- Deployment
- Glasswall Artifact Registry
- AKS
- AKS Setup Guide
- Prerequisites
- Step 1 - Set your Kubernetes context to AKS
- Step 2 - Create namespaces
- Step 3 - Add secrets in Key Vault
- Step 4 - Enable your AKS cluster to access Key Vault
- Step 5 - Enable access to Glasswall's Artifact Registry
- Step 6 - Pull Helm charts
- Step 7 - Install and configure prerequisite components
- Step 8 - Install Glasswall Halo services
- Step 9 - Install Constellations components
- Constellations Release Notes
- Terms of Service
- Performance
- Meteor
- About Meteor
- Meteor Versions
- Getting Started
- Using Meteor
- Meteor Connect
- About Meteor Connect
- Minimum Requirements
- Install Glasswall Meteor Connect
- User Interface
- Preferences
- File Versions
- Support
- Storage Protocols
- Connect Mode
- Meteor Connect Release Notes
- Cloud Folders
- Meteor Release Notes
- Appendix
- Terms of Service
- Glasswall REST APIs
- Glasswall Research
Word Search & Redaction
- PDF
Contents
Word Search & Redaction
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
The Glasswall Embedded Engine provides a pattern matching capability in the following file formats:
- Microsoft Binary Office
- Office Open XML
- ASCII and UTF-8 plain text *(when
enable_text_support
is specifiedtrue
undersysConfig
)*
The search strings are configured via a policy file, where they can be specified as either a text
item or a regex
item:
- Text - Match only distinct words or numbers. Words and numbers are considered distinct if the character immediately preceding or succeeding the match is not a letter or digit respectively, meaning `or` will not produce a match when found in "ore", "word" or "door".
- Regex - Match anywhere the regular expression pattern is found. This includes matches within distinct words or numbers. For example, a regular expression of
r[aeiou]+
will match the "re" in "regular", "expression" and "anywhere".- The 'Word Search' feature does not support regular expression assertions.
- Avoid using
^
or$
in regular expressions, as these anchors may not work as expected for matching the start or end of lines within the file. - Regular expressions using lookaround assertions (lookahead/lookbehind) will not return any matches.
- Avoid using
- Regular expression matching is case insensitive by default in the current implementation.
- The regular expression matching engine uses boost/regex, which is based on Perl-style regular expressions.
- The 'Word Search' feature does not support regular expression assertions.
Precedence - Text rules will be evaluated in the order that they are encountered in the policy file, and always before the RegEx rules, which again will be evaluated in order that they are recorded
For every pattern matched, the following actions (textSetting) can be taken:
- Allow - Produce an XML analysis report specifying the number of matching strings within the file and their location
- Disallow - Report all matches and do not regenerate the input file if any are found
- Redact - Report matches and regenerate the input file with all instances replaced with a character specified in the policy file with `replacementChar`. *This action is only available for Microsoft Binary Office and Office Open XML files.*
- Require - Report all matches and do not regenerate the input file unless at least one match is found. *This action is only available for plain text files, and at least one must be specified.*
The APIs for Word Search support string, character based and regular expression matching. A full list of the Word Search API functions can be found in Word Search Library.
Learn more
- About Embedded Engine
- API Functions
- File Type Specifications
- License Management
- OS Features Compatibility
- Policy Management
- Supported File Types
- Supported Operating Systems
Was this article helpful?
Thank you for your feedback! Our team will get back to you
How can we improve this article?
Your feedback
Comment
Comment (Optional)
Character limit : 500
Please enter your comment
Email (Optional)
Email
Please enter a valid email