UCDMO Home

Basic Definitions

Domain:  System or group of systems operating under a common security policy.  (CNSSI 4009) 

Controlled Interface:  Mechanism that facilitates the adjudication of different interconnected system security policies (e.g., controlling the flow of information into or out of an interconnected system).  (CNSSI 4009) 

Cross Domain Solution:  Information Assurance solution that provides the ability to access or transfer information between two or more security domains.  (CNSSI 4009) 

Multilevel Security (MLS):  Concept of processing information with different classifications and categories that simultaneously permit access by users with different security clearances and denies access to users who lack authorization.  (CNSSI 4009) 

Cross Domain Solutions (CDS) are a subset of controlled interfaces that provide the capability to access or transfer information across different security domains.

Controlled Interfaces that fall outside of the CDS definition may provide the capability to access or transfer information but operate within a single security domain. Special Access Programs and/or compartments are typically considered to fall in this category. These types of Controlled Interfaces fall under the approval of the local accreditor and are governed by the security policy of the local domain.

What is the relationship between the UCDMO and DHS?  

The UCDMO is currently working with the IC elements of DHS.  It has been discussed at senior levels about expanding the jurisdiction of the UCDMO to include the rest of the DHS but currently the jurisdiction of the UCDMO is limited to the DoD and IC.  POC for CD efforts in DHS is: Mr Daniel Dister, 202.447.3467, Daniel.dister@dhs.gov

Will the UCDMO have members of non US Agencies included in the office?  

The UCDMO will collaborate with our allies and coalition partners on CD issues and activities.  Currently, we do not have any formal arrangement with any non-US organizations.

Does the UCDMO publish Directives and Instructions?    

All Instructions and Directives will be promulgated via the respective authorities.  The UCDMO will work with the respective authorities to ensure the policies are aligned.  The UCDMO will develop, with community participation, the body of the policy, but will submit them to the appropriate office within the DoD and DNI for signature.  

Does the UCDMO have jurisdiction over Manual transfers?

Yes. The establishment memorandum (10 July 2006) and charter (March 2007) describe the UCDMO mission - to provide centralized coordination and oversight of all cross domain activities and investments for the DoD and the IC. This includes requirements and technologies. 

The establishment of the UCDMO per Mr. Meyerrose  in ODNI News Release No. 08-07, dated 8 March 2007 is "...the first of many endeavors that ODNI and OSD are going to undertake to bring National Intelligence and Defense activities into closer alignment as we move to a more integrated, collaborative enterprise."

How do I get my technology onto the Baseline? 

The UCDMO has published a Cross Domain Inventory Management Process Concept of Operations that describes the steps involved to facilitate bringing a new technology onto the baseline.  The UCDMO will review technology for inclusion on the Baseline List of the Cross Domain Inventory, once a formal request is submitted to the UCDMO and if the formal request states that the technology meets all of the following baseline selection criteria: Addresses a capability gap identified in the Cross Domain Roadmap; extends current CDS capabilities; reduces the cost of a current capability; successfully completed CT&E; has a government organization that manages the solution over its lifecycle - lifecycle support for hardware and software; and, is ready to be or has been accredited for operation.

How do I get a copy of the Baseline and see what R&D products are in the pipeline?

The UCDMO' CD Inventory, version 2.3, is posted on Intelink-JWICS at https://www.intelink.ic.gov/sites/ucdmo
and on SiprNet at http://www.intelink.sgov.gov/UCDMO/UCDMO.intel
Intelink-U access is required to access UCDMO FOUO documents at:
https://www.intelink.gov/sites/UCDMO/UCDMO%20Visitor%20Library/Forms/AllItems.aspx

The updated CD Inventory, version 2.3, contains updates to the CD Inventory Guidance, the CD Baseline List, and the Sunset List.  The R&D List is not for publication or for general review.  Once a requirement is identified, further discussion with the appropriate Cross Domain Solutions Office (CDSO) or the UCDMO may point to a solution on the CD Baseline or possibly to a solution in the R&D pipeline.

When would I need to contact the UCDMO when developing a new solution?  

We normally work with the respective service or agency CD program offices when discussing development efforts.  If you are developing a new solution, not an update to a technology on the baseline, you should first contact your CD program office for your service or agency or command prior to contacting the UCDMO.  If you are not sure who your service or agency or command lead is, you can contact our customer outreach division to get that information.

Why isn't my solution on the Baseline?

Various reasons could be responsible for a technology not being listed.  The initial baseline used the following criteria. 
1. The technology must be used to bridge disparate Security Domains. 
2. The technology must have been certified and accredited under either the DCID 6/3 or NSA's SR 1-9. 
3. The technology must have lifecycle support.  Subsequent additions to the baseline must show value added above that of the technologies currently on the baseline.  Additionally, an addition must do one of the following - address a capability Gap (as defined by the UCDMO) or extend a current capability or provide a current level of capability at a reduced cost. 

As a vendor, I want to promote my solution/product to the UCDMO for inclusion on the Baseline List and in the CD Inventory, what should I do?

Before the UCDMO will entertain the review of new products, the developers and vendors should have answered the following questions:

What is the requirement this product is satisfying;

Who is the Government PM and what is the Government Program that is requesting this product;

What is the Technical Capability GAP that is being filled by this product; and,

Has the appropriate CDSO been contacted

Periodically, the UCDMO hosts “Developer Days” to identify programs of interest that may fill CD gaps, and identify programs that may unnecessarily duplicate either existing or planned CD capabilities.  CD Program Managers, sponsors, and developers are sometimes invited to brief “mini program reviews” to a Community SME Panel on their program or project, following a standardized template and questionnaire.  The request to be included on the “Developers Days” schedule should come from the Government Program Manager or respective CDSO that is sponsoring the product, and will go through the UCDMO Plans & Resources Division.

How does an organization sponsor a CDS?

The sponsoring organization must first identify a requirement; define the requirement in terms of mission and environment.  Then the sponsor begins the CD Implementation process by initiating a CD request.  Next, the requirement/request is validated and prioritized by the Agency/Service CD office, or appropriate Cross Domain Solutions Office (CDSO) before being reviewed by the UCDMO.

How do you contact the UCDMO?  

Our Customer Outreach phone # is (240) 373-0796, and you can email us at info@ucdmo.gov. 

Where is the UCDMO located?

Army Research Laboratory
2800 Powder Mill Rd
Hyattsville, MD 20783

We are Building 601 which is also called the Della Whittaker Building.

Use of this U.S. Government system, authorized or unauthorized, constitutes consent to monitoring of this system.
Unauthorized use may subject you to criminal prosecution.
Evidence of unauthorized use collected during monitoring may be used for administrative, criminal, or other adverse actions.