CUI Scoping
Define the CUI Boundary With Evidence
Identify where CUI exists before deciding which systems, repositories, users, and assets belong inside the assessment boundary.
TERAMIS SOLUTIONS
Start With the CUI Decision You Need to Make
Different organizations face different CUI challenges. Teramis helps you identify where Controlled Unclassified Information exists, validate your documented boundary, and monitor what changes over time.
Use the evidence to make more informed decisions about CUI scoping, boundary validation, migration planning, spillage monitoring, incident review, and supply chain risk.
Review our solutions: By Decision | By Organization
START WITH THE DATA
Every CUI Decision Begins With the Same Question
Where does your CUI actually live?
Policies, interviews, inventories, and diagrams describe an intended environment. Teramis helps you examine supported data sources and compare that intended state with the findings in your actual environment.
That evidence can support decisions about:
- CMMC scope
- System and data boundaries
- Migration planning
- CUI spillage monitoring
- Post-incident review
- Supply chain and M&A due diligence
The right solution starts with a CUI footprint that can be examined, explained, and defended.
Trusted by leading companies
Choose the Problem You Are Solving
Teramis provides the CUI ground truth organizations need to support compliance decisions, self-attestation, and ongoing CUI governance.
Define the CUI Boundary With Evidence
CUI Boundary Validation
Test Whether the Documented Boundary Matches Reality
Compare your documented boundary with actual findings and surface CUI discovered outside expected or approved locations.
CUI Remediation & Spillage Monitoring
Monitor for CUI Outside Approved Locations
Run recurring scans to identify new findings, changes between scans, and CUI appearing outside the locations your team expects.
Post-Incident CUI Review
Examine Affected Systems for Potential CUI
Use targeted discovery to help determine whether CUI may have existed in affected systems or repositories after a security incident.
Teramis supports factual discovery. It does not make legal, reporting, or notification determinations.
Migration Planning Support
Know What Requires Review Before a Move
Identify files and locations that administrators or approved service providers may need to review when planning authorized CUI migration activity.
Teramis reports findings, and Remedius carries out the actions your team approves.
Supply Chain and M&A Review
Test CUI Representations With Evidence
Examine whether representations about an organization’s CUI footprint are supported by findings from the actual environment.
Use cases include supplier reviews, acquisitions, integration planning, and data-separation planning.
Start Where Your Organization Needs Clarity
Compliance Advisors
Support scoping recommendations with technical CUI evidence that helps clients validate where CUI actually exists and whether the documented boundary matches the real environment.
Enterprise
Build shared visibility across Microsoft 365, distributed repositories, engineering environments, endpoints, and legacy storage.
Government Agencies
Improve visibility into CUI before information enters a publication, sharing, or operational workflow.
Small Business
Find the CUI your organization actually handles before finalizing scope, purchasing licenses, designing an enclave, or preparing for assessment. Teramis helps small businesses focus their next steps on the environment the evidence supports.
Partners
MSPs, MSSPs, compliance advisors, GRC providers, and technology partners can use Teramis to support repeatable discovery, validation, and monitoring services.
vCISOs, enclave partners, and other organizations serving the Defense Industrial Base can strengthen client recommendations with technical CUI findings that complement the services and platforms they already provide.
EVIDENCE-BASED DECISION SUPPORT
How Teramis Supports the Decision Cycle
Teramis is not another platform war. It complements the systems, tools, advisors, and workflows organizations already use by helping identify where CUI actually exists.
- Discover the CUI footprint across supported data sources.
- Compare findings with the intended boundary.
- Review evidence and exceptions that require a decision.
- Plan authorized next steps using file and location details.
- Monitor for changes as systems, users, and projects evolve.
CLEAR PRODUCT BOUNDARIES
Evidence for Decisions. Remediation You Can Prove.
Teramis finds, validates, remediates, and monitors CUI, ITAR, and other covered defense information. Through Remedius, Teramis moves approved CUI to authorized locations, verifies every transfer, removes or tombstones unauthorized copies, and documents what changed. Your team approves every action.
Teramis does not certify an organization, guarantee a compliance or audit outcome, or replace legal, incident-response, compliance, or advisory professionals.
START WITH YOUR CUI QUESTION
SOLUTIONS BY DECISION AND ORGANIZATION
Find the Right Starting Point
Teramis supports different CUI questions across the organization. Choose the decision you need to make or the type of organization you represent.
By Decision
01
CUI Scoping
Identify where CUI exists before determining which systems, repositories, users, and assets belong inside the CUI boundary.
Explore CMMC Scoping →02
CUI Boundary Validation
Compare the documented boundary with actual findings and identify exceptions that require review.
Explore CUI Boundary Validation →03
Spillage Monitoring
Run recurring scans to identify new findings, changes between scans, and CUI appearing outside approved locations.
Explore Spillage Monitoring →04
Migration Planning Support
Identify files and locations that administrators or approved providers may need to review when planning authorized CUI migration activity.
Teramis finds what needs to move and, through Remedius, moves what your team approves, with verification and a documented record.
Explore Migration Planning Support →05
Post-Incident CUI Review
Examine approved portions of affected systems or repositories to help determine whether CUI may have been present after a security incident.
Teramis supports factual discovery. It does not make legal, reporting, or notification decisions.
Explore Post-Incident CUI Review →06
Supply Chain and M&A Review
Use discovery findings to evaluate whether representations about an organization’s CUI footprint align with the actual environment.
Explore Supply Chain and M&A Review →By Organization
Defense Contractors
Establish a clearer CUI baseline before making scope, infrastructure, enclave, licensing, or self-assessment decisions.
Solutions for Defense Contractors →Enterprise
Build shared visibility across Microsoft 365, distributed repositories, engineering environments, endpoints, and legacy storage.
Solutions for Enterprise →Government Agencies
Improve visibility into CUI before information enters a publication, sharing, or operational workflow.
Solutions for Government Agencies →Find Your Starting Point
Make Your Next CUI Decision With Better Evidence
Talk with Teramis about your environment, your data sources, and the CUI question your organization needs to answer.
By Decision
01
CUI Scoping
Support CUI scoping recommendations with technical CUI evidence from the client's actual environment.
Solutions for Compliance Advisors →02
CUI Boundary Validation
Compare the documented boundary with actual findings and identify exceptions that require review.
Explore Boundary Validation →03
Spillage Monitoring
Run recurring scans to identify new findings, changes between scans, and CUI appearing outside approved locations.
Explore Spillage Monitoring →04
Migration Planning Support
Identify files and locations that administrators or approved providers may need to review when planning authorized CUI migration activity.
Teramis finds what needs to move and, through Remedius, moves what your team approves, with verification and a documented record.
Explore Migration Planning →05
Post-Incident CUI Review
Examine approved portions of affected systems or repositories to help determine whether CUI may have been present after a security incident.
Teramis supports factual discovery. It does not make legal, reporting, or notification decisions.
Explore Post-Incident Review →06
Supply Chain and M&A Review
Use discovery findings to evaluate whether representations about an organization’s CUI footprint align with the actual environment.
Explore Supply Chain and M&A →By Organization
01
Compliance Advisory
Support CUI scoping recommendations with technical CUI evidence from the client’s actual environment.
Solutions for Compliance Advisory →02
Enterprise
Build shared visibility across Microsoft 365, distributed repositories, engineering environments, endpoints, and legacy storage.
Solutions for Enterprise →03
Government Agencies
Improve visibility into CUI before information enters a publication, sharing, or operational workflow.
Solutions for Government Agencies →Choose by objective
Find Your Starting Point
We are beginning CMMC planning. Start with CMMC Scoping → We already have a documented boundary. Start with CUI Boundary Validation → We need ongoing visibility. Start with Spillage Monitoring → We are planning an authorized data move. Start with Migration Planning Support → We experienced a security incident. Start with Post-Incident CUI Review → We are reviewing a supplier, acquisition, or integration. Start with Supply Chain and M&A Review →
Need help figuring out where to start?
Choose by objective
Find Your Starting Point
We are beginning our NIST SP 800-171 program. Start with CUI Scoping → We already have a documented boundary. Start with CUI Boundary Validation → We need ongoing visibility. Start with Spillage Monitoring → We are planning an authorized data move. Start with Migration Planning Support → We experienced a security incident. Start with Post-Incident CUI Review → We are reviewing a supplier, acquisition, or integration. Start with Supply Chain and M&A Review →