Appendix A - Install Paths

Software Path

The Glasswall Meteor installation process places a shortcut to your desktop.

If the ‘all users’ option was selected, the shortcut will point to the following software installation path:

* C:\Program Files (x86)\Glasswall Meteor\Glasswall Meteor.exe

If the single user option was selected, the shortcut will point to the following software installation path:

* C:\Users[username]\AppData\Local\Programs\glasswall-meteor\Glasswall Meteor.exe

Working Directory Path

Glasswall Meteor creates a working data folder at the following location on each individual machine:

* C:\Users[username]\AppData\Roaming\glasswall-meteor

Clean File Path

You can change where your files are stored once they have been cleaned, however the default location is set as:

* C:\Users[username]\AppData\Roaming\glasswall-meteor\clean

Note: It is important to keep clean files separate from original source files, which could contain malware.

Audit Folder Path

The Glasswall Meteor retains a report of all actions performed, so that users can analyze what risky items or broken document structures were found in the source file.

The audit folder location can be found at:

* C:\Users[username]\AppData\Roaming\glasswall-meteor\audit_folder

Folders

Each processing job (which can include one or more files) will have a new folder created with an eight-character name. For each file processed as part of the job, a folder is created using a universally unique identifier (UUID) to record the artefacts that are created as part of the CDR process.

Four sub-folders are created under each UUID parent folder.

1. Report – This contains the master analysis XML file, which is the most detailed report about what was found in the original file.

2. Analysed – This contains a digest of information about sanitisation and remediation items that were found in the original file. The details are contained in json files within the folder. Where sanitisation occurs, potentially risky content has been removed. Remediation relates to deviations from the industry specifications for the file format, and how they have been repaired.

3. Original – This contains the original file that was provided to the Glasswall Meteor. Caution should be exercised as this file has not been protected by CDR. The document is preserved to protect the audit trail.

4. Clean – This contains an additional copy of the clean file, which has undergone CDR and is therefore safe to interact with.

Additional files (config.*) relate to the content management policy and the settings provided to the Glasswall engine during the CDR process for the file.