Filter:

Submit Search

IMPORTANT
SNS 3.x versions have reached End of Maintenance since July 1st, 2024.
We recommend that you update your SNS firewalls to a version with maintenance to guarantee the protection of your infrastructure.

# Backup tab

Through this screen, you can create a manual backup or schedule an automatic backup of the firewall's configuration.

## Configuration backup

Backup filename | The suggested name of the backup is <firewall serial number>_day_month_year.na by default. This name can be changed if necessary.
Download the configuration backup | Click on this button to save the backup. The file will be saved in .na format. IMPORTANT If the firewall has a TPM that has been initialized, the download will fail as the backup file can only be downloaded from the CLI console. For more information, refer to the section Explanations on usage when the TPM is initialized, in the technical note Configuring the TPM and protecting private keys in SNS firewall certificates.

### Advanced properties

Password/Confirm | Set a password to protect your backup. You are advised to protect the backup file with a strong password. Keep it in a safe place, as restorations will not be possible without this password, and the file can neither be modified nor reinitialized. Our technical support team will not be able to retrieve or reinitialize it for you.
Password strength | This progress bar indicates your password’s level of security: “Very Weak”, “Weak”, “Medium”, “Good” or “Excellent”. You are strongly advised to use a combination of upper and lowercase letters, numbers as well as special characters.

## Configuration automatic backup

Automatic configuration backups are made regularly and securely. Information regarding the latest backup is also available in the firewall's Dashboard, in the Properties widget.

NOTE
The firewall must be covered by a valid maintenance contract in order to be eligible for this service.

When the firewall has a TPM that has been initialized, the backup will contain all private keys of certificates on the firewall, and the TPM-protected private keys that are included will be encrypted. For more information, see the section Trusted Platform Module.

Enable automatic backup | When selected, this checkbox allows a backup of your firewall’s configuration to be sent regularly.
Backup server selection | Cloud backup: these backups are stored in the cloud service infrastructure using encrypted channels. Customized server: these backups are stored on a customized server, depending on the criteria defined below.

The various settings of the service are listed below. Depending on your choice of backup server, it may not be possible to modify some settings.

Server's URL | Location used for storing backups. This URL is defined by the resolution of the Cloud server or customized server selected below combined with the access path indicated hereafter.
Backup server | Selects a customized server. Ensure that the resolution of the selected server corresponds to the one expected.
Backup filename | Enter the name assigned to the backup file.
Server port | Server’s listening port for receiving backups.
Communication protocol | Protocol used for sending backups, which may be HTTP or HTTPS. For HTTPS, a certificate needs to be entered so that the firewall may confirm the identity of the server.
Server certificate | If HTTPS has been chosen, import then select the server certificate in this field, so that the firewall can authenticate it. The aim of this is for the firewall to confirm the identity of the server before sending it the backup.
Access path | Depending on the sending method selected above, this access path for data on the server may be a folder (/directory/) for WebDAV methods (auth) or a script (/upload.php) for the POST method.
Send method | Basic and Digest modes (RFC 2617) allow the identification of the firewall on the server with the help of a login and password: auth basic: this mode sends the encoded password but in plaintext. It is therefore recommended for use with HTTPS communications. auth digest: this mode allows an identification but without sending the password in plaintext; this mode is more secure than the basic mode. It is recommended for use in HTTP communications. POST: as identification via this method is not managed, you are advised to use it with HTTPS communications.
Login | If a sending method with identification is used (auth basic or auth digest), this user name will allow the server to authenticate the firewall.
Password | If a sending method with identification is used (auth basic or auth digest), this password will allow the server to authenticate the firewall.
POST - control name | If the POST method is used, this field will indicate the control name in the header of HTTP packets.
Backup frequency | The automatic backup can be carried out every day, every week (7 days) or every month (30 days).
Password of the backup file | For security reasons, you are advised to encrypt the configuration file with a complex password. Keep it in a safe place, as restorations will not be possible without this password, and the file can neither be modified nor reinitialized. Our Technical Assistance Center will not be able to retrieve or reinitialize it for you.