Overview of security considerations
As an administrator, you are responsible for the security of your HCL VersionVault deployment.
HCL VersionVault security depends on host and network security. Therefore, ensure that you have met the security requirements for your deployment infrastructure as well as those for VersionVault itself.
Authentication and identity management
- For information on Lightweight Directory Access Protocol (LDAP), see "Understanding LDAP Design and Implementation."
- For information on domain administration, see HCL VersionVault and Windows domains.
- If you use MultiSite, refer to Identities and permissions strategy for VOB replicas.
Encryption
- For instructions on configuring Secure Sockets Layer (SSL), see technote 541765 and technote 78711.
- For information about using Microsoft Bitlocker with HCL VersionVault, see technote 400481.
Authorization
- For information about HCL VersionVault authorization, see VOB and view access control. If you plan to use HCL VersionVault ACL authorization, consult operating system documentation for instructions on enabling OS-level ACLs.
- For information on platform-specific authorization administration, refer to Administering platforms for HCL VersionVault.
Auditing
You can use the cleartool lshistory command to list VOB database events affecting filesystem objects, hyperlinks, types, storage pools, the VOB object itself, and VOB replicas. Alternatively, use the HCL VersionVault History Browser for Windows.
Firewall configuration
If you use file-based packet transportation to synchronize VOB replicas, refer to Store-and-forward through a firewall (Linux and the UNIX system only).