Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Information 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.

At least 145 records · Page 8
All sourcesNASA NTRSDOE OSTI
DOE OSTI2026

Facilitating Data Collection of Maintenance Events to Populate the Hydrogen Component Reliability Database (HyCReD)

The Hydrogen Component Reliability Database (HyCReD) is a collaborative project between the National Renewable Energy Laboratory, the University of Maryland, and hydrogen stakeholders to improve safety and reliability for hydrogen facilities by implementing component reliability data taxonomies that support hydrogen infrastructure failure rate analysis. The project aims to quantify failure rates of hydrogen components through high-quality data collection and analysis on root causes and maintenance needed. HyCReD provides a common database for cataloging hydrogen component failures which exists for reliability research in many other mature industries [2]. The database fills a gap for the hydrogen community by providing a scientifically rigorous approach to quantitative risk assessment (QRA), prognostic health management (PHM), and reliability-centered maintenance (RCM) analysis. High level results will be aggregated and anonymized to protect company sensitive information; detailed results will be used to help address issues of hydrogen components. These advanced analytics will support accelerated deployment of hydrogen infrastructure by enabling better: design and safety of projects (safety codes and standards development), infrastructure reliability and cost (component failure rates, maintenance protocols), and component R&D needs (robust supply chain). A key to a successful HyCReD implementation is facilitating the ease of reporting and data quality in the database that can be used for analysis. Maintenance data was a previously identified gap in initial efforts to populate and validate the database taxonomies [3]. Collection of maintenance data will be instrumental in identifying failure modes and rates, identifying incipient component failures or reduced performance, cataloging best practices for maintenance routines and methods for prognostic health management, and quantifying the risk and effect of different failure modes. Several key priorities are identified for streamlined data collection to achieve quality and detailed failure data: Applicability, Ease of Use, Accessibility, and Information Security. The HyCReD team has now begun deployment of the database to several companies and groups that have signed non-disclosure agreements to facilitate the data collection of failures in industry hydrogen refueling station infrastructure. This paper will provide an update into the process of HyCReD deployment including the development of a coding guide for facility personnel to reference and ensure data quality and consistency from one station to another as well as implementation of contextually dependent data fields of system taxonomy and formatted entries to provide ease of use. The goal is to communicate the lessons learned from the roll-out to technicians and engineers in the field, and the addition of need for high level of security to protect all stakeholders.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗
DOE OSTI2026

Studies in Nuclear and Nucleon Structure, and Neutrino Physics

We have provided training to students in skill sets relevant to job placement in areas of national needs. These trainings are tuned towards placing graduating students in the workforce related to sciences at national laboratories, national security, information systems, and data sciences. The support for undergraduate students will address the academic retention shortfalls by providing opportunities in mentored research experiences.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗
NASA NTRS2004

A Recipe for Streamlining Mission Management

This paper describes a project's design and implementation for streamlining mission management with knowledge capture processes across multiple organizations of a NASA directorate. Thc project's focus is on standardizing processes and reports; enabling secure information access and case of maintenance; automating and tracking appropriate workflow rules through process mapping; and infusing new technologies. This paper will describe a small team's experiences using XML technologies through an enhanced vendor suite of applications integrated on Windows-based platforms called the Wallops Integrated Scheduling and Document Management System (WISDMS). This paper describes our results using this system in a variety of endeavors, including providing range project scheduling and resource management for a Range and Mission Management Office; implementing an automated Customer Feedback system for a directorate; streamlining mission status reporting across a directorate; and initiating a document management, configuration management and portal access system for a Range Safety Office's programs. The end result is a reduction of the knowledge gap through better integration and distribution of information, improved process performance, automated metric gathering, and quicker identification of problem areas and issues. However, the real proof of the pudding comes through overcoming the user's reluctance to replace familiar, seasoned processes with new technology ingredients blended with automated procedures in an untested recipe. This paper shares some of the team's observations that led to better implementation techniques, as well as an IS0 9001 Best Practices citation. This project has provided a unique opportunity to advance NASA's competency in new technologies, as well as to strategically implement them within an organizational structure, while wetting the appetite for continued improvements in mission management.

