8.5.2. Manual installation of an update of signatures and/or anti-viral engines (update)

8.5.2.1. Introduction

This procedure describes the various options for updating the signature files of the solution's detection engines.

The graphical interface is described in the paragraph `Admin-GUM- Threat DB update` screen of the legacy web UI.

Note

Pour la mise à jour en mode online ou en mode local, voir la procédure de Configuring automatic update via GUM.

---

8.5.2.2. Prerequisites

• User : member of Administrator group

---

8.5.2.3. Preliminary operations

• Login to GCenter via a browser (see Connecting to the GCenter web interface via a web browser).

---

8.5.2.4. Procedure to update the signature files in manual mode

After pressing the `Threat DB update` command from the `Admin-GUM` menu, the following screen is displayed.

• Click on the `Browse` button (2) and select the previously downloaded package.

To update the engine	Use the file
CTI	cti.gwp
dga	dga.gwp
malcore	malcore.gwp
sigflow	sigflow.gwp
all engines	full.gwp

Note

If the selected file is not an update file (update) but an upgrade file (upgrade) then um message is displayed as the following example.

An error occurred during the last gum operation : Error : Gwp file decryption error, are you sure it is a TypeGwp.THREAT_DB_UPDATE ?
Please check your configuration/documentation. Otherwise, please contact the Gatewatcher Support.

• Click on the button (1) `Submit`.

  The following message is displayed: `Upload in progress x%, please wait`.

  The message `Upload done` indicates that the file has been loaded.
• Wait for progress bars to indicate that the transaction has been successfully completed.

  The button indicates `Please wait`.

  When the button changes back to `Submit`, the engine update has been applied to GCenter and GCaps.

---