DON27BZ02-NV010.pdf
PDF 52 KB Posted
- Solicitation number
- DON27BZ02-NV010
About this file
This is a Small Business Innovation Research (SBIR) solicitation document for DON27BZ02-NV010, issued by the U.S. Navy, seeking development of an automated tool to cyber harden Linux-based operating systems on Navy platforms, particularly autonomous or unmanned systems.
The objective is to develop software that automatically analyzes Linux OS functionality required by specific platform instantiations, removes unnecessary OS components, and configures remaining systems to improve cybersecurity posture while preserving required functionality. Phase I requires performers to determine a conceptual software architecture for the automated cyber hardening tool, demonstrate capability on a representative platform (preferably a commercial off-the-shelf or open-source autonomous vehicle), and present cybersecurity improvements through code analysis and penetration testing. Phase II involves developing a functional prototype through collaboration with Navy personnel, implementing automated data ingestion from multiple sources (specifications, test plans, etc.), and demonstrating effectiveness through metrics including code reduction, debloating, and penetration testing results. Phase III focuses on commercialization and transition to Navy use, with identified dual-use applications in commercial IoT and Smart Home technology sectors. The solicitation requires compliance with CMMC Level 2 (Self) and aligns with modernization priorities including Advanced Computing and Software, Sustainment and Logistics, and Trusted AI and Autonomy. Technical points of contact are Dan Koller (daniel.p.koller.civ@us.navy.mil) and Ryan Craven (ryan.m.craven2.civ@us.navy.mil).
View the file
Other files
| File | Type | Posted |
|---|---|---|
| NAVY_SBIR_27BZ_PH I_R2.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DON27BZ02-NV010: Automated Hardening for Cyber Secure Operating Systems
PROJECTED CMMC LEVEL REQUIREMENT:
Level 2 (Self)
TECHNOLOGY AREAS:
None
MODERNIZATION PRIORITIES:
Advanced Computing and Software | Sustainment & Logistics | Trusted AI and Autonomy
KEYWORDS:
Cybersecurity; Operating System; OS; cyber hardening; Automation; Zero-Trust
ADDITIONAL INFORMATION
N/A
OBJECTIVE:
Develop an automated tool to cyber harden various platform instantiations built on a Linux operating system.
DESCRIPTION:
Navy platforms have computing devices that drive their operational capabilities, especially autonomous or unmanned systems. Many platforms such as autonomous vehicles have some version and distribution of Linux as their operating system (OS) as well as an application running on it. Providing cybersecurity to these platforms is not only challenging due to their complexities but also very time consuming from a manpower perspective. This workload includes analyzing all levels of software (to include the OS) and configuring them to make them more secure as well as other cyber hardening operations such as software debloating to remove unnecessary functionality. The Navy has many platforms so each would require its own analysis and hardening. There are various means for improving the cybersecurity posture of the platform, each either manual or with its own tool, which creates undue burden on the developer of the platform for hardening without missing certain security features.
The focus of this SBIR effort is strictly on the OS, in this case Linux. The tool should determine the Linux OS functionality actually required by a specific platform instantiation, remove unnecessary OS components and functionality, and configure the remaining Linux OS to improve cybersecurity posture while preserving required system functionality. The goal is to create an automated tool that analyzes the various specifications, configurations, applications, etc. to harden the cybersecurity posture of the underlying Linux OS. The performer should propose their own platform, preferably either a commercial off-the-shelf (COTS) or open source platform that has a Linux OS and use this for design and experimentation on how to automate the cyber hardening of just the OS. It is preferred that the device be some type of autonomous vehicle. The performer will produce an overall software architecture for the automated OS hardening tool as well as a demonstration of the conceptual capability in Phase I while Phase II will involve development of a prototype in cooperation/guidance with Navy personnel. Metrics to demonstrate the improvements from the automated tool should be provided in the proposal.
PHASE I:
Determine a conceptual software architecture for an automated cyber hardening tool for the Linux OS. Ensure that this tool will (1) leverage available runtime information for an existing system to identify the minimal set of OS functionality required for system functionality and (2) then recommend and/or configure the OS, removing unnecessary OS components and functionality and add/or configure recommended security features/functionality. At the conclusion of Phase I, present the proposed software architecture (i.e., the tool’s design and specification of functionality) and a demonstration on a representative platform (e.g., COTS or open-source autonomous platform) that shows improvement in cybersecurity posture (e.g., code analysis, pen testing, etc.). Tools will be compared on cybersecurity OS hardening completeness and approach (i.e., architecture) for ingesting various sources to automate the tool’s execution.
PHASE II:
Develop a functional prototype of the automated tool. Interact with Navy personnel who own a platform and who will provide guidance and experimentation against the prototype OS cyber hardening tool. In conjunction with the Navy, devise, develop, and implement means for verifying the automated OS cyber hardening. Demonstrate that the tool can automatically ingest data sources (e.g., specifications, test plans, other hardening tools capabilities, etc.), and harden and minimalize the Linux OS footprint on the Navy platform. (Note: Navy personnel will examine metrics such as code reduction in the Linux OS, configurations, debloating, code analysis, and pen testing results to measure the effectiveness of the automated OS hardening.) Prepare a Phase III commercialization/transition plan.
PHASE III DUAL USE APPLICATIONS:
Support the transition to Navy use.
Many commercial platforms leverage the Linux OS (e.g., IoT and Smart Home technology). The manufacturers of those devices often implement them on Linux and also need cyber hardening.
REFERENCES:
“Engineering Trustworthy Secure Systems, NIST SP 800-160 Vol. 1 Rev. 1.”
https://csrc.nist.gov/pubs/sp/800/160/v1/r1/final
1.
Brown, Michael D. and Meily, Adam. “Trail of Bits”2.
Fairservice, Brian; Sood, Akshay and Dorn, Jonathan. “GrammaTech”3.
Kilmer, Eric and Eytchison, Ronald, “Trail of Bits.” “A Broad Comparative Evaluation of Software Debloating Tools”. 33rd USENIX Security Symposium.
https://www.usenix.org/conference/usenixsecurity24/presentation/brown
4.
TECHNICAL POINT OF CONTACT (TPOC):
TPOC-1: Dan Koller
PHONE: N/A
EMAIL: daniel.p.koller.civ@us.navy.mil
TPOC-2: Ryan Craven
PHONE: N/A
EMAIL: ryan.m.craven2.civ@us.navy.mil
File details come from the government source that posted it. Updated .