Data leaks

Detected sensitive-data class analytics.

This screen belongs to the Secure deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.

Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.

Step-by-step actions

Open Data leaks and select the period.
Locate class and tenant, compare severity and trend.
Review matching audit records for the actual action.
Use Custom DLP for an organizational detector and Policies for handling.

Every control and its meaning

Control / parameter	Values, units and effect
Период / Period	Selects detected-class analytics, not regex configuration or retention.
Классы, severity, tenant	Shows sensitive-data matches. Multiple classes may occur in one request; their sum is not unique request count.
Decision / policy link	Class detection differs from mask/block action; edit the action under Policies.

Verify the result

A positive synthetic sample should detect the intended class ID; a clean negative sample should not. Verify the final outcome through a protected call.

Errors, disabling and reverting changes

For an empty report, expand the window and inspect source. Disabling one custom pattern does not disable built-in detectors.

**Data leaks report · actual staging**
2026-10-15 · Actual staging application; settings read without changing global protection. Aggregates describe a test stand, not real customers or a benchmark. Unretouched original pixels.

Detailed security settings · Traffic analysis · FAQ · All application sections