Find
Discover CUI across approved Microsoft 365 environments, file systems, email, endpoints, CAD files, PDFs, scanned documents, archives, engineering repositories, and other supported sources.
ACCURATE CUI DISCOVERY
Controlled Unclassified Information can exist far beyond the systems and folders where teams expect to find it.
Teramis examines supported data sources to identify where CUI, ITAR, and other covered defense information exists, surface unexpected locations, and provide a stronger technical foundation for scoping, boundary, and remediation decisions.
Purpose-built CUI discovery with scanning and analysis performed within the customer environment.
Why CUI Discovery Comes First
Asset inventories, architecture diagrams, policies, and employee interviews can describe where CUI is supposed to be. They do not necessarily show where it actually exists.
Files get copied, forwarded, downloaded, archived, renamed, scanned, and stored in unexpected places. When those locations are missed, the documented boundary can drift from the actual data environment.
Over-Scoped
Systems that do not need to be included may add unnecessary licensing, security, assessment, and support requirements.
Under-Scoped
CUI may remain outside the documented boundary, creating gaps that require investigation and correction.
Evidence before assumptions.
WHERE IS THE CUI?
Controlled Unclassified Information does not always live in the folder someone designated for it. It can appear in technical documents, engineering files, PDFs, email attachments, images, scans, compressed archives, project folders, and repositories that have grown over years.
Teramis is built for the messy reality of defense data. It helps organizations examine approved environments and supported file types so CUI discovery is not limited to obvious labels, expected folders, or simple keyword searches.
Find the data first. Then draw the boundary.
Trusted by leading companies
HOW CUI DISCOVERY WORKS
Teramis examines the systems, repositories, and data sources approved for review to identify candidate CUI and establish a clearer, evidence-backed picture of the data environment.
Teams can use those findings to investigate the CUI footprint before scoping, boundary validation, migration planning, or assessment preparation.
Discover CUI across approved Microsoft 365 environments, file systems, email, endpoints, CAD files, PDFs, scanned documents, archives, engineering repositories, and other supported sources.
Validate findings and produce evidence that helps executives, advisors, compliance teams, and government or prime-contractor reviewers understand whether the documented boundary matches the actual environment.
Run recurring scans to identify new CUI, movement, spillage, and boundary drift before the next assessment, annual affirmation, prime contractor request, or internal review.
From Discovery to Reviewable Findings
Move from an approved discovery scope to organized, reviewable findings that help teams understand where potential CUI exists and what requires further validation.
01
Select the systems, repositories, projects, and data sources approved for examination.
02
Teramis scans supported content within the approved scope for potential CUI.
03
Findings provide file and location information so teams can understand where CUI may exist and where exceptions require attention.
04
Discovery findings can move into the Teramis validation process to build greater confidence in the resulting CUI inventory.
Teramis discovery can provide:
Teramis reports what it finds. Authorized teams approve the response, and Remedius can carry it out with a documented record.
BEYOND KEYWORD SEARCH
Controlled Unclassified Information does not always live in the folder someone designated for it. It can appear in technical documents, engineering files, PDFs, email attachments, images, scans, compressed archives, project folders, and repositories that have grown over years.
Teramis is built for the messy reality of defense data. It helps organizations examine approved environments and supported file types so CUI discovery is not limited to obvious labels, expected folders, or simple keyword searches.
SharePoint
OneDrive
Exchange
Supported Microsoft 365 repositories
Network file shares
Local and distributed endpoints
Legacy repositories
Project and engineering folders
CAD and engineering files
PDFs
Images and scanned documents
Email and attachments
Archives
Structured and unstructured files
BETTER TOGETHER WITH YOUR EXISTING STACK
Teramis is not another platform war. It complements the systems, tools, advisors, and workflows organizations already use by helping identify where CUI actually exists.
Use labels and compliance workflows with stronger CUI discovery evidence.
Support access governance with clearer visibility into where CUI exists.
Strengthen enforcement strategies by starting with better CUI ground truth.
Connect documentation, control evidence, and boundary decisions to the actual CUI footprint.
Identify where CUI actually exists before defining the systems, users, repositories, and controls that belong inside the boundary that must meet NIST SP 800-171.
Compare the documented boundary with the actual data environment and identify exceptions that require review or customer action.
Identify and report the files, locations, and findings administrators need when planning customer-led movement into approved environments.
Run recurring scans to identify CUI that appears outside approved locations as people, files, systems, and business processes change.
Examine affected systems and repositories to help determine whether CUI may have existed within the impacted environment.
Evaluate whether the actual CUI footprint supports representations made during vendor reviews, acquisitions, integrations, and supply-chain due diligence.
Common sensitive-data searches often focus on predictable identifiers such as payment card or Social Security number patterns.
CUI is different. It may be inconsistently marked, embedded in technical content, stored in images or scans, mixed with ordinary project information, or located in repositories no one expected to contain controlled data.
Teramis is purpose-built to help organizations find CUI across the complex data environments common to the Defense Industrial Base.
Partner With Teramis
Teramis gives compliance advisors, MSPs, MSSPs, vCISOs, GRC providers, enclave partners, and other organizations serving the Defense Industrial Base the technical evidence needed to guide clients with greater confidence.
Use Teramis to reduce scoping uncertainty, identify late-stage CUI surprises, strengthen client recommendations, and create repeatable CUI discovery and monitoring services.
About Teramis
Teramis is a purpose-built forensic discovery, validation, remediation, and continuous monitoring platform for CUI, ITAR, and other covered defense information. The platform helps organizations understand where that data actually lives so they can make stronger decisions about scope, boundary validation, remediation, spillage monitoring, and self-assessment.
Make the Documented Boundary Match Reality
See how Teramis can help your organization or your clients identify CUI, validate the CMMC boundary, and monitor what changes over time.