PII DLP — credit card data
Condition: all content matching the predefined detector Global – Credit card number (likelihood Medium), NOT on Internal URLs. Expected block message: “The content that you are uploading/downloading/pasting/printing contains PII information.” Test data follows the dlptest.com Sample Data Library schema: every card number is Luhn-valid per brand BIN range and trips real detectors, but no value corresponds to a real card or person.
Select and copy the block below. It is the source material for the paste, print, upload and download tests.
First 6 rows of the Name + SSN + CCN dataset (30 rows, dlptest.com schema).
Paste the copied specimen into the field below (or into any external page not on the internal list). Bulk text content analysis scans it before entry.
Print this page — it contains the card numbers above, so print content analysis must block the job.
Download content analysis scans these files as they land on disk:
First download a specimen file from an exempt context (or create cc.txt locally by pasting the specimen into Notepad). Then attach it here — upload content analysis scans on submission. Control case: a clean file must upload without interference.
The POV guide's original flow uses dlptest.com directly — still a useful cross-check that the rule fires off this server too: copy a dataset, then paste or upload it at dlptest.com/https-post (or /http-post). The endpoint accepts and discards submissions; your block should trigger before anything is sent.
- Paste, print, download and upload of card data are each blocked with the custom PII message — on this site and on dlptest.com.
- The same actions on Internal URLs domains (e.g. pasting into a Google Doc) are allowed.
- The clean control file passes all four channels.
- If Securely save content and Sensitive content storage are enabled, the triggering snippet is visible in Chrome log events.