S3 / object storage PUT DLP test
Upload from the browser
Accepted files (shared list)
A common action — upload a file to S3-compatible object storage with a PUT request. DLP should see that channel and, with the right policies, respond. Upload a test file to our server and compare what you see under Accepted files with what your DLP reports. The file stays on this page for 15 minutes and is visible to all visitors.
Use the browser upload or the curl examples. Pick a file from the sample library or upload one from disk.
curl
curl -X PUT --upload-file ./hello-dlp.txt https://s3.dlpbench.com/dlpbench-public/hello-dlp.txt # Plain text with no identifiers: the request should arrive. If it fails, check the network or an overly strict policy.
curl -X PUT --upload-file ./us-name-ssn-passport-30.csv https://s3.dlpbench.com/dlpbench-public/us-name-ssn-passport-30.csv # Test SSN and card: with DLP configured the request should not leave. If you get ok — the channel was not stopped.
FAQ
Where are PUT requests used in real life?
Cloud services, file-exchange APIs, and similar paths. For example, Dropbox-style uploads often speak S3 — DLP should catch those requests.
What is the size limit?
Up to 20 MB per PUT.
How do I know the channel is not blocked or the block policy failed?
The object appears in the list on this page — the upload succeeded. If the PUT dies or the object is missing, check the DLP log and the network path.
Where do I get a file for the check?
Use the panel on the right, the sample library, or Sample data.
How do I test cloud services?
Separate three mechanisms — otherwise the test answers the wrong question.
Traffic through a gateway (CASB / SSE / proxy): station in path → upload in the service web UI. Nearby range channels: HTTPS POST and this page (S3 PUT).
In-cloud API / storage scan: the file or record is already inside the service → wait for the scanner cycle.
Agent or browser extension: paste/submit on the station; for paste use the clipboard test.
Corporate and personal accounts of the same service often sit under different rules — if both are in scope, run two tests.
Check other exfil channels
Try sending a file by email or generate another sample set.