Search NASA⌕ Search

SEARCH · Search NASA

Results for “Vulnerability management”

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 37 records · Page 2

Evaluating Process Effectiveness to Reduce Risk

It is well documented that government agencies do not have the same incentive as the private sector to focus on process effectiveness and continual improvement of those processes. It is also well documented whenever government agencies fail to deliver efficient, effective, consistent, and fair services to the citizens. In spite of the various "reinventing government" and "effectiveness initiatives" of the past decades, and in spite of the efforts on the part of many agencies to improve, government in general still lags behind industry in creating a culture of effective processes and systems. While the tragic events that unfolded recently in Flint, Michigan, teach us that running government "like a business" does not always take the needs of the citizenry into account, there are many lessons and techniques from the private sector that government agencies can use to improve. The incentive to improve, while mandated by various administrations1, needs to come from within the workforce, in order to effectively take root. The best, most effective incentive is to reduce, control or eliminate risk. Government agencies face some of the same risks as the private sector, while some are unique. While ISO 310002 has been around since 2009, risk has taken on increased visibility within the private sector with the advent of the emphasis on risk-based thinking in ISO 9001:20153. The relationship between risk-based thinking and effective processes is simple and direct. Those processes that are well thought out and standardized (i.e. Plan-Do-Check-Act), will have taken into account the applicable policy, statutory, regulatory, safety, quality and technical parameters, which may not occur to someone performing the process with minimal experience or training; and thus protect the employees, the public and the agency from statutory and regulatory violations; delay in providing services; non-delivery of services; harm to public or employee safety and health; cost overruns; breaches in security; loss of confidence in government; failure of publicly funded projects; damage to the environment; ethics violations, and the list goes on; with local, national and even international consequences. The Plan-Do-Check-Act process, also known as the "process approach" can be used at any time to establish and standardize a process, and it can also be used to check periodically for "process creep" (i.e., informal, unauthorized changes that have occurred over time), any necessary updates and improvements. While ISO 9001 compliance is not mandated for all government agencies, if interpreted correctly, it can be useful in establishing a framework and implementing effective management systems and processes.4 Another method that can be used to evaluate effectiveness is the scorecard definitions in Mallory's Process Management Standard5 as a basis for evaluating work on the process level on effective, and continuously improved and improving processes. With processes on the lower end of the scale, agencies are vulnerable to a great many risks, with employees and managers making up many of the rules as they go, leading to the above listed negative results. Without clear guidance for nominal operations, off-nominal situations can, and do, increase the likelihood of chaos. In an increasingly technical environment, with inter-agency communication and collaboration becoming the norm, agencies need to come to grips with the fact that processes can become rapidly outdated, and that the technical community should take on an increased role in the maturation of the agency's processes. Industry has long known that effective processes are also efficient, and process improvement methods such as Kaizen, Lean, Six Sigma, 5S, and mistake proofing lead to increased productivity, improved quality, and decreased cost. Again, government agencies have different concerns, but inefficiencies and mistakes can have dire and wide reaching consequences for the public that they serve. While no one goes to work planning to cause harm, it is up to agencies to establish upper level systems, which make establishment and compliance with processes possible. Again, Mallory provides us with a Systems Management Standard6, similar to the Process Management Standard, with a scale of 0-5 for systems effectiveness and maturity. Deming determined that "eighty-five percent of the reasons for failure are deficiencies in the systems and process rather than the employee. The role of management is to change the process rather than badgering individual employees to do better." 7 It is not just the working level employees who need effective processes, but the mid-and upper level managers as well. A disciplined management culture sets the tone for the employees, aids both routine and off-nominal decision-making, and incorporates risk -based thinking into the systems and processes as a matter of normal activity. Figure 1, illustrates the relationship between ineffective and effective processes and risk, through the use of the "stoplight" colors that are commonly used to show serious situations (red), situations which may be improving or deteriorating depending on trends (yellow), and situations that are under control and continuously improved (green).

Shepherd, Christena C.↗

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↗

Multitasking

Multitasking is endemic in modern life and work: drivers talk on cell phones, office workers type while answering phone calls, students do homework while text messaging, nurses prepare injections while responding to doctor’s calls, and air traffic controllers direct aircraft in one sector while handling additional traffic in another. Whether in daily life or at work, we are constantly bombarded with multiple concurrent demands, and we have all somehow come to believe in the myth that we can, and in fact are expected to, easily address them all - without any repercussions. However, accumulating scientific evidence is now suggesting that multitasking increases the probability of human error. This talk presents a set of NASA studies that characterize concurrent demands in routine airline flight operations, in order to illustrate the ways operational task demands together with the proclivity to manage them all concurrently make human performance in this and in any domain vulnerable to potentially serious errors and to accidents.

