Bacula Enterprise Edition:

State-Of-The-Art Security.

Bacula Enterprise Edition is used by leading governmental and banking institutions because of its outstanding security qualities.

Below are listed some of the security layers built into Bacula Enterprise Edition:

Key security methods for Bacula Enterprise Edition:

* open source code: each line of code is available for in-house verification

* 256k AES encription can be enabled
* Configurable TLS (SSL) communications encryption between each component. Bacula can encrypt data to be stored on Volumes. It also uses OpenSSL for this purpose.
* Bacula can encrypt data over the wire.  To do so it uses OpenSSL, which has been certified.
* Configurable Data (on Volume) encryption on a Client by Client basis.
* Bacula has a tripwire like verification process that can be used to detect intrusions (changed systems files, new programs loaded, etc.).
* If required, there are directives that can restrict what addresses Bacula binds to.
* You can enable the use of tcp wrappers to restrict access to Bacula.
* Bacula uses its own internal routines to detect buffer overflows (a typical means of attack).

Some of the methods that Bacula Enterprise Edition uses to verify the authenticity of the data backed up:

* SHA 1 hash code, when enabled.
* Verification of files previously cataloged, permitting a Tripwire like capability (system break-in detection)
* Computation of MD5 or SHA1 signatures of the file data if requested