Enterprise
Catch personal data leaking through errors.
An error message that echoes a row can expose the very data your access rules protect. The --pii pass looks where nobody writes a test.
- Every error and RAISE path exercised
- Output inspected for personal data
- Findings in their own report, with JSON alongside
- Runs on your side, no telemetry
The PII audit report
- Each finding names the routine, the path, and the personal data it exposed
- Written to
<out>/pii_tests/pii_report.html, its own module in the output
pii_findings.json alongside, for CI- Run it with
--pii next to your security coverage run
Why it is its own check
- Access control asks who can reach a row; this asks what the code says back
- A leak here needs no multi-tenancy. One customer's data in an error is still exposure
- Maps to data-minimisation, distinct from the access controls seccover covers
- The one leak conventional tests never assert on