multitasking↗

The implementation of fail-operative functions in integrated digital avionics systems

System architectures which incorporate fail operative flight guidance functions within a total integrated avionics complex are described. It is shown that the mixture of flight critical and nonflight critical functions within a common computer complex is an efficient solution to the integration of navigation, guidance, flight control, display, and flight management. Interfacing subsystems retain autonomous capability to avoid vulnerability to total avionics system shutdown as a result of only a few failures.

Osoer, S. S.↗

We Don't Need Any Stinking AFSRB!

Flight Test supports four needs: a) Management approval to proceed; b) Establish a record of accountability; c) Inject expert insight into the risk management process; and d) Mitigate the human factors vulnerabilities associated with small group teaming and project ownership.

Henwood, Barton↗

Eastern Washington Disasters: Integrating NASA Earth Observations to Analyze Spatiotemporal Distributions of Lightning-Caused Wildfires in Eastern Washington

According to the Washington Department of Natural Resources, roughly 36% of large fires in the state since 2010 were caused by lightning. General trends also show a greater increase in the number of lightning-ignited fires over the last three decades. The NASA DEVELOP Eastern Washington Disasters team partnered with The Nature Conservancy’s Washington Chapter to analyze the relationship between lightning strikes and wildfire events in Eastern Washington, with an emphasis on Kittitas and Yakima Counties. Using the International Space Station Lightning Imaging Sensor, the Landsat 5 Thematic Mapper and Landsat 8 Operational Land Imager vegetation moisture index, and Washington Department of Natural Resources historical fire data, the team generated a lightning-caused fire vulnerability index for 2001-2019. Climatology maps of lightning, wildfire, and vegetation moisture of the study area, along with an Esri ArcGIS StoryMap, further communicated project findings. The project results demonstrated that spatiotemporal patterns of lightning-ignited wildfires in Eastern Washington can be useful to inform land management practices and better predict areas that may be more vulnerable to these events.

Disasters↗

Eastern Washington Disasters: Integrating NASA Earth Observations to Analyze Spatiotemporal Distributions of Lightning-Caused Wildfires in Eastern Washington

According to the Washington Department of Natural Resources, roughly 36% of large fires in the statesince 2010 were caused by lightning. General trends also show a greater increase in the number of lightning-ignited fires over the last three decades. The NASA DEVELOP Eastern Washington Disasters team partnered with The Nature Conservancy’s Washington Chapter to analyze the relationship between lightning strikes and wildfire events in Eastern Washington, with an emphasis on Kittitas and Yakima Counties. Using the International Space Station Lightning Imaging Sensor, the Landsat 5 Thematic Mapper and Landsat 8 Operational Land Imager vegetation moisture index, and Washington Department of Natural Resources historical fire data, the team generated a lightning-caused fire vulnerability index for 2001-2019. Climatology maps of lightning, wildfire, and vegetation moisture of the study area, along with an Esri ArcGIS StoryMap, further communicated project findings. The project results demonstrated that spatiotemporal patterns of lightning-ignited wildfires in Eastern Washington can be useful to inform land management practices and better predict areas that may be more vulnerable to these events.

Disasters↗

Keweenaw Bay Water Resources: Turbidity Data Decision Support for Shoreline Assessment and Management in Lake Superior's Keweenaw Bay

Community Concerns: Keweenaw Bay is vulnerable to flooding and erosion, which threaten wetland restoration projects that provide a critical habitat for wildlife and fish. Erosion and flooding threaten the loss of public beaches and shoreline, coastal infrastructure, and impacts to coastal highways, which has driven shoreline armoring projects. Our goals were to first, produce a seasonal turbidity analysis to understand the sediment redistribution patterns in the bay during snow melt and rainy seasons to provide insight into coastal sediment dynamics. KBIC has completed an Environmental Protection Agency (EPA) - funded project titled "Long-Term Coastal Dynamic Collaborative for Tribal Resiliency" which has thus far produced detailed shoreline maps of the area. The NASA DEVELOP project is taking place in between phase 1 and 2 of the EPA-funded project.

Khaim Syed-Raza↗

Security Vulnerability Profiles of Mission Critical Software: Empirical Analysis of Security Related Bug Reports

