# LLM06: Sensitive Information Disclosure ### Sensitive Information Disclosure LLM applications have the potential to reveal sensitive information, proprietary algorithms, or other confidential details through their output. This can result in unauthorized access to sensitive data, intellectual property, privacy violations, and other security breaches. It is important for consumers of LLM applications to be aware of how to safely interact with LLMs and identify the risks associated with unintentionally inputting sensitive data that it may be returned by the LLM in output elsewhere. To mitigate this risk, LLM applications should perform adequate data sanitization to prevent user data from entering the training model data. LLM application owners should also have appropriate Terms of Use policies available to make consumers aware of how their data is processed and the ability to opt-out of having their data included in the training model. The consumer-LLM application interaction forms a two-way trust boundary, where we cannot inherently trust the client->LLM input or the LLM->client output. It is important to note that this vulnerability assumes that certain pre-requisites are out of scope, such as threat modeling exercises, securing infrastructure, and adequate sandboxing. Adding restrictions within the system prompt around the types of data the LLM should return can provide some mitigation against sensitive information disclosure, but the unpredictable nature of LLMs means such restrictions may not always be honoured and could be circumvented via prompt injection or other vectors. #### Common Examples of Vulnerability 1. Incomplete or improper filtering of sensitive information in the LLM’s responses. 2. Overfitting or memorization of sensitive data in the LLM’s training process. 3. Unintended disclosure of confidential information due to LLM misinterpretation, lack of data scrubbing methods, or errors. #### How to Prevent 1. Integrate adequate data sanitization and scrubbing techniques to prevent user data from entering the training model data. 2. Implement robust input validation and sanitization methods to identify and filter out potential malicious inputs to prevent the model from being poisoned. 3. When enriching the model with data and if fine-tuning a model: (I.E, data fed into the model before or during deployment) * Anything that is deemed sensitive in the fine-tuning data has the potential to be revealed to a user. Therefore, apply the rule of least privilege and do not train the model on information that the highest-privileged user can access which may be displayed to a lower-privileged user. * Access to external data sources (orchestration of data at runtime) should be limited. * Apply strict access control methods to external data sources and a rigorous approach to maintaining a secure supply chain. #### Example Attack Scenarios * Unsuspecting legitimate user A is exposed to certain other user data via the LLM when interacting with the LLM application in a non-malicious manner. * User A targets well-crafted prompts to bypass input filters and sanitization from the LLM to reveal sensitive information (PII) about other users of the application. * Personal data such as PII is leaked into the model via training data due to negligence from the user or the LLM application. This case could increase risk and probability of scenario 1 or 2 above. #### Reference Links * [AI data leak crisis: New tool prevents company secrets from being fed to ChatGPT](https://www.foxbusiness.com/politics/ai-data-leak-crisis-prevent-company-secrets-chatgpt) * [Lessons learned from ChatGPT’s Samsung leak](https://cybernews.com/security/chatgpt-samsung-leak-explained-lessons/) * [Cohere - Terms Of Use](https://cohere.com/terms-of-use) * [AI Village- Threat Modeling Example](https://aivillage.org/large%20language%20models/threat-modeling-llm/) * [OWASP AI Security and Privacy Guide](https://owasp.org/www-project-ai-security-and-privacy-guide/) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://wiki.hackerium.io/owasp/owasp-llm-top-10-v1.0/llm06-sensitive-information-disclosure.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.