Add instructions to disable default log masking

Author: ashviniwe

en/identity-server/6.1.0/docs/deploy/monitor/mask-sensitive-information-in-logs.md

@@ -1,6 +1,6 @@
 # Mask Sensitive Information in Logs
 
-There can be business sensitive information that are added to logs in 
+There can be business sensitive information that are added to logs in
 the product console and/or Carbon log files. When these logs
 are analyzed, the information is exposed to those who check this.
 
@@ -11,8 +11,8 @@ information.
 
 ## Mask Sensitive Information in Logs with Log4j
 
-Users can mask sensitive information from the log file at the time of logging. 
-In this feature, you can define patterns that need to be masked from the logs. 
+Users can mask sensitive information from the log file at the time of logging.
+In this feature, you can define patterns that need to be masked from the logs.
 This is particularly useful in the cases of credit card numbers, access tokens,
 etc.
 
@@ -25,6 +25,15 @@ see, [Configure log masking with Log4j]({{base_path}}/deploy/monitor/log4j-mask-
 Users can mask sensitive information from the logs at the time of shipping with Filebeat.
 In this feature, you can define patterns that need to be masked from the logs and it
 will be masked at the Filebeat level and shipped. However, the log file itself
-will contain the sensitive information. 
+will contain the sensitive information.
 
 see, [Configure log masking with Filebeat]({{base_path}}/deploy/monitor/elk-mask-sensitive-information-in-logs)
+
+## Disabling Default Log Masking
+
+By default, log masking is enabled. To disable log masking, navigate to `<IS-HOME>/repository/conf/deployment.toml` and add the following configuration.
+
+```toml
+[masking_logs]
+enabled = false
+```

en/identity-server/7.0.0/docs/deploy/monitor/mask-sensitive-information-in-logs.md

@@ -16,3 +16,12 @@ Users can mask sensitive information from the logs at the time of shipping with
 In this feature, you can define patterns that need to be masked from the logs and it will be masked at the Filebeat level and shipped. However, the log file itself will contain sensitive information.
 
 For more information, refer to [Configure log masking with Filebeat]({{base_path}}/deploy/monitor/elk-mask-sensitive-information-in-logs)
+
+## Disabling Default Log Masking
+
+By default, log masking is enabled. To disable log masking, navigate to `<IS-HOME>/repository/conf/deployment.toml` and add the following configuration.
+
+```toml
+[masking_logs]
+enabled = false
+```

en/identity-server/7.1.0/docs/deploy/monitor/mask-sensitive-information-in-logs.md

@@ -16,3 +16,12 @@ Users can mask sensitive information from the logs at the time of shipping with
 In this feature, you can define patterns that need to be masked from the logs and it will be masked at the Filebeat level and shipped. However, the log file itself will contain sensitive information.
 
 For more information, refer to [Configure log masking with Filebeat]({{base_path}}/deploy/monitor/elk-mask-sensitive-information-in-logs)
+
+## Disabling Default Log Masking
+
+By default, log masking is enabled. To disable log masking, navigate to `<IS-HOME>/repository/conf/deployment.toml` and add the following configuration.
+
+```toml
+[masking_logs]
+enabled = false
+```

en/identity-server/next/docs/deploy/monitor/mask-sensitive-information-in-logs.md

@@ -16,3 +16,12 @@ Users can mask sensitive information from the logs at the time of shipping with
 In this feature, you can define patterns that need to be masked from the logs and it will be masked at the Filebeat level and shipped. However, the log file itself will contain sensitive information.
 
 For more information, refer to [Configure log masking with Filebeat]({{base_path}}/deploy/monitor/elk-mask-sensitive-information-in-logs)
+
+## Disabling Default Log Masking
+
+By default, log masking is enabled. To disable log masking, navigate to `<IS-HOME>/repository/conf/deployment.toml` and add the following configuration.
+
+```toml
+[masking_logs]
+enabled = false
+```