Guardrail Policies
SL-09Constraints applied to every AI interaction, driven by what Discovery classified the data as rather than by generic keyword rules. That is what allows a guardrail to permit a legitimate case-drafting prompt while blocking a district-wide contact extraction.
Deny after withdrawal
Configured guardrails
Inspects prompts for attempts to retrieve data classified as personal or high-risk, and for mass-extraction or enumeration patterns.
Checks performed
- Inspects promptsReads the request before any retrieval happens.
- Inspects outputsAnalyses the response for personal data before display.
- Validates consentBlocks retrieval where consent has been withdrawn or has expired.
- Validates purposeChecks the requested data is within the purpose it was collected for.
- Blocks children's dataPrevents any retrieval of data classified as a child's personal data.
- Detects mass extractionRecognises enumeration and bulk-retrieval patterns in the prompt itself.
Analyses every response for personal or sensitive content and masks identifier categories before display.
Checks performed
- Inspects promptsReads the request before any retrieval happens.
- Inspects outputsAnalyses the response for personal data before display.
- Validates consentBlocks retrieval where consent has been withdrawn or has expired.
- Validates purposeChecks the requested data is within the purpose it was collected for.
- Blocks children's dataPrevents any retrieval of data classified as a child's personal data.
- Detects mass extractionRecognises enumeration and bulk-retrieval patterns in the prompt itself.
Validates that the data a prompt would retrieve is within the declared purpose and that consent is active. Blocks where consent is withdrawn or expired.
Checks performed
- Inspects promptsReads the request before any retrieval happens.
- Inspects outputsAnalyses the response for personal data before display.
- Validates consentBlocks retrieval where consent has been withdrawn or has expired.
- Validates purposeChecks the requested data is within the purpose it was collected for.
- Blocks children's dataPrevents any retrieval of data classified as a child's personal data.
- Detects mass extractionRecognises enumeration and bulk-retrieval patterns in the prompt itself.
Any personal data destined for an AI service outside the sanctioned catalogue is blocked at the gateway and logged.
Checks performed
- Inspects promptsReads the request before any retrieval happens.
- Inspects outputsAnalyses the response for personal data before display.
- Validates consentBlocks retrieval where consent has been withdrawn or has expired.
- Validates purposeChecks the requested data is within the purpose it was collected for.
- Blocks children's dataPrevents any retrieval of data classified as a child's personal data.
- Detects mass extractionRecognises enumeration and bulk-retrieval patterns in the prompt itself.
Permits code context but blocks any prompt containing content classified as personal data.
Checks performed
- Inspects promptsReads the request before any retrieval happens.
- Inspects outputsAnalyses the response for personal data before display.
- Validates consentBlocks retrieval where consent has been withdrawn or has expired.
- Validates purposeChecks the requested data is within the purpose it was collected for.
- Blocks children's dataPrevents any retrieval of data classified as a child's personal data.
- Detects mass extractionRecognises enumeration and bulk-retrieval patterns in the prompt itself.
The dependency worth understanding
None of these guardrails work without Discovery. “Block children's data” is only meaningful if something has already classified which columns and files contain it; “deny after withdrawal” is only meaningful if consent state is bound to data elements. An AI guard deployed without a classification layer underneath it degrades to keyword filtering, which fails in both directions.