A Brief Note on Raise the Bar and One-Way Transfer

A Brief Note on Raise the Bar and One-Way Transfer


This past year’s publication of the National Cross Domain Strategy and Management Office (NCDSMO) “Raise the Bar” (RTB) mandate is causing a positive transformation of the cross domain solution (CDS) market. However, like any increase in government regulation on an industry, there will be some impacts to customers that will be seen in cost, performance, and operational procedures, as well as the loss of some vendor participation in the CDS market.

The RTB mandate’s focus on improving the security of CDS data flow and content filtering controls has produced new, more complex CDS architectures. The overall result in these architectures is much more rigorous processes and greater assurance for system and data owners concerning the protection of their mission and enterprise dataflows that are transferring content.

One aspect of the increased assurance is the recognition that hardware-enforced one-way transfer mechanisms are an essential component for system and data owners that need cross domain transfer of information with either the source or destination being a less trusted (e.g., Unclassified, High Threat, Internet) network.

Hardware-enforced one-way transfer mechanisms, a core component in every Owl solution, prevent any and all aspects of back channel communications originating from any of those less trusted networks. System and data owners must employ hardware-enforced one-way transfer mechanisms for any touchpoint that they deem has any substantive degree of risk to ensure their infrastructures are protected from unauthorized connectivity. As such, during the transition to bring all of Owl CDSs to RTB compliance, Owl will continue to provide customers with hardware-enforced data diode one-way transfer devices to ensure the continued protection of government assets and national security.

For more information on Owl hardware-enforced one-way transfer mechanisms and systems, please visit our Cross Domain Solutions Products page.

Charlie Schick Healthcare Consultant

Why Do A Medical Device Assessment, Part 3: The Device

In the previous two posts in this series, I talked about the reasons cybersecurity analysis on medical devices is necessary and some processes behind device analysis. In the next coupl...
October 21, 2020
Board inspection
Charlie Schick Healthcare Consultant

Why Do A Medical Device Assessment, Part 2: How We Do It

In my last post, I talked a bit about the cybersecurity challenges around medical devices. In this post, I want to tell you a bit about the process of device cybersecurity analysis, wi...
October 15, 2020
Device Assessment
Charlie Schick Healthcare Consultant

Why Do A Medical Device Assessment, Part 1: “It’s Not a Good Situation”

Relevant to this series, Owl’s Device Inspection and Analysis Lab focuses on security analysis of all sorts of devices, ranging from laptops, servers, and mobile devices; to securing op...
October 7, 2020