1.2 Protecting OpenText eDirectory Data and Storage

1.2.1 Protecting OpenText eDirectory DIB

Read through the following recommendations to protect your OpenText eDirectory database or Directory Information Base (DIB):

  • Always create an encrypted attribute policy to secure sensitive data. For more information, see Encrypting Data in OpenText eDirectory.

  • When using tools like ndscheck and nmasinst, avoid entering passwords in the command line. Instead, wait for the password prompt or use ndspassstore utility to provide password to the tools. For more information, see Setting the sadmin Password.

  • It is important to safeguard NMAS data, which includes password, secret store, configuration store, and more. To ensure maximum protection, it is recommended to use AES 256-bit key.

  • All Tree partitions should be replicated across multiple servers.

    With only one server storing and serving an OpenText eDirectory replica, a server failure would result in the loss of the partition and possibly serious consequences for the rest of the OpenText eDirectory tree. To avoid this, it is recommended that every OpenText eDirectory partition is replicated on at least three servers.

  • Take a backup of your OpenText eDirectory files.

    Managing OpenText eDirectory can be complex task, which makes it even more important to ensure that it is fully archived. To achieve this, it is recommended to use the OpenText eDirectory backup and restore utility. It is important to note that the built-in OpenText eDirectory backup requires a file-based backup to be performed as well. During the backup process, OpenText eDirectory data is saved to the server's file system. For more information on the processes required to take a full backup, see Backing Up and Restoring OpenText eDirectory.

1.2.2 Protecting Data in Transit

Read through the following recommendations to protect the data transmitted between two or more OpenText eDirectory servers: