Some of the more rigorous compliance expectations that your business should be adhering to, under the various regulations, include lawful possession of data, fairness in the use of that data, and transparency about the data that you have. Some other requirements are that you only use the data for its originally agreed purpose, that you only hold the absolute minimum of data that you need, that you retain it only for so long as you previously agreed or until the data no longer serves its original purpose, that the data be correct and proper and not exposed publicly and that if any of these facets are not adhered to, that the persons to whom that data relates, will be appropriately informed.
The fines and penalties associated with violations and failures can be extremely punitive and actually put organizations out of business.
The Pretectum Customer Master Data Management platform addresses aspects of this defensive strategy by offering five key characteristics to the customer master data management practice that support your CMDM function in being compliant.
Encryption – all data stored in the Pretectum CMDM platform and as such, data at rest, is encrypted by default in a secure database
Access Control – all access to objects within the Pretectum CMDM platform is granted through a “least permissions” model and is granted to users via an identifier with an accompanying password for UI access, and the same with a token via API. Users are then further restricted based on a hierarchy of permissions based on the organizational assignment and very fine-grained permissions within that organizational assignment.
Identifiable users – all users are identified by way of an email address that is part of the domain associated with the Pretectum platform subscription.
Data Quality built-in – depending on the way schemas are defined, all data either confirms or conflicts with self-defined business rules and configuration. The ability to observe the compliance of a given record with the specific rules defined, is observable at every stage in the platform.
Verbose Auditing and change logging – a verbose history of changes and events is tracked for all data and all objects in the platform including changes to user permissions and access.
