Protegrity Data Protection method

The following table describes the fields for Protegrity Data Protection method.

Field	Sub-Field	Description	Notes
Protection Method		Specify the action performed (protection, unprotection, or re-protection).
Data Element Name		Specify the Data element used (for protection, unprotection, or re-protection).	The Data Element Name drop down list populates data elements from the deployed policy.
Encryption Data Element		Select to process the encryption data element
Default External IV		Default value to be used as an external initialization vector.
Reprotect New Data Element Name		New data element name that will be used to reprotect data.	The Data Element Name drop down list populates data elements from the deployed policy.
Reprotect New Default External IV		New default value to be used as an external initialization vector.
Default Username		Policy Username used for the user.	Ensure that you do not use the OS user alliance as a policy user. If the user is not specified, by default the data security operation will be performed by the alliance user. Ensure that the username does not exceed 256 characters.
Encoding		Encoding method to be used.
Codec		Based on the encoding selected, select the codec to be used.For more information about codec types, refer to the section Codecs.
Prefix		Prefix text to be padded before the protected value. This helps in identifying protected text from clear text.
Suffix		Suffix text to be padded after the protected value. This helps in identifying protected text from clear text.
Padding Character		Characters to be added to raise the number of characters to the minimum required size by the Protection method.
Minimum Input length		Number of characters that define if input is too short for the Protection method to be padded with the Padding Character.	If a data element is created with the Length Preservation property and it allows short data, then the input data will be tokenized if the input data is short. If a data element is created with the Length Preservation property and it does not allow short data, then the input data will not be tokenized and an error message will be generated.
Advanced Settings
	Permissive Error Handling	Click to expand.The underlying Application Protector API used in the DSG might encounter input that is not ideal in nature, such as, input too short. In such cases, you can use this option to decide how such inputs should be handled gracefully, as opposed to failing the entire data body processing.
	Enabled	Select to enable permissive handling of error generated due to distorted input.
	Error strings	Regex pattern to identify the errors that need to be handled permissively. You can also provide the exact error message.For example, if the error message on the Log viewer screen is “The input is too short”, then you can enter the exact message “The input is too short” in this field. Other error message examples are “The input is too long”, “License is invalid”, “Permission denied”, “Policy not available”, and so on. Based on the error message that you encounter and want to handle differently, the value in this field should be adjusted accordingly. For example, a pattern, such as, too short, too long, Permission denied can be used to gracefully handle the respective three errors.
	Output Data	Regex substitution pattern that dictates how output values for erroneous input values are substituted. For example, if this value is set to “????”, then the distorted input will be replaced with this value, thus allowing the rule to process instead of failing due to distorted input. Users may choose such fixed substitution strings to spot individual erroneous input data values post processing of data. You can also add prefix and suffix to the input. The regex must follow the “<prefix>\g<0><suffix>” REGEX substitution pattern. For example, if you want the input to be identified with the “#*_” as the input prefix and “_#*” as the input suffix, the regex pattern with be “#*_\g(0)_#* “.

• ←Previous
• Next→