2016 Symantec Corporation This document may be freely reproduced & distributed whole & intact including this copyright
notice.
56
SV3800, SV3800B, and SV3800B-20 Security Policy
3.4 Module Management
The Crypto Officer can manage the SV3800/SV3800B/SV3800B-20 via the WebUI
(HTTPS over TLS), and the CLI. The Crypto Officer also has physical access to
the module and can perform limited management functions, as detailed in
. Detailed instructions on how to monitor and troubleshoot the SV3800 are
contained in the Blue Coat Systems SSL Visibility Appliance Administration and
Deployment Guide v3.8.2F, 3.8.4FC, or 3.10.
The Crypto Officer should monitor the SV3800/SV3800B/SV3800B-20 status
regularly. Any irregular activity or reported errors should be investigated by the
Crypto Officer and corrected. In the event that correction is not possible, the
customer should contact Symantec Support for advice.
In case the module’s power is lost and then restored, the key used for the AES
GCM encryption/decryption shall be re-distributed.
3.5 Module Zeroization
Whenever the module is being taken out of service, returned to Symantec for
service, or disposed of at the end of its life, the Crypto Officer must ensure that all
FIPS CSP data is zeroized. This is achieved by forcing the box to undergo a
factory default reset. The Crypto Officer must wait until the factory default reset
has completed and the system has returned to the bootstrap state to ensure that all
data has been zeroized.
The following techniques are used during zeroization:
•
Overwrite of entire disk with zeros.
•
Factory default reset can only be triggered during a reboot of the
appliance.
•
All keys and CSPs are zeroized.
•
No keys or CSPs are retained after zeroization.
•
During the boot process, no remote access to the appliance is possible.
After the factory default reset has been triggered during the boot process,
no additional commands can be given until the reset has been completed.
This prevents an attacker from influencing the zeroization procedure.