Mitchell, Andrew E.↗
NASA NTRS2004

Practical Pocket PC Application w/Biometric Security

I work in the Flight Software Engineering Branch, where we provide design and development of embedded real-time software applications for flight and supporting ground systems to support the NASA Aeronautics and Space Programs. In addition, this branch evaluates, develops and implements new technologies for embedded real-time systems, and maintains a laboratory for applications of embedded technology. The majority of microchips that are used in modern society have been programmed using embedded technology. These small chips can be found in microwaves, calculators, home security systems, cell phones and more. My assignment this summer entails working with an iPAQ HP 5500 Pocket PC. This top-of-the-line hand-held device is one of the first mobile PC's to introduce biometric security capabilities. Biometric security, in this case a fingerprint authentication system, is on the edge of technology as far as securing information. The benefits of fingerprint authentication are enormous. The most significant of them are that it is extremely difficult to reproduce someone else's fingerprint, and it is equally difficult to lose or forget your own fingerprint as opposed to a password or pin number. One of my goals for this summer is to integrate this technology with another Pocket PC application. The second task for the summer is to develop a simple application that provides an Astronaut EVA (Extravehicular Activity) Log Book capability. The Astronaut EVA Log Book is what an astronaut would use to report the status of field missions, crew physical health, successes, future plans, etc. My goal is to develop a user interface into which these data fields can be entered and stored. The applications that I am developing are created using eMbedded Visual C++ 4.0 with the Pocket PC 2003 Software Development Kit provided by Microsoft.

Logan, Julian↗
NASA NTRS2005

Documentation: No Substitute for Communication

SO WHAT IS AN RFI? IT WAS ONE OF THE FIRST THINGS I learned about back when I started my project management career with my first large construction firm. I learned how to use these forms as a convenient and effective means of documenting the many legitimate clarifications needed on a major project. However, like most other young engineers, I also learned to use the RFI as a weapon in the ongoing battle between owners. or their designer and the construction contractors. Recently, our project team has done a few simple things to greatly reduce the waste and frustration that comes from this type of battle. The RFI form can be a great tool if used properly, and I certainly don t recommend that they be eliminated entirely. The RFI form was created to document the many clarifications that are commonly required on projects. Typically, the contractor uses the top half of the form to clarify-or request permission to vary from-the contract documents. The bottom half of the form is used to record the answer. But this seemingly simple process is plagued by a number of problems. From the contractor s perspective, RFIs are needed to secure information that should have been in the contract documents in the first place. The missing information keeps their crews from working effectively, and it makes hitting already demanding cost and schedule targets even more difficult. Owners, or their design firms, often view the RFI as a means of harassment. Both sides of the issue have legitimate complaints, and both sides cause most of their own pain.

Strickland, John↗
NASA NTRS2010

Deliberate Satellite Fragmentations and their Effects on the Long-Term Space Environment

Since 1964 at least 56 spacecraft and two launch vehicle upper stages have been deliberately fragmented while in Earth orbit. Many of these events have had no long-lasting effects on the near-Earth space environment, but one represents the most devastating satellite breakup in history that will pose hazards to operational spacecraft in low Earth orbit for decades to come. International space debris mitigation guidelines now call for avoiding the creation of long-lived debris from intentional satellite fragmentations. This paper summarizes the reasons for and environmental consequences of deliberate satellite fragmentations. Contrary to popular belief, only one in five deliberate fragmentations have been related to the testing of anti-satellite weapon systems, for which only one such test has occurred during the past 25 years. Other reasons for deliberate satellite fragmentations range from engineering tests to protecting national security information. Whereas the majority of deliberate satellite fragmentations have occurred in low Earth orbits, some have involved spacecraft in highly elliptical orbits. The former Soviet Union and the current Russian Federation have been responsible for 90% of all identified deliberate on-orbit satellite fragmentations.

