@ANIRBANDATTA  can you give us the exact version of PRPC 6.2 that you have installed?

Did you check other forum posts such these ones?

Can ParameterPage values be supressed for PEGA0001 alert log entries?

Issues during suppressing/masking the ParameterPage values for PEGA0001 alert log entries

Suppress parameters in the alert event (Support article SA-9328)

I was not able to find the option to add these as DSS.

Add the following setting to prconfig.xml to suppress the sensitive property values:

<env name="alerts/database/operationTimeThreshold/suppressInserts" value="true" />

This setting will suppress the sensitive property values (and replace them with question marks).

To suppress information in parameters, add the following setting to prconfig.xml:

<env name="alerts/general/includeparameterpage" value="false" />

This setting determines if the parameter page of the top-most stackframe will be included in the ALERT log when the alert is generated.

Re-start the server after changes made.

the DSS prconfig/alerts/parameterpage/remoteFilterType/default should be set to "obfuscate". The default value is "allowed"

If you are on Pega 6.2. SP2 we recommend that you request HFIX-21245   for 6.2 SP1 it is HFix-5683  (for 7.2      HFIX-66817  )

updates to allow the following DSS settings to work to either suppress the parameters on the alert: Pega-Engine

prconfig/alerts/general/includeparameterpage/default with a value of "false" or to filter on specific keywords (AccountNumber;SSN; below):

Pega-Engine prconfig/alerts/parameterpage/remoteFilterType/default with a value of "obfuscate"

Pega-Engine prconfig/alerts/parameterpage/obfuscateKeywords/default with a value of the property name(s) separated by semicolon. ex. AccountNumber;SSN;

To suppress sensitive property values, add the following setting to prconfig.xml:

<env name="alerts/database/operationTimeThreshold/suppressInserts" value="true" /> This setting will suppress the sensitive property values (and replace them with question marks). To suppress information in parameters, please add the following setting to prconfig.xml:

<env name="alerts/general/includeparameterpage" value="false" /> This setting determines whether the parameter page of the topmost stackframe will be included in the ALERT log when the alert is generated. We will recommend you to upgrade to recent versions of Pega as they offer more granular approach to obsfuscate sensitive information.

From Pega 8.1 the white list using allowed keywords of the parameter page will be the default for both the file system and PDC/AES.

This will resolve the security issue of data in the filesystem for alerts. There are also hotfixes available to make white list the only option for the filesystem.