{"id":"GRD-006","section":"Runtime Guardrails","requirement":"Detect sensitive health and workforce information","acceptance":"Recognize sensitive patient, clinical-research and employee information in context, including when users summarize or rewrite it. Document supported prompts and file types.","tier":"AT0–AT4","whyItMatters":"Sensitive records can appear in everyday prose, not just structured forms or obvious identifiers.","verificationMethod":"LT","verificationTest":"Test synthetic health and workforce examples in prompts and supported files, including summarization requests. Compare results with nonsensitive reference text.","formerly":"DAT-010","alsoIn":[],"sort":16,"adoptionContext":"Employee records can flow through shadow use, assistants, integrated platforms and citizen workflows, making those the primary workforce-data test contexts.","mappings":[{"frameworks":["csf"],"explanation":"Recognizing named employee medical, accommodation, compensation and performance details supplies a detection input for in-transit protection. Detection alone does not restrict disclosure.","kind":"framework","references":{"csf":["PR.DS-02"]},"relation":null,"conditions":[]},{"frameworks":["rmf"],"explanation":"Findings about named employees make privacy exposure and potential impacts on individuals or groups visible for assessment. Recognizing sensitive workforce prose does not itself examine or document the full consequences.","kind":"framework","references":{"rmf":["MEASURE 2.10"]},"relation":null,"conditions":[]},{"frameworks":["soc2"],"explanation":"Workforce-record recognition informs release restrictions and identification of records designated confidential. Permitted use, access and retention remain organizational decisions; this does not establish a privacy program. C1.1 applies only when the Confidentiality category and relevant information are in scope.","kind":"framework","references":{"soc2":["CC6.7","C1.1"]},"relation":null,"conditions":[]},{"frameworks":["iso27001"],"explanation":"Detection of named employee records feeds leakage-control decisions and privacy safeguards. A.8.12 needs an operated leakage-protection workflow with defined alert triage, warnings, blocking or another protective response. Monitoring these records itself needs approved privacy handling; detection does not determine employment-law or privacy compliance.","kind":"framework","references":{"iso27001":["A.8.12","A.5.34"]},"relation":null,"conditions":[]}],"area":"Runtime Guardrails","areaSlug":"GRD","url":"/r/GRD-006","frameworkRefs":{"ISO27001":["A.8.12","A.5.34"],"NIST-CSF":["PR.DS-02"],"NIST-AI-RMF":["MEASURE 2.10"],"SOC2":["CC6.7","C1.1"]}}