Johnson, N. L.↗
NASA NTRS2004

Managing an Archive of Images

The SSC Multimedia Archive is an automated electronic system to manage images, acquired both by film and digital cameras, for the Public Affairs Office (PAO) at Stennis Space Center (SSC). Previously, the image archive was based on film photography and utilized a manual system that, by today s standards, had become inefficient and expensive. Now, the SSC Multimedia Archive, based on a server at SSC, contains both catalogs and images for pictures taken both digitally and with a traditional, film-based camera, along with metadata about each image. After a "shoot," a photographer downloads the images into the database. Members of the PAO can use a Web-based application to search, view and retrieve images, approve images for publication, and view and edit metadata associated with the images. Approved images are archived and cross-referenced with appropriate descriptions and information. Security is provided by allowing administrators to explicitly grant access privileges to personnel to only access components of the system that they need to (i.e., allow only photographers to upload images, only PAO designated employees may approve images).

Andres, Vince↗
NASA NTRSDate not supplied

Gateway Implementation of Cybersecurity Requirements

Cyber threats are a constant present-day reality for any type of business -- Space exploration is not excluded from these threats either. The Gateway Program is one of NASA’s latest initiatives that extend space exploration beyond low earth orbit. Gateway allows for NASA to prove technologies and mature systems necessary to live and work on another celestial body before embarking on multi-year missions to Mars. The Gateway is a small, human-tended space station in orbit around the Moon. With the increased autonomy, distance and criticality of systems, cybersecurity is one of the critical subsystems that touches and integrates with most if not all subsystems of the Gateway. Building a gateway to the lunar orbit is no simple task. In this presentation, we outline an approach that the Gateway team adopted in creating a cyber safe and robust vehicle to support operations and assure protection of the critical functions. Gateway Program is required to implement National Institute of Standards and Technology (NIST) guidelines to adhere to the Federal Information Security Modernization Act (FISMA). NIST provides a framework for managing and controlling cybersecurity risks by defining cybersecurity controls and methodologies for implementation. The NIST framework is based upon the system, data within the system, integrations with external systems, and risk assessments to determine impacts for each of those systems. The goals and objectives are to identify appropriate security controls that fulfill and map to the NIST 800-53 framework. The implementation process involves developing an organizational understanding to manage cybersecurity risk to systems, people, assets, data, and capabilities. NIST Security controls are interpreted and defined within the Gateway vehicle requirements subsystems specifications. This paper details the approach, implementation, and challenges faced during the development and design phases to address cyber threats during the Gateway vehicle operations.

Svetlana Hanson↗
NASA NTRSDate not supplied

Gateway Implementation of Cybersecurity Requirements

Cybersecurity threats are a constant present-day reality for any type of business -- Space exploration is not excluded from these threats either. The Gateway Program is one of NASA’s latest initiatives that extend space exploration beyond low earth orbit. Gateway allows for NASA to prove technologies and mature systems necessary to live and work on another celestial body before embarking on multi-year missions to Mars. The Gateway is a small, human-tended space station in orbit around the Moon. With the increased autonomy, distance and criticality of systems, cybersecurity is a critical discipline that touches and integrates with most if not all subsystems of the Gateway. Building a gateway to the lunar orbit is no simple task. In this presentation, we outline an approach that the Gateway team adopted in creating a cyber safe and robust vehicle to support operations and assure protection of the critical functions. Gateway Program is required to implement National Institute of Standards and Technology (NIST) guidelines to adhere to the Federal Information Security Modernization Act (FISMA). NIST provides a framework for managing and controlling cybersecurity risks by defining cybersecurity controls and methodologies for implementation. The NIST framework is based upon the system, data within the system, integrations with external systems, and risk assessments to determine impacts for each of those systems. The goals and objectives are to identify appropriate security controls that fulfil and map to the NIST 800-53 framework. The implementation process involves developing an organizational understanding to manage cybersecurity risk to systems, people, assets, data, and capabilities. NIST Security controls are interpreted and defined within the Gateway vehicle requirements subsystems specifications. This paper details the approach, implementation, and challenges faced during the development and design phases to address cyber threats during the Gateway vehicle operations.

