> For the complete documentation index, see [llms.txt](https://waf-doc.inext.checkpoint.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waf-doc.inext.checkpoint.com/additional-security-engines/genai-security/data-leakage-prevention.md). # Data Leakage Prevention Data Leakage Prevention Protects against sensitive data exposure by detecting and blocking patterns, based on the pre determined confidence level.

The following types of sensitive can be discovered and blocked:

PII Type	Example LLM Response
Credit Card	"Based on your account, your payment method on file is 4111-1111-1111-1111, expiring 03/27."
Email	"The account owner's contact email is john.doe@acme-corp.com."
SSN	"According to your records, your Social Security Number is 123-45-6789."
Phone	"Your account manager can be reached at +1 (555) 123-4567."
IBAN	"The wire transfer was sent to IBAN DE89 3704 0044 0532 0130 00."
Name + Address	"This account belongs to John Doe, 742 Evergreen Terrace, Springfield IL 62704."
IP Address	"The last login to your account was from 192.168.14.42."

Data checks can be applied to both **incoming requests** (requests to the application) and **outgoing responses** (responses from the application to the calling client). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://waf-doc.inext.checkpoint.com/additional-security-engines/genai-security/data-leakage-prevention.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.