Verification of a Practical Hardware Security Architecture Through Static Information Flow Analysis
Explore the source record for details and available documents.
Andrew Ferraiuolo↗
SEARCH · Search NASA
Results for “hardware security”
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Verification of a Practical Hardware Security Architecture Through Static Information Flow Analysis
Explore the source record for details and available documents.
Andrew Ferraiuolo↗
Verification of a Practical Hardware Security Architecture Through Static Information Flow Analysis
Explore the source record for details and available documents.
Andrew Ferraiuolo↗
Spacecraft Power Source Installation at Launch Complex
For certain space missions, an assembly must be integrated onto the spacecraft as late as possible in the launch vehicle processing flow. 12This late integration can be driven for a variety of reasons including thermal or hazardous materials constraints. This paper discusses the process of integrating an assembly onto a spacecraft as late as one week prior to the opening of the launch window. Consideration is given to achieving sufficient access for hardware integration, methods of remotely securing hardware to the spacecraft, maintaining spacecraft cleanliness throughout the integration process, and electrically integrating the component to the spacecraft. Specific examples are taken from the remote mechanical, electrical, and fluid cooling system integration of the power source onto the Mars Science Laboratory (MSL) Rover at the Atlas V Vertical Integration Facility (VIF) at Cape Canaveral Air Force Station, Florida.
Lytal, Paul↗
Post-Shuttle EVA Operations on ISS
The EVA hardware used to assemble and maintain the ISS was designed with the assumption that it would be returned to Earth on the Space Shuttle for ground processing, refurbishment, or failure investigation (if necessary). With the retirement of the Space Shuttle, a new concept of operations was developed to enable EVA hardware (EMU, Airlock Systems, EVA tools, and associated support equipment and consumables) to perform ISS EVAs until 2016 and possibly beyond to 2020. Shortly after the decision to retire the Space Shuttle was announced, NASA and the One EVA contractor team jointly initiated the EVA 2010 Project. Challenges were addressed to extend the operating life and certification of EVA hardware, secure the capability to launch EVA hardware safely on alternate launch vehicles, and protect EMU hardware operability on orbit for long durations.
West, Bill↗
Architecture for Survivable System Processing (ASSP)
The Architecture for Survivable System Processing (ASSP) Program is a multi-phase effort to implement Department of Defense (DOD) and commercially developed high-tech hardware, software, and architectures for reliable space avionics and ground based systems. System configuration options provide processing capabilities to address Time Dependent Processing (TDP), Object Dependent Processing (ODP), and Mission Dependent Processing (MDP) requirements through Open System Architecture (OSA) alternatives that allow for the enhancement, incorporation, and capitalization of a broad range of development assets. High technology developments in hardware, software, and networking models, address technology challenges of long processor life times, fault tolerance, reliability, throughput, memories, radiation hardening, size, weight, power (SWAP) and security. Hardware and software design, development, and implementation focus on the interconnectivity/interoperability of an open system architecture and is being developed to apply new technology into practical OSA components. To insure for widely acceptable architecture capable of interfacing with various commercial and military components, this program provides for regular interactions with standardization working groups (e.g.) the International Standards Organization (ISO), American National Standards Institute (ANSI), Society of Automotive Engineers (SAE), and Institute of Electrical and Electronic Engineers (IEEE). Selection of a viable open architecture is based on the widely accepted standards that implement the ISO/OSI Reference Model.
Wood, Richard J.↗
EVA 2010: Preparing for International Space Station EVA Operations Post-Space Shuttle Retirement
The expected retirement of the NASA Space Transportation System (also known as the Space Shuttle ) by 2011 will pose a significant challenge to Extra-Vehicular Activities (EVA) on-board the International Space Station (ISS). The EVA hardware currently used to assemble and maintain the ISS was designed assuming that it would be returned to Earth on the Space Shuttle for refurbishment, or if necessary for failure investigation. With the retirement of the Space Shuttle, a new concept of operations was developed to enable EVA hardware (Extra-vehicular Mobility Unit (EMU), Airlock Systems, EVA tools, and associated support hardware and consumables) to perform ISS EVAs until 2015, and possibly beyond to 2020. Shortly after the decision to retire the Space Shuttle was announced, the EVA 2010 Project was jointly initiated by NASA and the OneEVA contractor team. The challenges addressed were to extend the operating life and certification of EVA hardware, to secure the capability to launch EVA hardware safely on alternate launch vehicles, to protect for EMU hardware operability on-orbit, and to determine the source of high water purity to support recharge of PLSSs (no longer available via Shuttle). EVA 2010 Project includes the following tasks: the development of a launch fixture that would allow the EMU Portable Life Support System (PLSS) to be launched on-board alternate vehicles; extension of the EMU hardware maintenance interval from 3 years (current certification) to a minimum of 6 years (to extend to 2015); testing of recycled ISS Water Processor Assembly (WPA) water for use in the EMU cooling system in lieu of water resupplied by International Partner (IP) vehicles; development of techniques to remove & replace critical components in the PLSS on-orbit (not routine); extension of on-orbit certification of EVA tools; and development of an EVA hardware logistical plan to support the ISS without the Space Shuttle. Assumptions for the EVA 2010 Project included no more than 8 EVAs per year for ISS EVA operations in the Post-Shuttle environment and limited availability of cargo upmass on IP launch vehicles. From 2010 forward, EVA operations on-board the ISS without the Space Shuttle will be a paradigm shift in safely operating EVA hardware on orbit and the EVA 2010 effort was initiated to accommodate this significant change in EVA evolutionary history.
Chullen, Cinda↗
Post-Shuttle EVA Operations on ISS
The expected retirement of the NASA Space Transportation System (also known as the Space Shuttle ) by 2011 will pose a significant challenge to Extra-Vehicular Activities (EVA) on-board the International Space Station (ISS). The EVA hardware currently used to assemble and maintain the ISS was designed assuming that it would be returned to Earth on the Space Shuttle for refurbishment, or if necessary for failure investigation. With the retirement of the Space Shuttle, a new concept of operations was developed to enable EVA hardware (Extra-vehicular Mobility Unit (EMU), Airlock Systems, EVA tools, and associated support hardware and consumables) to perform ISS EVAs until 2015, and possibly beyond to 2020. Shortly after the decision to retire the Space Shuttle was announced, the EVA 2010 Project was jointly initiated by NASA and the One EVA contractor team. The challenges addressed were to extend the operating life and certification of EVA hardware, to secure the capability to launch EVA hardware safely on alternate launch vehicles, to protect for EMU hardware operability on-orbit, and to determine the source of high water purity to support recharge of PLSSs (no longer available via Shuttle). EVA 2010 Project includes the following tasks: the development of a launch fixture that would allow the EMU Portable Life Support System (PLSS) to be launched on-board alternate vehicles; extension of the EMU hardware maintenance interval from 3 years (current certification) to a minimum of 6 years (to extend to 2015); testing of recycled ISS Water Processor Assembly (WPA) water for use in the EMU cooling system in lieu of water resupplied by International Partner (IP) vehicles; development of techniques to remove & replace critical components in the PLSS on-orbit (not routine); extension of on-orbit certification of EVA tools; and development of an EVA hardware logistical plan to support the ISS without the Space Shuttle. Assumptions for the EVA 2010 Project included no more than 8 EVAs per year for ISS EVA operations in the Post-Shuttle environment and limited availability of cargo upmass on IP launch vehicles. From 2010 forward, EVA operations on-board the ISS without the Space Shuttle will be a paradigm shift in safely operating EVA hardware on orbit and the EVA 2010 effort was initiated to accommodate this significant change in EVA evolutionary history. 1
West, William↗
Security for Multimedia Space Data Distribution over the Internet
Distribution of interactive multimedia to remote investigators will be required for high quality science on the International Space Station (ISS). The Internet with the World Wide Web (WWW) and the JAVA environment are a good match for distribution of data, video and voice to remote science centers. Utilizing the "open" Internet in a secure manner is the major hurdle in making use of this cost effective, off-the-shelf, universal resource. This paper examines the major security threats to an Internet distribution system for payload data and the mitigation of these threats. A proposed security environment for the Space Station Biological Research Facility (SSBRP) is presented with a short description of the tools that have been implemented or planned. Formulating and implementing a security policy, firewalls, host hardware and software security are also discussed in this paper. Security is a vast topic and this paper can only give an overview of important issues. This paper postulates that a structured approach is required and stresses that security must be built into a network from the start. Ignoring security issues or putting them off until late in the development cycle can be disastrous.
Stone, Thom↗
Secure Networks for First Responders and Special Forces
When NASA needed help better securing its communications with orbiting satellites, the Agency called on Western DataCom Co., Inc., to help develop a prototype Internet Protocol (IP) router. Westlake, Ohio-based Western DataCom designs, develops, and manufactures hardware that secures voice, video, and data transmissions over any IP-based network. The technology that it jointly developed with NASA is now serving as a communications solution in military and first-response situations.
Source record↗
RS-34 Phoenix (Peacekeeper Post Boost Propulsion System) Utilization Study
The Advanced Concepts Office (ACO) at the NASA Marshall Space Flight Center (MSFC) in conjunction with Pratt & Whitney Rocketdyne conducted a study to evaluate potential in-space applications for the Rocketdyne produced RS-34 propulsion system. The existing RS-34 propulsion system is a remaining asset from the de-commissioned United States Air Force Peacekeeper ICBM program, specifically the pressure-fed storable bipropellant Stage IV Post Boost Propulsion System, renamed Phoenix. MSFC gained experience with the RS-34 propulsion system on the successful Ares I-X flight test program flown in October 2009. RS-34 propulsion system components were harvested from stages supplied by the USAF and used on the Ares I-X Roll control system (RoCS). The heritage hardware proved extremely robust and reliable and sparked interest for further utilization on other potential in-space applications. MSFC is working closely with the USAF to obtain RS-34 stages for re-use opportunities. Prior to pursuit of securing the hardware, MSFC commissioned the Advanced Concepts Office to understand the capability and potential applications for the RS-34 Phoenix stage as it benefits NASA, DoD, and commercial industry. As originally designed, the RS-34 Phoenix provided in-space six-degrees-of freedom operational maneuvering to deploy multiple payloads at various orbital locations. The RS-34 Phoenix Utilization Study sought to understand how the unique capabilities of the RS-34 Phoenix and its application to six candidate missions: 1) small satellite delivery (SSD), 2) orbital debris removal (ODR), 3) ISS re-supply, 4) SLS kick stage, 5) manned GEO servicing precursor mission, and an Earth-Moon L-2 Waypoint mission. The small satellite delivery and orbital debris removal missions were found to closely mimic the heritage RS-34 mission. It is believed that this technology will enable a small, low-cost multiple satellite delivery to multiple orbital locations with a single boost. For both the small satellite delivery and the orbital debris mission candidates, the RS-34 Phoenix requires the least amount of modification to the existing hardware. The results of the RS-34 Phoenix Utilization Study show that the system is technically sufficient to successfully support all of the missions analyzed.
Esther, Elizabeth A.↗
RS-34 Phoenix (Peacekeeper Post Boost Propulsion System) Utilization Study
The Advanced Concepts Office (ACO) at the NASA Marshall Space Flight Center (MSFC) in conjunction with Pratt & Whitney Rocketdyne conducted a study to evaluate potential in-space applications for the Rocketdyne produced RS-34 propulsion system. The existing RS-34 propulsion system is a remaining asset from the decommissioned United States Air Force Peacekeeper ICBM program; specifically the pressure-fed storable bipropellant Stage IV Post Boost Propulsion System, renamed Phoenix. MSFC gained experience with the RS-34 propulsion system on the successful Ares I-X flight test program flown in October 2009. RS-34 propulsion system components were harvested from stages supplied by the USAF and used on the Ares I-X Roll control system (RoCS). The heritage hardware proved extremely robust and reliable and sparked interest for further utilization on other potential in-space applications. Subsequently, MSFC is working closely with the USAF to obtain all the remaining RS-34 stages for re-use opportunities. Prior to pursuit of securing the hardware, MSFC commissioned the Advanced Concepts Office to understand the capability and potential applications for the RS-34 Phoenix stage as it benefits NASA, DoD, and commercial industry. Originally designed, the RS-34 Phoenix provided in-space six-degrees-of freedom operational maneuvering to deploy multiple payloads at various orbital locations. The RS-34 Phoenix Utilization Study sought to understand how the unique capabilities of the RS-34 Phoenix and its application to six candidate missions: 1) small satellite delivery (SSD), 2) orbital debris removal (ODR), 3) ISS re-supply, 4) SLS kick stage, 5) manned GEO servicing precursor mission, and an Earth-Moon L-2 Waypoint mission. The small satellite delivery and orbital debris removal missions were found to closely mimic the heritage RS-34 mission. It is believed that this technology will enable a small, low-cost multiple satellite delivery to multiple orbital locations with a single boost. For both the small satellite delivery and the orbital debris mission candidates, the RS-34 Phoenix requires the least amount of modification to the existing hardware. The results of the RS-34 Phoenix Utilization Study show that the system is technically sufficient to successfully support all of the missions analyzed
Esther, Elizabeth A.↗
RS-34 (Peacekeeper Post Boost Propulsion System) Orbital Debris Application Concept Study
The Advanced Concepts Office (ACO) at the NASA Marshall Space Flight Center (MSFC) lead a study to evaluate the Rocketdyne produced RS-34 propulsion system as it applies to an orbital debris removal design reference mission. The existing RS-34 propulsion system is a remaining asset from the de-commissioned United States Air Force Peacekeeper ICBM program; specifically the pressure-fed storable bi-propellant Stage IV Post Boost Propulsion System. MSFC gained experience with the RS-34 propulsion system on the successful Ares I-X flight test program flown in the Ares I-X Roll control system (RoCS). The heritage hardware proved extremely robust and reliable and sparked interest for further utilization on other potential in-space applications. Subsequently, MSFC is working closely with the USAF to obtain all the remaining RS-34 stages for re-use opportunities. Prior to pursuit of securing the hardware, MSFC commissioned the Advanced Concepts Office to understand the capability and potential applications for the RS-34 Phoenix stage as it benefits NASA, DoD, and commercial industry. Originally designed, the RS-34 Phoenix provided in-space six-degrees-of freedom operational maneuvering to deploy multiple payloads at various orbital locations. The RS-34 Concept Study, preceded by a utilization study to understand how the unique capabilities of the RS-34 Phoenix and its application to six candidate missions, sought to further understand application for an orbital debris design reference mission as the orbital debris removal mission was found to closely mimic the heritage RS-34 mission. The RS-34 Orbital Debris Application Concept Study sought to identify multiple configurations varying the degree of modification to trade for dry mass optimization and propellant load for overall capability and evaluation of several candidate missions. The results of the RS-34 Phoenix Utilization Study show that the system is technically sufficient to successfully support all of the missions analyzed. The results and benefits of the RS-34 Orbital Debris Application Concept Study are presented in this paper.
Esther, Elizabeth A.↗
A tensor approach to modeling of nonhomogeneous nonlinear systems
Model following control methodology plays a key role in numerous application areas. Cases in point include flight control systems and gas turbine engine control systems. Typical uses of such a design strategy involve the determination of nonlinear models which generate requested control and response trajectories for various commands. Linear multivariable techniques provide trim about these motions; and protection logic is added to secure the hardware from excursions beyond the specification range. This paper reports upon experience in developing a general class of such nonlinear models based upon the idea of the algebraic tensor product.
Yurkovich, S.↗
Trace Oxygen Measurements of Asteroid Sample Storage Desiccators
The Astromaterials Curation facility at the NASA Johnson Space Center is currently curating more than 120 g of carbonaceous asteroid Bennu material as well as over 500 mg of asteroid Ryugu [1 and 2]. These astromaterials are stored in isolating desiccators and gloveboxes under a continuous purge of pure (<1 ppm O 2 ) gaseous nitrogen. The oxygen and moisture concentrations in our OSIRIS-REx sample processing gloveboxes are continuously monitored via integrated sensors; however, our sample storage desiccators lack integrated oxygen and humidity sensors. In previous studies, we used PreSens Fibox 4 trace oxygen meters and optochemical PSt9 spot sensors to measure the oxygen concentrations in candidate asteroid sample containers that had been sealed in nitrogen; we determined that Eagle stainless steel containers inhibit the ingress of external oxygen for several weeks [3]. This optochemical sensor technology allowed us to take precise, contactless measurements within a trace range of 0 to 200 ppmv O 2 . The effectiveness of the trace oxygen sensors in our container experiments inspired us to utilize them to assess the performance of our desiccators that previously lacked trace oxygen monitoring. In this study, our goal was to determine the quality of the nitrogen purge in the isolating desiccator under normal operating conditions by measuring the trace oxygen content. Utilizing optochemical sensor technology, we determined how long the oxygen concentration takes to reach an equilibrium in the desiccator; that is, determine the rate at which the oxygen diffusion into the desiccator equals the rate at which oxygen diffuses out of the desiccator via N2 purge. Additionally, we wanted to determine the oxygen concentration at this equilibrium, the state in which our desiccators are in during normal operating conditions. We tested a custom three chamber desiccator manufactured by Germfree using a PSt9 trace oxygen sensor spot that was mounted into a ¼” National Pipe Tapered (NPT) metal flow-through cell and attached it to the desiccator exhaust. The desiccator consists of top, middle, and bottom isolating chambers. The top chamber door was opened for several minutes to simulate a sample exchange, it was sealed, and then purged ~15 Standard Cubic Feet per Hour (SCFH). Oxygen measurements were automatically recorded via the Fibox 4 trace oxygen meter in 5-minute intervals over the course of a 24-hour period. Our results indicate the desiccator reached an equilibrium value of 10-15 ppm O 2 after ~5 hours (Fig. 1). This data allows us to explore standards for purging and exchange protocols that can be applied to similar types of desiccators in Hayabusa2, OSIRIS-REx, and for sample return collections. The assessment of the internal gaseous compositions of desiccators also allows us to share with the community the N 2 environment in which many of our asteroid samples and hardware are securely curated. Future measurements will include other nitrogen flow rates and measuring the trace oxygen concentration as a function of time for the levels of the previous commercial desiccator in which the Hayabusa2 sample collection was stored. We will also analyze how long the desiccators hold N2 after being disconnected from their N2 source, an extended measurement for sample security reassurance.
Curation↗
Genomics and Proteomics Based Security Protocols for Secure Network Architectures
A hardware design that integrates live and algorithmic inhabitants to produce patterns of gene expression in vivo and in silico Protocols and algorithms based upon the processes of regulation of gene expression to produce cryptographic representations of genes, RNA, proteins, and gene expression to perform authentication and confidentiality functions for computers and networks. A network concept of operations integrating all of the above into existing legacy networks.
Security Genomics↗
IT Security Support for the Spaceport Command Control Systems Development Ground Support Development Operations
Security is one of the most if not the most important areas today. After the several attacks on the United States, security everywhere was heightened from Airports to the communication among the military branches legionnaires. With advanced persistent threats (APTs) on the rise following Stuxnet, government branches and agencies are required, more than ever, to follow several standards, policies and procedures to reduce the likelihood of a breach. Attack vectors today are very advanced and are going to continue to get more and more advanced as security controls advance. This creates a need for networks and systems to be in an updated and secured state in a launch control system environment. FISMA is a law that is mandated by the government to follow when government agencies secure networks and devices. My role on this project is to ensure network devices and systems are in compliance with NIST, as outlined in FISMA. I will achieve this by providing assistance with security plan documentation and collection, system hardware and software inventory, malicious code and malware scanning and configuration of network devices i.e. routers and IDSsIPSs. In addition I will be completing security assessments on software and hardware, vulnerability assessments and reporting, conducting patch management and risk assessments. A guideline that will help with compliance with NIST is the SANS Top 20 Critical Controls. SANS Top 20 Critical Controls as well as numerous security tools, security software and the conduction of research will be used to successfully complete the tasks given to me. This will ensure compliance with FISMA and NIST, secure systems and a secured network. By the end of this project, I hope to have carried out stated above as well as gain an immense knowledge about compliance, security tools, networks and network devices, policies and procedures.
computer information security↗
IT Security Support for the Spaceport Command Control Systems Development Ground Support Development Operations
Security is one of the most if not the most important areas today. After the several attacks on the United States, security everywhere has heightened from airports to the communication among the military branches legionnaires. With advanced persistent threats (APT's) on the rise following Stuxnet, government branches and agencies are required, more than ever, to follow several standards, policies and procedures to reduce the likelihood of a breach. Attack vectors today are very advanced and are going to continue to get more and more advanced as security controls advance. This creates a need for networks and systems to be in an updated and secured state in a launch control system environment. FISMA is a law that is mandated by the government to follow when government agencies secure networks and devices. My role on this project is to ensure network devices and systems are in compliance with NIST, as outlined in FISMA. I will achieve this by providing assistance with security plan documentation and collection, system hardware and software inventory, malicious code and malware scanning, and configuration of network devices i.e. routers and IDS's/IPS's. In addition, I will be completing security assessments on software and hardware, vulnerability assessments and reporting, and conducting patch management and risk assessments. A guideline that will help with compliance with NIST is the SANS Top 20 Critical Controls. SANS Top 20 Critical Controls as well as numerous security tools, security software and the conduction of research will be used to successfully complete the tasks given to me. This will ensure compliance with FISMA and NIST, secure systems and a secured network. By the end of this project, I hope to have carried out the tasks stated above as well as gain an immense knowledge about compliance, security tools, networks and network devices, as well as policies and procedures.
security↗