Servers should be kept in a physically secure location with access by authorized personnel only.

The corporate network should be physically secured against eavesdropping or packet sniffing. Any packets associated with the administration of BCC should be the most secured.

Access to BCC configuration settings and logs should be restricted. This includes file system access rights, FTP access, access via Web utilities, SSH, and any other type of access to these files.

Services that are used to send BCC data to other servers or e-mail accounts or that protect BCC data should be examined periodically to ensure that they have not been tampered with.

When synchronizing cluster or user information between servers outside the corporate firewall, the HTTPS protocol should be employed. Because resource script information is passed between clusters, strong security precautions should be taken.

When a BCC is administered by users outside of the corporate firewall, the HTTPS protocol should be used. A VPN should also be employed.

If a server is accessible from outside the corporate network, a local server firewall should be employed to prevent direct access by a would-be intruder.

Audit logs should be kept and analyzed periodically.