Cybersecurity↗
DOE OSTI2011

Management of Control System Information SecurityI: Control System Patch Management

The use of information technologies in control systems poses additional potential threats due to the frequent disclosure of software vulnerabilities. The management of information security involves a series of policy-making on the vulnerability discovery, disclosure, patch development and patching. In this paper, we use a system approach to devise a model to understand the interdependencies of these decision processes. In more details, we establish a theoretical framework for making patching decision for control systems, taking into account the requirement of functionability of control systems. We illustrate our results with numerical simulations and show that the optimal operation period of control systems given the currently estimated attack rate is roughly around a half a month.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2013

A Mathematical Framework for the Analysis of Cyber-Resilient Control Systems

The increasingly recognized vulnerability of industrial control systems to cyber-attacks has inspired a considerable amount of research into techniques for cyber-resilient control systems. The majority of this effort involves the application of well known information security (IT) techniques to control system networks. While these efforts are important to protect the control systems that operate critical infrastructure, they are never perfectly effective. Little research has focused on the design of closed-loop dynamics that are resilient to cyber-attack. The majority of control system protection measures are concerned with how to prevent unauthorized access and protect data integrity. We believe that the ability to analyze how an attacker can effect the closed loop dynamics of a control system configuration once they have access is just as important to the overall security of a control system. To begin to analyze this problem, consistent mathematical definitions of concepts within resilient control need to be established so that a mathematical analysis of the vulnerabilities and resiliencies of a particular control system design methodology and configuration can be made. In this paper, we propose rigorous definitions for state awareness, operational normalcy, and resiliency as they relate to control systems. We will also discuss some mathematical consequences that arise from the proposed definitions. The goal is to begin to develop a mathematical framework and testable conditions for resiliency that can be used to build a sound theoretical foundation for resilient control research.

Control Theory↗
DOE OSTI2013

Efficient Aho-Corasick String Matching on Emerging Multicore Architectures

String matching algorithms are critical to several scientific fields. Beside text processing and databases, emerging applications such as DNA protein sequence analysis, data mining, information security software, antivirus, ma- chine learning, all exploit string matching algorithms [3]. All these applica- tions usually process large quantity of textual data, require high performance and/or predictable execution times. Among all the string matching algorithms, one of the most studied, especially for text processing and security applica- tions, is the Aho-Corasick algorithm. 1 2 Book title goes here Aho-Corasick is an exact, multi-pattern string matching algorithm which performs the search in a time linearly proportional to the length of the input text independently from pattern set size. However, depending on the imple- mentation, when the number of patterns increase, the memory occupation may raise drastically. In turn, this can lead to significant variability in the performance, due to the memory access times and the caching effects. This is a significant concern for many mission critical applications and modern high performance architectures. For example, security applications such as Network Intrusion Detection Systems (NIDS), must be able to scan network traffic against very large dictionaries in real time. Modern Ethernet links reach up to 10 Gbps, and malicious threats are already well over 1 million, and expo- nentially growing [28]. When performing the search, a NIDS should not slow down the network, or let network packets pass unchecked. Nevertheless, on the current state-of-the-art cache based processors, there may be a large per- formance variability when dealing with big dictionaries and inputs that have different frequencies of matching patterns. In particular, when few patterns are matched and they are all in the cache, the procedure is fast. Instead, when they are not in the cache, often because many patterns are matched and the caches are continuously thrashed, they should be retrieved from the system memory and the procedure is slowed down by the increased latency. Efficient implementations of string matching algorithms have been the fo- cus of several works, targeting Field Programmable Gate Arrays [4, 25, 15, 5], highly multi-threaded solutions like the Cray XMT [34], multicore proces- sors [19] or heterogeneous processors like the Cell Broadband Engine [35, 22]. Recently, several researchers have also started to investigate the use Graphic Processing Units (GPUs) for string matching algorithms in security applica- tions [20, 10, 32, 33]. Most of these approaches mainly focus on reaching high peak performance, or try to optimize the memory occupation, rather than looking at performance stability. However, hardware solutions supports only small dictionary sizes due to lack of memory and are difficult to customize, while platforms such as the Cell/B.E. are very complex to program.

