GALOIS, INC. — Department of Defense STTR Phase II: N152-120
GALOIS, INC. — STTR Phase II award from Department of Defense.
Phase II STTR prototype / development signal
- Phase II is where Department of Defense funds deeper R&D after feasibility. Incumbents with Phase II history are serious competitors on adjacent topics.
- Use this award as past-performance context and to map customer organizations for STRATFI/TACFI-style transition planning.
- At $1,799,837, this is a large obligation for typical SBIR Phase sizing — worth reviewing for scope breadth and teaming opportunity.
- Topic code N152-120 links this award to a solicitation family — search the same topic stem for incumbents and recompete timing.
- Amount
- $1,799,837
- Agency
- Department of Defense · Defense Advanced Research Projects Agency
- Program / Phase
- STTR · Phase II
- Topic
- N152-120
- Solicitation
- 15.2
- NAICS
- —
- Place of performance
- OR
- Period
- 2023-08-11 → 2025-02-13
Description
In the Phase I and II efforts on Galois' Attack Sensitive Brittle Software (Brittle) SBIR project, we implemented Software Fault Enhancement (SFE), a binary modification technique for improving the robustness of existing binary code, without requiring access to source code or other documentation. This work is promising enough that the toolset is now being commercialized. On this sequential Phase II project, we will extend and integrate recent work on symbolic, concrete, and timed trace analysis to implement new means of providing assurance to the user that binary modifications made for SFE do not result in additional, unwanted changes in behavior. This specifically includes changes in timed behavior, important in the operation of embedded systems such as digital control systems. The results of this project will be useful for providing such assurance for a range of applications of localized binary modification. In addition to SFE, these include patching bugs or removing possible execution paths (e.g., removing application features), or instrumenting binaries to gather run-time information for further testing and analysis. In all of these cases, potential end-users need assurance that the modified binaries will behave as before, except in circumscribed ways related to the goal of the modification as above.