# GRD-005: Detect general, customer, employee and bulk PII


- Area: Runtime Guardrails

- Verification: Live test
- OWASP adoption tier: AT0–AT4
- Formerly: DAT-009
- URL: /r/GRD-005

**Acceptance criteria:** Correctly classify realistic personal, customer, employee and multi-person records inside contextual prompts.

**Why it matters:** Personal data is the most regulated thing employees paste into AI, often as whole records rather than single fields.

**How to verify:** Realistic customer, employee and multi-person records in pilot prompts are detected on default configuration.

**OWASP adoption context:** Personal data can be submitted through any listed employee AI context; the tier does not determine whether the content is sensitive.

**Mappings:**
- NIST CSF 2.0: PR.DS-02 — Contextual recognition of individual and bulk personal records supplies a detection input for protecting data in transit. Classification alone does not prevent release.
- NIST AI RMF: MEASURE 2.10 — Personal-data findings make relevant privacy exposure visible for examination and documentation. Recognizing PII does not complete the AI system’s privacy-risk assessment.
- SOC 2: CC6.7, C1.1 — PII recognition informs transfer controls and, for records designated confidential, confidential-information identification. It does not establish notice, consent or a complete privacy program. C1.1 applies only when the Confidentiality category and relevant information are in scope.
- ISO 27001: A.8.12, A.5.34 — Contextual PII recognition feeds leakage controls and privacy safeguards. A.8.12 needs an operated leakage-protection workflow with approved handling rules and defined alert triage, warnings, blocking or another protective response. Detection does not determine a lawful basis, fulfill privacy rights or establish regulatory compliance.