Data classes

Sensitive-data detector registry and regex masking test.

Sensitive-data detector registry and regex masking test.

This screen belongs to the Router 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

  1. Open Data classes and locate the class ID used by policy.
  2. Check external/hybrid/local actions and the enforcement banner.
  3. Open Classification test, enter a synthetic sample and click Test.
  4. Compare detected classes and masked text with a negative sample.
  5. Request operator changes to detector files or enforcement configuration.

Every control and its meaning

Control / parameterValues, units and effect
ID, severity, placeholderClass ID links detection to policy; severity is low/medium/high/critical; placeholder identifies replacement. A class is not the final action.
default_action / action_enforcementPerimeter actions mask/block/allow/local_only execute only in enforce mode. off means metadata; shadow means observation. Check the installation’s banner.
Текст для тестированияSynthetic sample up to 64 KB. Tests the registry, not a full LLM call; the operator updates it through IAM_GW_DATA_CLASSES.

Verify the result

Send a separate request using the intended policy_mode and verify action/perimeter in history. A regex match alone does not prove full screening.

Errors, disabling and reverting changes

For an empty registry, ask the operator to check the path and file loading. Preserve the previous file for rollback and repeat positive/negative tests.

Class registry: per-perimeter actions · actual staging
Class registry: per-perimeter actions · actual staging
2026-10-15 · Actual staging application. Synthetic client, public definitions or aggregate test-stand metrics only; not customer statistics or a benchmark. Original pixels are unmodified; personal profile and private data excluded.
  1. Refresh
  2. External / hybrid / local actions
  3. Placeholder
Actual regex test: pii.contact → [CONTACT]
Actual regex test: pii.contact → [CONTACT]
2026-10-15 · Actual staging application. Synthetic client, public definitions or aggregate test-stand metrics only; not customer statistics or a benchmark. Original pixels are unmodified; personal profile and private data excluded. screenshot@example.invalid was tested. This is a registry regex check, not a model-transport test.
  1. Sample text
  2. Test
  3. Masked text

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