Broader coverage
M365 SharePoint and OneDrive, personal OneDrive, Google Drive, Box, Dropbox, S3, network shares, and computers via the Sherpa agent.
Most tools pitching CUI discovery for CMMC are general data-security platforms that added CUI to their marketing. DetectCUI is purpose-built for it, from discovery and human review to standards-based sampling and assessor-ready scoping evidence.
Finding CUI is step one. DetectCUI carries it through review, sampling, evidence, remediation and investigation, in one system that can serve many clients.
M365 SharePoint and OneDrive, personal OneDrive, Google Drive, Box, Dropbox, S3, network shares, and computers via the Sherpa agent.
Scans Gmail, Google Workspace and Microsoft 365 mailboxes, where CUI often travels first.
Confirm or dismiss findings. One decision covers identical copies, and review history can't be altered.
MIL-STD-105E / ANSI/ASQ Z1.4 acceptance sampling of both flagged files (false positives) and clean files (missed CUI), reproducible from a recorded seed.
CUI boundary, spillage exceptions and asset categories in a report mapped to NIST SP 800-171 Rev. 2 / CMMC L2, exported as PDF, CSV and JSON with a logged SHA-256.
Quarantine or move files on computers, with hash verification and two-person approval.
Cases, rules-based routing to real analysts, chain of custody and tamper-evident evidence.
Run many client organisations (tenants) in one system.
Teramis is the closest purpose-built competitor. Compared with what Teramis publishes, DetectCUI covers more of the workflow after a file is found.
| Capability | DetectCUI | Teramis (as published) |
|---|---|---|
| Where it finds CUI | M365 SharePoint/OneDrive, personal OneDrive, Google Drive, Box, Dropbox, S3, network shares, and computers via the Sherpa agent | M365, file shares, endpoints |
| Email scanning | Gmail, Google Workspace and M365 mailboxes | Exchange listed as a repository |
| Human review | Confirm / dismiss findings; one decision covers identical copies; history can't be altered | Not described |
| Acceptance sampling | MIL-STD-105E / ANSI/ASQ Z1.4 single sampling with Table I code letters and normal/tightened plans. Switching rules apply automatically. Lots are frozen and samples reproducible from a recorded seed. Rejected lots need a recorded disposition. Covers flagged and clean files. | Cites "DoD-aligned statistical sampling", Z1.9 and 105E |
| Scoping evidence | CUI boundary, exceptions (spillage) list and asset categories, in a report mapped to NIST SP 800-171 Rev. 2 / CMMC L2 (including 3.12.1 sampling results) as PDF, CSV and JSON, with the report's SHA-256 logged | Containment documentation |
| Remediation | Quarantine or move on computers, with hash verification and two-person approval | Not described |
| Investigations | Cases, rules-based routing to real analysts, chain of custody, tamper-evident evidence | Not described |
| Multi-client (MSP) | Many client organisations (tenants) in one system | Not described |
Why Z1.4, not Z1.9? Z1.9 covers sampling by measured values. A file's CUI classification is yes/no, so Z1.4 / MIL-STD-105E is the applicable standard. DetectCUI's report states this, and each lot's record lets an assessor reproduce the sample.
Other options find or label sensitive data. None of them makes assessor-ready CUI scoping evidence its core output.
| Alternative | What it offers | What DetectCUI adds |
|---|---|---|
| Spirion CUI Discovery Package (archTIS) | Prebuilt CUI content (category names, banner markings, abbreviations) for Spirion's data platform. Finds CUI only; doesn't remediate or claim CMMC compliance. | Human review, controlled remediation, investigations and a scoping report mapped to NIST SP 800-171 / CMMC L2 |
| Broad data-security platforms: Varonis, Concentric AI, Fortra, Netwrix | General classification, labelling, access analysis and data loss prevention, with CUI added to their CMMC messaging | A product focused on CUI, with assessor-ready scoping evidence and standards-based sampling as the core output |
| Microsoft Purview | Labels data and blocks it from leaving. Per Daymark, content-based auto-labelling, trainable classifiers and endpoint DLP need E5; E3 auto-labelling only matches fixed patterns. | Scoping evidence, which Purview doesn't produce, plus coverage beyond Microsoft 365 |
Walk through the interactive demo, or talk with us about a pilot.
Competitor details come from vendor websites and press releases as of October 2026 and are not independently verified. "Not described" means the capability was not found in the vendor's published materials. Sources: Teramis; archTIS / Spirion CUI Discovery Package; Varonis; Concentric AI; Fortra; Netwrix; Daymark. All product names are trademarks of their respective owners. DetectCUI is a support tool, not a certification authority.