USB Firewall for Direct Connect USB Cyber Warfare Protection
Closed Solicitation Posted
- Solicitation number
- A10-130
- Agency
-
Space and Missile Defense Command
Department of the Army, Department of Defense
- Responses due
- Set-aside
- Total Small Business
Opportunity facts
- NAICS code
- 541715 Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology)
- More information
Notice details come from DoD SBIR/STTR (DSIP). Updated .
Notice text
DoD SBIR topic A10-130
Component: ARMY
Command: SMDC
Phase: SBIR Program Phase I Action
Technology Areas: Electronics; Information Systems; Materials
Keywords: USB; Cyber warfare; Firewall
Objective:
The objective of this effort is to develop a compact USB firewall that can be used to protect government computer systems from Cyber Warfare attacks using common USB devices. The device should enforce the USB standards for devices attached to a computer system, and prevent the devices from performing malicious acts.
Description:
USB is a widely-used interface mechanism in the modern computer industry for peripheral devices (USB can also be used to directly inter-connect computers). While widely used, it is often not understood both by the developer and the security expert. In its basic form, USB forms an extension of the computer’s internal hardware structure/memory to the outside world. To begin to understand the complexity of USB, one must first define what USB is and how it interconnects computers and the external hardware devices. One of the simplest ways of abstracting the interconnect methodology is to view each separate device as an independent entity/computer that is interconnected in a client-server fashion to the central host. Each node on this quasi-network has its own firewall (the USB hardware layer), and under the USB specifications, each node is assumed to follow the documented procedures. The network analogy goes very deep inside the core of how both USB and Firewire are designed. Under USB, each device has its own distinct address assigned by the host computer as per USB specification. This is highly analogous to the IP address used in modern networking. In addition, each USB device can have up to 9 endpoints, which are similar in function to the port on a networked computer. Two of these endpoints are designed in a specific way. Endpoint 0 is a bi-directional endpoint that is used exclusively for control of the USB device. It is used by the host to set basic features and other host client signaling. Endpoint 1 is also a bi-directional endpoint with a data buffer of a fixed size. Both of these endpoints are always defined. The other endpoints are mono-directional and of variable size and may not exist. The specifications of the interface force this kind of structure, and what each controls varies between manufacturers. What is important to note is that unlike older peripheral interfaces (such as RS-232C), a significant amount of USB functionality is embedded in specialized hardware that is not easily accessible or directly controlled by typical equipment manufacturers. This creates an environment where the device, that is a trusted agent, comes from an untrusted source. There are a number of potential vulnerabilities due to malicious USB devices. These include: 1. Malicious code on storage 2. Storage bait-and-switch 3. Monitoring devices 4. Data leaks across device boundaries 5. Keyboard/mouse emulation 6. Remote control 7. Electronic Attack devices Required for this initiative is the development and construction of an inexpensive "USB Firewall” which would act as an intermediary between the on board USB bus and the device to be connected. This device would act as a trusted filter to detect/mitigate malicious activity and hard electronic attack.
Phase I:
Conduct analytical and experimental efforts to demonstrate feasibility of designing a USB firewall which can detect and defend against malicious activity. Proof-of-principle experiments with a brass board device would be encouraged to determine the feasibility of such a device.
Phase II:
Based on the results and findings of Phase I, demonstrate the technology by fabricating and testing a prototype in a laboratory environment. Assemble a proof-of-principle device and demonstrate the proposed technology and its ability to signal an attack warning, identify its characteristics, and defend against the attack. Identify and address technological hurdles. The proposed development and demonstration should be limited to what is required to demonstrate TRL level 4 or level 5 and should identify the means necessary to transition the technology.
Phase III:
This technology could be used in a broad range of military and commercial applications. The final embodiment of this device would be a standalone hardware module where un trusted USB devices could be inserted to minimize damage/virus injection possibilities. The final device should result in a standalone self updatable unit that can be self installed by any user. It should warn the user of possible threat via either on screen message or status lights and require minimal configuration and maintenance.
Files
| File | Type | Posted |
|---|---|---|
| A10-130.pdf |
On GovTribe
Work this opportunity
- Track it in your pipeline
- Find teaming partners
- Similar opportunities
- Ask GovTribe AI about this opportunity