Frequently Asked Questions

New Masking Rules can be added by following instructions here

At its core, CS:Govern is an intelligent dynamic SQL function and trigger generator that reacts to administrative changes to the selected fields to be Governed, the masking rules, and the associated compliance categories.  You can read more about it by going to this article.

We refer to CopyStorm as being CS:Govern “unaware” in the sense that by means of database triggers, data is protected without any changes to the CopyStorm runtime.  Due to the transactional nature of these triggers it is guaranteed that at no point in time is a user who does not have any of the protection rule compliance categories ever available to view encrypted fields in human readable form.  To learn more please refer to this article.

CS:Govern works seamlessly with CopyStorm/Restore.  Encrypted field data is restored to Salesforce in human readable form only if the Restore user has privileges (at least one of the compliance categories that was specified for those fields.)  For Restore purposes, as opposed to data analysis purposes, one should take care to use masking rules that are acceptable to Salesforce.  To learn more about this topic please go to this article.

Snapshotting is a powerful feature of CopyStorm that allows for point-in-time views of your Salesforce data.  CS:Govern was designed to work seamlessly with the Snapshotting feature.  Please read this article for more information about this topic.

Base64 Chunking was introduced as a CopyStorm feature to allow for virtually unlimited sizes of document content in such fields as Attachment.Body, ContentVersion.VersionData and other Salesforce object fields.  CS:Govern protected these fields by encrypting those chunks.  Please read this article to learn more about how this is handled by CS:Govern.

CS:Govern certainly does allow for this, and please read this article to learn more about how to do it.

System failures are inevitable no matter how rare they may occur.  CS:Govern was built to mitigate leaving record fields unprotected when these failures occur.  Read this article to learn more.