ASSURED INFORMATION SECURITY, INC. — Department of Defense STTR Phase II: HR001120S0019-001

ASSURED INFORMATION SECURITY, 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 $2,499,721, this is a large obligation for typical SBIR Phase sizing — worth reviewing for scope breadth and teaming opportunity.
  • Topic code HR001120S0019-001 links this award to a solicitation family — search the same topic stem for incumbents and recompete timing.

Informational capture context from public federal data — not legal or bid advice.

Amount
$2,499,721
Agency
Department of Defense · Defense Advanced Research Projects Agency
Program / Phase
STTR · Phase II
Topic
HR001120S0019-001
Solicitation
HR001120S0019.T
NAICS
Place of performance
NY
Period
2021-07-07 → 2024-10-13

Description

In the ACADIANA effort, we will address the inability of modern programming language, operating system, and architectural abstractions to provide a baseline level of adequate confidentiality protections. Until now, developers and users of software have largely relied on their programming language and operating system to ensure that confidential data isn’t leaked out of a process’ memory space or that malicious data won’t exploit the process’ code. However, recent architectural side-channel attacks have demonstrated that the baked-in default protection mechanisms provided to users of modern programming languages and operating systems are wholly inadequate to the task of providing adequate confidentiality guarantees. Under ACADIANA, we will overcome this problem by researching and developing a system that 1) augments a strictly-typed, memory safe programming language with a non-burdensome annotation domain-specific language for enabling / disabling runtime protections via the ABI, and 2) provides associated runtime protection mechanisms that enforce developer specified constraints as per annotations from the vantage point of an introspective hypervisor.