While some prior research work exists on characteristics of software faults (i.e., bugs) and failures, very little work has been published on analysis of software applications vulnerabilities. This paper aims to contribute towards filling that gap by presenting an empirical investigation of application vulnerabilities. The results are based on data extracted from issue tracking systems of two NASA missions. These data were organized in three datasets: Ground mission IVV issues, Flight mission IVV issues, and Flight mission Developers issues. In each dataset, we identified security related software bugs and classified them in specific vulnerability classes. Then, we created the security vulnerability profiles, i.e., determined where and when the security vulnerabilities were introduced and what were the dominating vulnerabilities classes. Our main findings include: (1) In IVV issues datasets the majority of vulnerabilities were code related and were introduced in the Implementation phase. (2) For all datasets, around 90 of the vulnerabilities were located in two to four subsystems. (3) Out of 21 primary classes, five dominated: Exception Management, Memory Access, Other, Risky Values, and Unused Entities. Together, they contributed from 80 to 90 of vulnerabilities in each dataset.

Goseva-Popstojanova, Katerina↗

Systemic Risk

Systemic risk is the name given to impacts that spread within and across systems and sectors (e.g. ecosystems, health, infrastructure and the food sector) via the movements of people, goods, capital and information within and across boundaries (e.g. regions, countries and continents). The spread of these impacts can lead to potentially existential consequences and system collapse across a range of time horizons. Globalization contributes to systemic risk affecting people worldwide. The impacts of climate change or COVID-19 show how the challenges of addressing systemic risk go beyond conventional risk management and governance. Critical system interdependencies, amplified by underlying vulnerabilities, highlight that there is a growing need to better understand cascading impacts, systemic risks and the possible political (governance) and societal responses. This includes improving our understanding of the root causes of systemic risk, both biophysical and socio-economic, and related information needs. Addressing contemporary challenges in terms of systemic risk requires integrating different systems perspectives and fostering system thinking, while implementing key intergovernmental agendas, such as the Paris Agreement, the Sendai Framework for Disaster Risk Reduction and the Sustainable Development Goals.

systemic risk↗

Selection for optimal crew performance - Relative impact of selection and training

An empirical study supporting Helmreich's (1986) theoretical work on the distinct manner in which training and selection impact crew coordination is presented. Training is capable of changing attitudes, while selection screens for stable personality characteristics. Training appears least effective for leadership, an area strongly influenced by personality. Selection is least effective for influencing attitudes about personal vulnerability to stress, which appear to be trained in resource management programs. Because personality correlates with attitudes before and after training, it is felt that selection may be necessary even with a leadership-oriented training cirriculum.

Chidester, Thomas R.↗

Predicting Fire Season Severity in South America Using Sea Surface Temperature Anomalies

Fires in South America cause forest degradation and contribute to carbon emissions associated with land use change. Here we investigated the relationship between year-to-year changes in satellite-derived estimates of fire activity in South America and sea surface temperature (SST) anomalies. We found that the Oceanic Ni o Index (ONI) was correlated with interannual fire activity in the eastern Amazon whereas the Atlantic Multidecadal Oscillation (AMO) index was more closely linked with fires in the southern and southwestern Amazon. Combining these two climate indices, we developed an empirical model that predicted regional annual fire season severity (FSS) with 3-5 month lead times. Our approach provides the foundation for an early warning system for forecasting the vulnerability of Amazon forests to fires, thus enabling more effective management with benefits for mitigation of greenhouse gas and air pollutant emissions.

Chen, Yang↗

Safety-Critical Partitioned Software Architecture: A Partitioned Software Architecture for Robotic

The flight software on virtually every mission currently managed by JPL has several major flaws that make it vulnerable to potentially fatal software defects. Many of these problems can be addressed by recently developed partitioned operating systems (OS). JPL has avoided adopting a partitioned operating system on its flight missions, primarily because doing so would require significant changes in flight software design, and the risks associated with changes of that magnitude cannot be accepted by an active flight project. The choice of a partitioned OS can have a dramatic effect on the overall system and software architecture, allowing for realization of benefits far beyond the concerns typically associated with the choice of OS. Specifically, we believe that a partitioned operating system, when coupled with an appropriate architecture, can provide a strong infrastructure for developing systems for which reusability, modifiability, testability, and reliability are essential qualities. By adopting a partitioned OS, projects can gain benefits throughout the entire development lifecycle, from requirements and design, all the way to implementation, testing, and operations.

