Security and Access Control
All data managed with PureCM is stored in a secure, fast and reliable database. To preserve your audit trail, the PureCM server fully controls access and changes to these objects.
Changesets are self-contained and fully atomic, so submits or merges are much safer. Any change is applied to the database as a whole or not at all - to protect its integrity. As a development manager, you don't need to worry about which files you need when merging a bugfix or rolling back a change that introduced a bug, because they're automatically grouped in the changeset.
Password and Domain Authentication
Any user wanting to access data in PureCM must authenticate first. PureCM administrators can create users with user/password or SSL/TLS certificate authentication. If running the PureCM server on Windows, users can authenticate with domain authentication. On Linux, PAM authentication is fully supported. Of course, PureCM also supports multiple authentication methods per user, e.g. for home and office use.
Policy-Based Access Control
With PureCM, you can define permissions based on policies, also known as access control lists (ACL). You can set permissions against any hierarchy level of the PureCM database - from the global repository level to projects, versions, folders and files. To facilitate administration, permissions can be inherited from the parent unless overwritten.
Backups and Integrity Checks
PureCM creates a predefined number of backup snapshots, which is the fastest way to restore a repository. Alternatively, existing backup solutions can be used to save PureCM's database files, which is particularly attractive with the newly supported SQL-type databases. For added peace of mind, administrators can run automated integrity checks using the tool's database utility "tdbutil".