Securing Your PowerDesigner Environment

A typical PowerDesigner environment comprises a number of networked components that an administrator is responsible for securing through appropriate encryption and authentication policies.

Administrators should consider the following when planning to secure your PowerDesigner environment:

Encrypt communications with the repository (seeEncrypting PowerDesigner Network Communications).
Delegate repository user authentication to an existing LDAP server (see Connecting to an LDAP Server for User Authentication).
Enforce security and renewal of passwords by defining an appropriate password policy (see Defining a Password Policy).
Control access to specific repository features through rights (see Granting Rights to Users and Groups).
Control access to specific repository documents through permissions (see Granting Access Permissions on Repository Items).
Review proposed changes to repository documents through the use of change lists (see Change Lists).
Be aware of the possibility for emergency access to the repository (see Obtaining Emergency Access to the Repository).

The following forms of monitoring are available:

The list of repository activities (see Auditing Repository Activities).
The repository proxy log file (see Installation Guide > Installing the Repository Proxy).
If you are experiencing problems with memory usage or repository database performance, contact customer support to obtain access to further debugging features.

Encrypting PowerDesigner Network Communications
The majority of PowerDesigner Network Communications, including all those over which sensitive information may transit can be encrypted or are encrypted by default.
Password and Data Encryption
PowerDesigner supports encryption of both passwords and data for direct and proxy connections to a repository and for connections to other databases using most of the supported DBMSs via one or more of native, ODBC, and JDBC connection profiles.

Parent topic: Administering PowerDesigner