DEPLOYMENT AND DATA SOURCES
CUI does not exist in one standard repository or file format.
Teramis supports discovery across approved Microsoft 365 environments, file systems, engineering content, documents, images, scans, archives, and other supported sources so teams can investigate the CUI footprint across the systems that matter.
Define the approved scope. Examine the data. Understand where CUI exists.
Every environment is different. Discovery begins by identifying the systems, repositories, business units, projects, and data sources authorized for review.
That creates a bounded technical scope for the engagement and keeps the discovery effort focused on the information relevant to the organization's CUI questions.
Teramis examines the approved sources included in that scope.
Trusted by leading companies
DATA SOURCES TERAMIS CAN SUPPORT
Teramis provides the CUI ground truth that compliance, security, advisory, and self-assessment decisions depend on.
Supported SharePoint, OneDrive, Exchange, email, attachments, and Microsoft 365 content.
Network file shares, project folders, endpoints, distributed repositories, and legacy storage where supported.
CAD and engineering content, technical drawings, specifications, design files, and project documentation.
Supported SharePoint, OneDrive, Exchange, email, attachments, and Microsoft 365 content.
Network file shares, project folders, endpoints, distributed repositories, and legacy storage where supported.
COMPLEX FILES MATTER
Defense information may be embedded in drawings, scans, images, technical documentation, attachments, archives, and specialized project files.
That matters because discovery limited to obvious folders or simple text patterns may leave important parts of the data environment unexplored.
Teramis is designed to support CUI discovery across the complex content common to defense and engineering workflows.
PLAN DEPLOYMENT AROUND THE ENVIRONMENT
A Teramis deployment should account for:
The exact architecture, connectivity, permissions, data-handling approach, and supported source configuration should be confirmed during technical planning.
This is intentionally more conservative than the previous draft. The V2 approval document specifically flags exact deployment architecture, data residency, integrations, file-type coverage, and similar technical statements for SME confirmation before publication.
Examine approved data sources to identify potential CUI across the systems and repositories in scope.
Review and validate findings to distinguish relevant CUI from false positives and provide evidence for customer-controlled decisions.
Use recurring scans to identify CUI that appears outside approved locations as people, files, systems, and business processes change.
Start With the Environment You Have
See how Teramis can help identify CUI across the repositories, systems, and file types your organization actually uses, validate the CUI boundary, and establish a foundation for ongoing monitoring as the environment changes.
Talk with us about your data sources, deployment requirements, supported file types, and the CUI questions that should shape your discovery scope.
