Test the identity behind a Databricks answer

A login is not proof of source impersonation

The person signed into an application and the principal opening a warehouse session can be different. Document that identity mapping before making a permission claim. If several users share one source credential, source policies see that credential unless an explicitly supported identity mechanism changes the execution context.

Unity Catalog row filters and column masks can restrict data based on policy and principal. Their existence does not prove that an application's service credential has the same visibility as each business user. Ask the source owner which policies apply to the exact objects and execution path being tested.

A two-persona synthetic exercise

Create approved test data for an East region and a West region. Give one test identity access to East only and another to both. Ask the same total and a regional breakdown through each identity. Agree the expected results before the run so that a confident explanation cannot substitute for the access test.

Repeat the restricted request after a privileged request has populated application caches. A cache hit must not widen visibility. Test the answer, downloadable output and saved-result path where the deployment supports them; those are separate places a prior result might be reused.

• Identity evidenceRecord the source principal and application role without collecting credentials.
• Expected behaviorRestricted rows stay absent; permitted aggregates match the approved reference.
• RevocationRemove access and verify the documented refresh or revocation behavior.

Make masking cases explicit

Choose a column that an authorized owner has masked for the restricted persona. Ask for the raw value and for a breakdown using that field. Inspect whether the system exposes protected values indirectly through explanations or evidence. Use artificial values so an unsuccessful test cannot disclose personal information.

Changes to compute mode, policies or object types can change the supported path. Record the configuration with the evidence and repeat the affected checks after material changes rather than relying on an old screenshot.

Scope the Nexatron conversation

Bring the intended source identity and two role definitions to a Nexatron walkthrough. Confirm how the configured Databricks connection and application controls combine. A successful administrator query establishes connectivity; the lower-privilege test establishes whether the proposed rollout is appropriate.