pii-audit

To check if a SQL query exposes PII, use the query PII inspection function with your SQL string and schema context object. It returns the specific PII columns accessed, the associated risk level, and whether sensitive data is exposed in the query output.

To classify PII across a warehouse, first index the warehouse, then inspect specific databases, schemas, and tables, and finally run PII detection. This process identifies sensitive columns and generates a risk assessment report with recommended mitigations.

Yes, you can detect PII without writing SQL by indexing your warehouse and inspecting the target database, schema, and table structures. The system analyzes the schema context directly to identify and classify sensitive PII columns automatically.

The best way to generate a PII risk assessment report for dbt projects is to run a batch audit using glob patterns on your SQL models. This evaluates every model for PII access and outputs a final report listing HIGH and MEDIUM risk columns with mitigation recommendations.

PII schema auditing works directly with existing warehouse metadata. You simply index your warehouse by name and inspect the desired databases and schemas, eliminating the need to manually define schema objects for PII classification and risk assessment.