CPM Server
CPM User:
- Password is stored in a local credentials file (on the CPM server) and is changed every time the CPM service is started.
PVWA Server
PVWAAppUser and PVWAGWUser:
- Password is stored in a local credentials file (on the PVWA server) and is changed every hour.
- This interval can be configured in
- web.config
- with the parameter:
- InternalUsersPasswordChangeInterval
Password change rules (default interval: 3600 seconds):
- When creating the credential file (using CreateCredFile.exe utility):
- If "Disable wait for DR synchronization before allowing password change" is set to yes, password is changed.
- If set to no (default), then:
-
- If DR replication never took place, password is changed.
- If DR replication occurred but the DR user is disabled, password is changed.
- If DR replication occurred and the DR user is enabled and replication executed successfully since last password change, password is changed.
PSM Server
PSMApp and PSMGW:
- Password is stored in a local credentials file (on the PSM server) and is changed every 24 hours.
- This interval is hard-coded.
Vault and Backup Servers
Backup and DR Users:
- Password is stored in a local credentials file (on the server initiating replication) and is changed every time the user logs into the vault (each replication interval).
NotificationEngine:
- Password is stored in a local credentials file (on the Vault server) and is changed every time the user logs in (each refresh interval).
Batch
- Internal user without a password.
- Does not perform an actual login action and cannot be impersonated, so it does not present a security risk.
EVD or PAS Reporter Server
- When EVD runs and utilizes a cred file, it will change the password in the vault and update the local cred file.
- Note: Testing this with the Administrator account may lead to a password change and potential account suspension.
AIM Credential Provider Component
CP users:
- Password is stored in a local credentials file (on the application server) and changes every 24 hours.
Other Users
Master:
- Password can only be changed by the Master user itself.
Administrator:
- Password can be stored in the vault and managed by CPM (Vault administrator's responsibility).
- Automatic management not recommended—it may cause the password to be unavailable when the vault isn't accessible.
- If managed, ensure Master password is available for potential recovery.
Operator:
- Password can be stored in the vault and managed by CPM (Vault administrator's responsibility).
Auditor:
- Password can be stored in the vault and managed by CPM (Vault administrator's responsibility).
Reporting on User Password Changes
To report and audit password change activity:
- Set the built-in or internal user's history to more than 0 days (default is 0). The user history dictates log retention.
- Set history for each user via PrivateArk:
- Tools > Users and Groups > Select User > Update > Time Limitations Tab > History
- Produce Activity Log report via PVWA:
- Include "Set Password" event (for users changing their own password)
- Include "CPM Change Password" event (for users managed by CPM)
- If changing passwords manually in PrivateArk (Administrator, Operator, Auditor, and Master) instead of using CPM, include "Reset User Password" and "Reset User Password Detailed Information" in the Activity Log report.