You can enable inSync end users to view and take action on violations reported for the data stored in their system. This is helpful when the Data Compliance team is small, and a huge number of violations are reported because of the nature of data stored in the data sources.

For example, financial organizations may use test or mock data that contains sample account numbers, card numbers, or other values that resemble sensitive information. inSync may report violations for this data. End users who understand the business context can review and resolve such violations without administrator intervention, allowing administrators to focus on critical or unresolved violations.

Even when end-user violation visibility is enabled, administrators retain control over the compliance workflow. Administrators can determine which violations are visible to users, which resolution actions are available, how frequently notifications are sent, and how violations are handled when users do not take action.

End-user violation visibility is supported for violations detected in backed-up data from the following workloads:

📝Note: The available actions may differ depending on whether the violation is associated with a file or an email.

As an administrator, you can configure the entire workflow of how a violation moves through various phases, right from detection to resolution. You have complete control over the entire process flow which ensures that there are no gaps or critical misses.

You can enable end-user violation visibility for individual Compliance Policies. When inSync detects a violation for a policy where this setting is enabled, the violation moves through the following stages.

inSync scans the backed-up data for sensitive information based on the rules defined in the applicable Compliance Policy.

When matching sensitive information is found, inSync creates a violation and associates it with the user who owns the affected data.

The user receives an email containing a summary of the reported violations and instructions to review them.

The violation appears on the Active tab of the Sensitive Data Governance Dashboard, on the File Violations page. Its status is displayed as Pending on User.

The user signs in to the inSync Web panel and opens the compliance violations page to review the affected data, violation details, and the actions available to them.

Depending on the policy configuration and the type of violation, the user can select one of the available resolution actions: Resolve, Acceptable Risk, False Positive, or Delete.

After the user submits an action, the violation status is updated. Depending on the selected action and the workflow configuration, the violation remains on the Active tab or moves to the Resolved tab.

If the user does not take action within the configured period, inSync applies the default resolution behavior defined in the Compliance settings.

Actions performed by end users are reflected in the Sensitive Data Governance Dashboard and can be reviewed by administrators through the violation details, history, and available compliance reports.

You can enable inSync client users to see violations per policy. The following workflow diagram shows how a file violation moves through different stages when End user violation visibility is enabled .

📝 Note

The following is the sequence of events that are triggered when inSync finds a violation for a policy that has end user violation visibility criteria enabled:

All the activities of the administrator and the end user are logged in Admin Audit Trail and User Audit trail respectively. The details are also available in the Non-Compliant File report and Non-Compliant Email report.

The user selects Resolve when corrective action has already been taken or when the affected data no longer requires further remediation. The violation is marked as resolved based on the configured workflow.

The user selects Acceptable Risk when the violation is valid but the data is required for an approved business purpose. This action records that the risk has been reviewed and accepted.

The user selects False Positive when the detected content is not actually sensitive or is incorrectly classified. For file violations, inSync whitelists the file hash, automatically resolves matching violations for that file, and excludes the same file from future compliance scans.

Important: False Positive is available only for file violations. It is not available for email violations because email content cannot be uniquely identified using a file hash.

Depending on the policy configuration, users may see one or both of the following options:

Only the non-compliant versions are targeted for deletion. Older compliant versions may remain available for restore, where applicable.

Important: Data associated with users who are on Legal Hold is not deleted.

When you enable end-user violation visibility for a Compliance Policy, default settings are applied. Review and update the settings based on your organization's compliance requirements.

Specify how frequently users receive violation summary emails. Learn more.

Define which violations are visible to end users. Use this setting to ensure that users see only the violations they are expected to review. Learn more

Select the resolution actions that users are allowed to perform. The available options may include Resolve, Acceptable Risk, False Positive, and Delete. Learn more

Enable this setting when users should be allowed to view files that have been quarantined because of a compliance violation.

Configure the period for which a violation can remain pending on the user and specify the default action to apply when the user does not respond.

Administrators can monitor end-user activity from the Sensitive Data Governance Dashboard. Review the violation status, selected resolution action, user comments where available, and the violation history to verify that the required remediation was completed.

When you enable End-user violation visibility for a policy, the default configured settings are auto-applied. If you want, you can configure these settings before you enable end users to view violations. The following settings are available: