|
Secure Open Architecture Open System Technologies for Tactical Networks
Navy SBIR 2009.3 - Topic N093-196 NAVSEA - Mr. Dean Putnam - [email protected] Opens: August 24, 2009 - Closes: September 23, 2009 N093-196 TITLE: Secure Open Architecture Open System Technologies for Tactical Networks TECHNOLOGY AREAS: Information Systems ACQUISITION PROGRAM: Submarine Combat and Weapons Control Program Office (PMS425) - ACAT III The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), which controls the export and import of defense-related material and services. Offerors must disclose any proposed use of foreign nationals, their country of origin, and what tasks each would accomplish in the statement of work in accordance with section 3.5.b.(7) of the solicitation. OBJECTIVE: Develop a technology that will segregate data of various security classifications without affecting the system�s open architecture design or open system standard compliance. DESCRIPTION: Technologies for data system security, in particular the NSA High Assurance Platform (HAP), have demonstrated promising results in their ability to securely process, protect and segregate multiple levels of classified and/or sensitive data. These technologies, however, have yet to be applied to submarine tactical environments due to the technical risks inherent with addressing key performance, stability functional, and Navy Open Architecture requirements. This topic will focus on bridging the gap that exists between current state-of-the-art high assurance technology capabilities and the performance, stability, and functional requirements for current and future tactical systems. Efforts will focus on developing technologies that extend beyond or are outside the scope of the NSA HAP. Developing a technology that is robust enough to maintain an open architecture standard while handling sensitive data in a tactical environment will offer great potential to expand the capability of systems while reducing the costs to develop, implement and maintain them. PHASE I: Develop a system design based on the High Assurance Platform Workstation (HAPWS) design for a secure tactical system that does not compromise Navy Open Architecture Standards. The system design should replicate the capabilities, functions and performance characteristics of an actual tactical system. PHASE II: Design and test required prototype hardware and/or software solutions proposed in Phase I on a simulated shipboard network (e.g., in a Navy lab environment). Provide Government with all prototype, design, and software products (to include source code) for Government use only. PHASE III: Install and test the Government approved system on board one or more designated Navy submarines. PRIVATE SECTOR COMMERCIAL POTENTIAL/DUAL-USE APPLICATIONS: This effort has direct applicability to numerous environments where classified or sensitive data is processed. Commercial sectors such as financial services, health care, and critical infrastructure could greatly benefit from the extension of open architecture technology to systems that perform mission critical or real-time processing. REFERENCES: KEYWORDS: Tactical Information Assurance; Navy Open Architecture Standards; Navy Security Requirements; sensitive data segregation; data classification segregation
|