Print DLP for CUI
Block CUI printing with rules that read the page
To stop CUI from being printed, you need a control that reads what's on the page, not just the file name or the printer. Preton Print Security checks the rendered content of every print job on the Windows endpoint, including OCR of scanned and image-based pages. When a CUI rule matches, it can block the job, or let it print while it records the job and alerts your security officer.
Try it on your CUI rulesWhy print-queue and metadata rules miss CUI
Most print management tools make decisions from metadata such as user, printer, page count or color. A document's name doesn't tell you it contains CUI. Its content does.
That's why content inspection matters at the moment of print:
- Output that was never a file. Pages printed from a browser, an ERP screen or a program portal never pass through file-based DLP.
- Scanned drawings and images. A scanned technical drawing has no text layer. Preton Print Security runs OCR on the endpoint, so rules can act on text inside images.
- Printers outside your print server. Inspection happens on the endpoint, so USB and home printers are covered as well as the office fleet.
What a CUI print rule looks like
A rule has a match condition, a severity and one or more actions. Match conditions are keywords or regular expressions run against the page text and the OCR text.
Typical starting rules for a defense contractor:
| What to catch | Example pattern | Typical action |
|---|---|---|
| CUI banner markings | \bCUI(//[A-Z-]+)*\b, CONTROLLED | Record and alert |
| Export-controlled data | ITAR, EXPORT CONTROLLED, CUI//SP-EXPT | Block |
| DoD distribution statements | DISTRIBUTION STATEMENT [B-F] | Record and alert |
| Program identifiers | Contract numbers, drawing number formats, program names | Record and alert |
Rules on banner text catch documents that were marked correctly. Unmarked CUI needs pattern rules for your own identifiers, which is why the archive's ability to re-search past jobs matters (see the audit trail).
You write and own the rules. The product includes rule documentation and a built-in tester for regular expressions. During a trial we help you write the first set.
Actions on a match
Block
The job doesn't print. Use it where policy says CUI never goes to paper, or never for a given category.
Record and alert
The job prints, its text and page image are archived, and your security officer gets an email.
Mark
A watermark and per-page user annotation trace the paper back to its source. More on marking.
Block, or record and alert?
Block where printing the content is never allowed. Record and alert where printing is sometimes legitimate and you need a trail.
Blocking everything that mentions CUI stops work. Engineers print drawings, and contracts staff print deliverables. Most contractors start with record-and-alert on broad CUI rules, then add block rules for the narrow cases policy forbids outright, such as export-controlled data.
A blocked job isn't held for later approval. If a user needs to print it, they reprint once authorized.
Questions about blocking CUI printing
Can Preton Print Security block printing based on content, not just user or printer?
Yes. Rules match keywords and regular expressions against the rendered page text and OCR text of each print job. A matching rule can block the job.
Does it detect CUI in scanned documents or images?
Yes. OCR runs locally on the endpoint for image-based pages, so rules apply to text inside scans and images. There's no per-image fee.
Can a manager release a blocked print job?
Not today. A blocked job is stopped, not held. If you need hold-and-release approval, tell us. It's a feature request we're tracking.
Does it replace our enterprise DLP?
No. It covers the print channel only and works alongside DLP that covers email, USB and cloud.
See your own rules block a test print
Thirty-day trial in your environment, fully air-gapped.
Request a trial