Privacy protection

Use the Account > Privacy Protection page to prevent end-user identifying information and/or data security incident trigger values from appearing in logs and web reports. If required, you can still collect this information for security threats.

Web Privacy Settings

End user identifying information comprises user names and IP addresses. If you want to prevent this information from appearing only for some of your end users, ensure those users are all registered to a specific policy or policies.

Select Anonymize end user information.

Define whether to anonymize user information in all policies, or only selected policies.


	Note If you select All policies, this applies to all existing policies and any new policies you create in the future.

If you choose Only selected policies, select the policies you want from the Available policies list. Use the Ctrl and/or Shift keys to make multiple selections.

Click the > button to move the policies into the Selected policies list.

To override all privacy protection selections in the event of a security threat, mark Preserve end user information for security threats.

Define the attributes that should be anonymized in web reports.

By default, User name, Connection IP, Source IP, and Workstation are all selected.

When the Connection IP option is selected, the connection name is also anonymized.

You can select and clear the options most appropriate for your organization, but at least one check box must be selected.


	Note If you have selected Preserve end user information for security threats, the attributes that you select are not anonymized for any web traffic considered to be a security risk.

Click Save when done.

Data Security Incident Settings (DLP Lite only)

Select Store and display incident data if you want the values that triggered data security incidents to be captured, stored in the incident database, and displayed in reports. (Credit card numbers, social security numbers, and email addresses are masked when they are stored, as are passwords in certain instances.)

By default, incident data is not captured, stored, or displayed. Administrators with permission to view incident data are able to see the number of matches in the report, but not the match values or context.

Changing this setting has no impact on incident data that has already been collected.