# US 2018/0322288 A1 · Method for manufacturing and executing single-use systems > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0322288 A1 - Document ID: US20180322288A1 - Status: Published application - Kind: A1 - Application number: 15/950,675 - Filed: 2018-04-11 - Published: 2018-11-08 - Earliest claimed: 2017-05-02 - Assignees: The United States of America as represented by the Secretary of the Air Force - Applicants: Goverment of the United States AS Represented By the Secretary of the Air Force - Inventors: KAMAL T. JABBOUR; ERICH D. DEVENDORF; ANDREW N. ZELIFF - Web page: https://patentgrep.com/patent/US20180322288A1 ## CPC - G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities - G06F 2221/034: Test or assess a computer or a system - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method for manufacturing and executing single-use systems. Invention provides provably secure system design, instantiated in heterogeneous hardware that exists solely for the lifetime of a mission. More specifically, the present invention provides a functional mission analysis, formal specification and mathematically rigorous machine-checkable representation of a hardware mission instantiation to significantly reduce the vulnerabilities of a mission. ## Claims ### Claim 1 (canceled) ### Claim 2 A computer-implemented method for executing a single-use computer hardware system, the method comprising: executing a finite state machine representative of predefined parameters associated with a mission, wherein the mission comprises a predefined computerized process used for a fixed duration and for a single-use, and wherein the finite state machine generates an output; compiling software code from the finite state machine to create a computerized instantiation from the output of the finite state machine; and transforming the computerized instantiation into a mission-specific hardware design computer language representative of a mission-specific integrated single-use computer hardware system. ### Claim 3 (depends on 2) The method of claim 2, further comprising: defining the parameters associated with the mission; and performing a functional mission analysis based on the defined parameters to decompose the mission into a computerized control action diagram, wherein the functional mission analysis creates logical formulae. ### Claim 4 (depends on 3) The method of claim 3, further comprising: developing access control logic based on the computerized control action diagram; proving a validity of the access control logic; and producing the finite state machine based on the valid access control logic. ### Claim 5 (depends on 4) The method of claim 4, further comprising: randomizing the computerized instantiation of the finite state machine, wherein the computerized instantiation comprises attributes of the computer hardware system; and translating the finite state machine to the software code. ### Claim 6 (depends on 5) The method of claim 5, wherein the attributes of the computer hardware system comprise any of a type of computer hardware platform, an instruction set architecture/alterations of the computer hardware system, whether the computer hardware system comprises a ternary or binary system architecture, whether the computer hardware system comprises a Harvard or Von Neumann architecture, command protocols of the computer hardware system, a cryptographic algorithm associated with the computer hardware system, cryptographic key materials of the computer hardware system, a management scheme of the computer hardware system, a distribution scheme of the computer hardware system, inter-instantiation protocols of the computer hardware system, and intra-instantiation protocols/bus choice of the computer hardware system, and a word length associated bits processed by the computer hardware system. ### Claim 7 (depends on 5) The method of claim 5, further comprising: translating the proven valid access control logic into a machine checkable specification; inserting the machine checkable specification into the software code; inserting the machine checkable specification into the finite state machine; and creating the computerized instantiation from the finite state machine. ### Claim 8 (depends on 7) The method of claim 7, wherein the mission-specific hardware design computer language comprises a computer hardware descriptor language. ### Claim 9 (depends on 7) The method of claim 7, further comprising instantiating hardware from the mission-specific hardware design computer language. ### Claim 10 (depends on 9) The method of claim 9, further comprising integrating randomized system binaries into the instantiated hardware to introduce system entropy into an executable software program run by the single-use computer hardware system. ### Claim 11 (depends on 2) The method of claim 2, wherein the fixed duration of the predefined computerized process is approximately 12 hours. ### Claim 12 (depends on 2) The method of claim 2, further comprising reusing the finite state machine for subsequent missions. ### Claim 13 A mission-specific integrated single-use computer hardware system comprising: a finite state machine representative of predefined parameters associated with a mission, wherein the mission comprises a predefined computerized process used for a fixed duration and for a single-use, and wherein the finite state machine generates an output; software code compiled from the finite state machine, wherein the software code creates a computerized instantiation of the output of the finite state machine; and computer architecture to transform the computerized instantiation into a mission-specific hardware design computer language representative the mission-specific integrated single-use computer hardware system. ### Claim 14 (depends on 13) The system of claim 13, wherein the computer architecture is to: perform a functional mission analysis based on the defined parameters to decompose the mission into a computerized control action diagram, wherein the functional mission analysis creates logical formulae. ### Claim 15 (depends on 14) The system of claim 14, wherein the computer architecture is to: develop access control logic based on the computerized control action diagram; prove a validity of the access control logic; and produce the finite state machine based on the proven valid access control logic. ### Claim 16 (depends on 15) The system of claim 15, wherein the computer architecture is to: randomize the computerized instantiation of the output of the finite state machine, wherein the computerized instantiation comprises attributes of the computer hardware system; and translate the finite state machine to the software code. ### Claim 17 (depends on 16) The system of claim 16, wherein the attributes of the computer hardware system comprise any of a type of computer hardware platform, an instruction set architecture/alterations of the computer hardware system, whether the computer hardware system comprises a ternary or binary system architecture, whether the computer hardware system comprises a Harvard or Von Neumann architecture, command protocols of the computer hardware system, a cryptographic algorithm associated with the computer hardware system, cryptographic key materials of the computer hardware system, a management scheme of the computer hardware system, a distribution scheme of the computer hardware system, inter-instantiation protocols of the computer hardware system, and intra-instantiation protocols/bus choice of the computer hardware system, and a word length associated bits processed by the computer hardware system. ### Claim 18 (depends on 16) The system of claim 16, wherein the computer architecture is to: translate the proven valid access control logic into a machine checkable specification; insert the machine checkable specification into the software code; insert the machine checkable specification into the finite state machine; and create the computerized instantiation of the output of the finite state machine. ### Claim 19 (depends on 18) The system of claim 18, wherein the mission-specific hardware design computer language comprises a computer hardware descriptor language. ### Claim 20 (depends on 18) The system of claim 18, wherein the computer architecture is to instantiate hardware from the mission-specific hardware design computer language. ### Claim 21 (depends on 20) The system of claim 20, wherein the computer architecture is to integrate randomized system binaries into the instantiated hardware to introduce system entropy into an executable software program run by the single-use computer hardware system.