The following text boxes contain data masking rules which can be used to protect data which is classified as "personal identifiable data" (or PII), personal sensitive data or commercially sensitive data. The data masking rules determine information object names or patterns, which should always be masked by Zend Server before it is stored or persisted. The configuration below applies to data storage by the following components: Code Tracing, Monitoring and Z-Ray.
{{ settings.fields['zend_codetracing.allow_from_all'].description }}
This area defines functions and methods which will mask all their arguments and return values. The definitions are complete words or wildcards. Functions can be assigned to Classes or Namespaces. Using * wildcard after a class name will mask all methods in it.
This area defines masking for Global Array keys and SQL bound values (shown in Z-Ray data). You can define complete words, prefixes, suffixes and wildcards, to match the sensitive keys. Matching is done without case sensitivity, so you don't need to worry about upper/lower case definitions in your masking rules.
This area defines functional data (parameters, return values and values in exceptions), which cannot be defined by specifying the functions as they can be random, or many (cross functional values). These rules can also be used when the values format is too generic and should be defined by its pattern and not its containers.