Tumeo, Antonino↗
DOE OSTI2019

Enhancing Research Reactor Safeguards Through the Use of Mailbox Declarations

There are historic examples in several States of research reactors being misused to produce undeclared nuclear material. However, misuse of a State’s research reactor has typically only been discovered after further investigation into the State’s non-compliance related to other undeclared activities. Light water research reactors are typically designed with sample irradiation ports, where the introduction of fertile material can illicitly produce fissile material. Additionally, some light water reactors continue to be fueled by highly enriched uranium, which is a more significant safeguards concern by the International Atomic Energy Agency (IAEA). Heavy water and graphite reactors can be used for illicit plutonium production, which is of particular proliferation concern. Because research reactors are designed for flexible operations and small research reactors are less frequently inspected by the IAEA than other nuclear facilities (depending on power and fuel type, it could several years between inspections), the likelihood of timely detection by the IAEA of misuse of the research reactor is low. During a 2013 workshop on safeguarding research reactors, the United States, France, and the United Kingdom made recommendations to the IAEA on how safeguards could be strengthened for such facilities. One of the recommendations was to assess the use of “mailbox” declarations coupled with short notice random inspections or unannounced inspections by the IAEA at research reactors. An electronic mailbox declaration refers to the use of a secure information repository into which an operator submits operating reports. The near real time submittal of information enables the IAEA to better implement randomized short notice inspections. These mailboxes are not used for collecting and submitting State reports to the IAEA, but for collecting and transmitting operator data. The use of mailboxes, in conjunction with short notice random inspections, is in routine use for some other facility types. This paper assesses the potential for the practical application of mailbox declarations for various research reactor types and how the approach could be effectively used. Potential diversion scenarios are described and operator data records are discussed in connection to mailbox declarations, including discussion of how the data could indicate research reactor misuse.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
DOE OSTI2023

Autonomous Energy Systems Functional Interoperability

Functional Interoperability is the capability of two or more networks, systems, devices, applications, or components to externally exchange and readily use information securely and effectively in order to achieve a stated objective. Our proposition is that NREL's ARIES capability is ideal to evaluate functional interoperability by defining use case (objective) and scenarios, by integrating systems, devices, and applications in a realistic laboratory environment, and by simulating scenarios.

ARIES↗
DOE OSTI2017

Development of a new IEC Standard on cybersecurity controls for I and C in Nuclear Power Plants - IEC 63096 - 158

Standards are promoting the enhancement of cybersecurity in Nuclear Power Plants (NPP). Standardizing processes and procedures are also crucial to achieve successful international collaboration. Many information security standards were developed in recent years; however, not many of them could be directly applied to NPPs. This paper provides an overview of the development of a new cybersecurity standard dealing with cybersecurity controls for nuclear power plants around the world. For I and C systems in NPPs, the new IEC 63096 standard targeted for issue in 2019, focuses specifically on the selection and application of cybersecurity controls from the included security controls catalogue. The role of selected and applied cybersecurity controls is to prevent, detect and react to digital attacks against computer-based I and C systems. This standard applies to the I and C of new nuclear power plants and to the I and C modernization in existing plants. It is being prepared and based on IEC 62645 , ISO/IEC 27000 series , IAEA , and country specific guidance in this expanding the technical and the security focus area. The Standard is intended to be used by designers and operators of NPPs (utilities), systems evaluators, vendors and subcontractors, and by licensors. While the development of international standards is essential it is also a lengthy process, taking multiple years. Especially with regard to cybersecurity, all involved stakeholders have to collaborate. (authors)

22 GENERAL STUDIES OF NUCLEAR REACTORS↗