(Avionics Application Standard Software Interface ↗

Forecasting Fire Season Severity in South America Using Sea Surface Temperature Anomalies

Fires in South America cause forest degradation and contribute to carbon emissions associated with land use change. We investigated the relationship between year-to-year changes in fire activity in South America and sea surface temperatures. We found that the Oceanic Ni o Index was correlated with interannual fire activity in the eastern Amazon, whereas the Atlantic Multidecadal Oscillation index was more closely linked with fires in the southern and southwestern Amazon. Combining these two climate indices, we developed an empirical model to forecast regional fire season severity with lead times of 3 to 5 months. Our approach may contribute to the development of an early warning system for anticipating the vulnerability of Amazon forests to fires, thus enabling more effective management with benefits for climate and air quality.

Chen, Yang↗

Dust Hazard Management in the Outer Solar System

Most robotic missions to the outer solar system must grapple with the hazards posed by the dusty rings of the gas giants. Early assessments of these hazards led simply to ring avoidance due to insufficient data and high uncertainties on the dust population present in such rings. Recent approaches, principal among them the Cassini dust hazard management strategy, provide useful results from detailed modeling of spacecraft vulnerabilities and dust hazard regions, which along with the range of mission trajectories are used to to assess the risks posed by each passage through a zone of potential hazard. This paper shows the general approach used to implement the analysis for Cassini, with recommendations for future outer planet missions.

mission hazards↗

Environmental Justice Needs Assessment for Disasters: Assessing the Landscape and Capacity of Organizations & Communities Working Towards Environmental Justice with Potential to Use NASA Earth Observations to Support Equitable Disaster Management and Risk Reduction

Natural disasters pose an increasing risk to communities worldwide. Marginalized populations, in particular, experience compounding vulnerabilities that contribute to unequal burdens of natural hazards as a result of systemic inequality stemming from historical disenfranchisement, disinvestment, and discriminatory policies such as racial redlining. This project connected with community organizations working at the intersection of environmental justice (EJ) and natural disaster management throughout the United States, to assess how NASA DEVELOP can leverage geospatial science to advance EJ efforts. Our team conducted a landscape analysis, which included a literature review, annotated bibliography, and identification of organizations working in EJ and disasters. We engaged EJ organizations in discussions to understand their current resources, challenges, and geospatial needs to inform how DEVELOP and NASA Applied Sciences can support their EJ and disaster work. Findings were compiled in a synthesis report and visualized in an ArcGIS StoryMap to showcase the work of EJ organizations, provide geospatial resources for them to explore, and provide examples of how remote sensing can be utilized in EJ and disasters work. The knowledge gained and end products created support the integration of EJ in future DEVELOP projects, and the expanded use of Earth observations by communities in support of a more just tomorrow.

Julianne Liu↗

Security engineering: systems engineering of security through the adaptation and application of risk management

Information Technology (IT) Security Risk Management is a critical task in the organization, which must protect its resources and data against the loss of confidentiality, integrity, and availability. As systems become more complex and diverse, and more vulnerabilities are discovered while attacks from intrusions and malicious content increase, it is becoming increasingly difficult to manage IT security. This paper describes an approach to address IT security risk through risk management and mitigation in both the institution and in the project life cycle.

security↗

Scalable Asset Discovery, Vulnerability Scanning, and Penetration Testing for Remote Sites and Wireless Spectrums Utilizing an Embedded Linux Plug - PwniPlug and the Raspberry Pi B+ as a Sample Pen Test

All devices attached to the NASA KSC network are subject to security vulnerability scanning and/or penetration testing. In today's changing environment, vulnerable and/or unprotected systems can easily be overlooked. Systems that are not properly managed can become a potential threat to the operational integrity of our systems and networks. This includes all NASA (internal and external) information systems within NASA KSC Internet Protocol (IP) address space, and NASA KSC facilities. The Office of the Chief Information Officer (OCIO) recommends that all NASA Centers and information systems be subject to penetration testing on a regular interval in accordance with the guidelines identified by the National Institute of Standards and Technology (NIST). (ITS-HBK-2810.04-02A) Protecting information and equipment at NASA is an area of increasing concern. In addition to the CPU's on the network; Supervisory, Control and Data Acquisition (SCADA) systems are especially vulnerable because these systems have lacked standards, use embedded controllers with little computational power and informal software, are connected to physical processes, have few operators, and are increasingly also being connected to corporate networks. The scope of work is comprised of several individual components which together build upon previous work by Drew Branch, NASA KSC Intern. The Pwn Plug is the selected COTS (Commercial-Off-The-Shelf) device chosen to test simplification of mandatory IT Security tasks. The device will be utilized to provide services to NASA KSC and enable an assessment of infrastructure soundness and regulatory compliance in an efficient, economical, and business responsive manner. The Pwn Plug is designed as a pen testing appliance which provides a hardware platform that can support commercial penetration testing efforts at significantly reduced costs. The expected outcomes are: 1) External Penetration Testing, 2) Social Engineering, 3) Procedural Documentation, 4) Recommended Remediation Action Plan, 5) System Retest & Remediation Attestation and 6) Final Reports, out briefing and Presentation. Due to physical and material constraints beyond intern and mentor control, the project was redefined as a working pen-test scenario. Limitations of lab availability and tools dictated an academic exercise. This report was developed within the scenario guidelines suggested by the project mentor. The guidelines were to be creative in developing a Pen Test program for a client.

Penetration Testing↗