Limitations in PII Identification and Masking

This page outlines the current limitations of Luma VA regarding the identification and masking of Personally Identifiable Information (PII) and Protected Health Information (PHI).

1. Nested Objects in JSON Arrays/Lists

   1. Luma VA does not fully support the identification and masking of PII within nested objects contained in JSON arrays or lists. PII data within nested structures may not be detected or masked, potentially exposing sensitive information.

2. Free Text in JSON Values

   1. Luma currently does not mask PII when it is embedded within free text fields in JSON values.

3. URLs with Path Parameters in Conversation History Logs

   1. PII masking is not applied to URLs containing path parameters in conversation history logs for integration calls.

4. Complete Address Masking

   1. During PII processing, the complete address is not fully masked. Partial masking of addresses may leave some sensitive information exposed.

5. Date of Birth (DOB) Identification

   1. Date of Birth is not currently included in the list of PII identifiers. DOB fields may not be detected or masked, potentially exposing sensitive personal information.

6. Knowledge and Catalog Search Responses

   1. PII information is currently not identified and masked in responses generated as part of Knowledge Search, and Catalog Search. PII data in search results or knowledge management systems may remain unmasked.

7. PHI Data Extraction

   1. The current implementation does not specifically address the extraction of Protected Health Information (PHI). So, PHI data may not be identified or masked.