Search NASA⌕ Search

SEARCH · Search NASA

Results for “network security analysis”

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.

513 records · Page 29

Resilient U.S. Land Ports of Entry

The continued operation of Land Ports of Entry (LPOE), managed by the Customs and Border Protection (CBP) and General Services Administration% is vital to the U.S. economy and security. Border faculties are included in the Department of Homeland Security (DHS) Government Facilities Sector2, one of the 16 critical infrastructures "whose assets, systems, and networks, whether physical or virtual, are considered so vital to the United States that their incapacitation or destruction would have a debilitating effect on security, national economic security, national public health or safety, or any combination thereof.'" Specifically, disruptions to the flow of border crossing traffic, in the form of closures or increased border crossing wait times, impact the economy and security of all countries involved. This paper describes a process for analyzing and improving the resilience of U.S. Land Ports of Entry. For LPOE, the team believes that energy resilience is the primary objective due to the complete reliance on the e-manifest system and the increasing use of Multi-Energy Portals (MEPs). Emanifests are part of CPB's Automated Commercial Environment (ACE). They document several key pieces of information about cargo vehicles wishing to cross the border into the United States and are submitted before arriving at the port. Vehicles can be flagged for more invasive inspection based on the content of the e-manifest. MEPs are a non-intrusive inspection (NII) technology used to scan the contents of the cargo. Together MEPs and ACE serve an important role in aiding CBP with their mission to protect "the public from dangerous people and materials", and "enabling legitimate trade and travel.'" To analyze resilience of a port, the team would need to understand the port's current energy usage, which systems depend on energy and what backup systems exist, and any emergency operation plans that dictate how systems are operated in the event of a power outage. The team would also need to determine the design basis threats (DBTs) for the LPOE which could include natural disasters, manmade events, and accidents. The magnitudes of the DBTs are calculated and are then translated to expected impacts on the infrastructure and systems at the port. With this information gathered, existing LPOE models developed here at Sandia National Laboratories could be extended to support decisions about resilience. Current models are implemented in FlexSim, a 3rd party discrete event simulator. FlexSim provides 3-D visuals of physical layout that can reveal valuable insights, allows input to be variable (e.g. time it takes to interact with the CBP officer at primary inspection can vary) so that a whole range of possibilities can be captured in the results, and can be used to collect user-defined output metrics. Current LPOE models focus on cargo vehicle traffic, and process changes caused by the installation of new drive-through MEPs. Extending them to address resilience questions would require the addition of key pieces of information learned during the resilience analysis including critical systems, failure rates, and process changes for when failures occur. The primary output metric for current models is border crossing wait time. Additional metrics would also be added to the model to gain a more complete understanding of impacts related to resilience, for example, MEP scan rate. Once complete, the model could be used to analyze the effectiveness of mitigation strategies representing some future state.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

Corridor Design and Analysis for UAM Operations

The Urban Air Mobility (UAM) concept is a part of Advanced Air Mobility (AAM), a joint initiative between the Federal Aviation Administration (FAA), NASA, and industry to develop an air transportation system that uses new electric (i.e., green) air vehicles in geographical areas previously underserved by traditional aviation. Market forecast studies predict that there will be demand for alternate modes of air transportation using electric Vertical Take-off and Landing aircraft. UAM expands transportation networks by introducing short flights to move people and goods around metropolitan areas​. UAM is expected to improve mobility for the public, decongest road traffic, reduce trip time, and decrease strain on existing public transportation networks. Various challenges exist to make the introduction of UAM operations successful in the U.S. National Airspace System (NAS). These include but are not limited to integration with existing airports and airspace, provision of air traffic services (e.g., separation), vehicle design and certification, and community acceptance. The focus of this paper is on integration of UAM operations into the NAS via introduction of new airspace structures. UAM will operate within a regulatory, operational, and technical environment that is incorporated into the NAS​. As per the UAM Concept of Operations (ConOps), the FAA retains regulatory authority and is responsible for establishing operational parameters and maintaining oversight. The FAA’s UAM ConOps describes flights at low altitudes (below 5,000 ft) with minimal disruption to established conventional aircraft traffic and limited voice interactions with the Air Traffic Control (ATC). Early stages of UAM may use existing procedures to safely integrate UAM with conventional flights. This would involve flying under Part 91 Visual Flight Rules (VFR) and using voice for communications. The initial UAM ecosystem will utilize the current infrastructure such as routes, helipads, and ATC services, where practicable. ​A NASA study explored the use of existing helicopter routes in Dallas Fort Worth (DFW) airspace for initial UAM operations with a Letter of Agreement (LOA) that included procedures to request a Class B (controlled airspace) clearance. The research showed that the chosen approach was feasible for near-term, low-demand UAM traffic, but was not scalable. The growth of operations in today’s aviation system has resulted in airspace reorganization and procedures to ensure safety and efficiency as traffic rates increase. One proposed operating innovation that can help with the scalability of UAM is establishing routes and corridors. This may look similar to the Area Navigation (RNAV) procedures used today to streamline operations into busy airports. However, instead of FAA automation systems and ATC managing the flow of traffic, some UAM concepts envision a third-party service provider performing this role as part of the Provider of Services for UAM (PSU) network. The FAA’s UAM ConOps posits that new airspace structures such as UAM corridors include the following design criteria: 1) Minimal impact on existing NAS operations, 2) no or minimal additional ATC services, 3) public interest considerations such as noise, safety, and security, and 4) customer needs. The airspace available in urban environments is limited by the height of buildings, the effect of weather including wind gusts, privacy needs, and a clearance envelope. The new airspace structure would need to be designed around large airports and urban areas where the initial market demand is likely to exist. NASA has started evaluating airspace in the Dallas Fort Worth area to design new airspace structures, keeping the first two design criteria in mind. It is assumed that there will be an on-board pilot-in-command, and the flights will operate under VFR in Visual Meteorological Conditions. Corridors will be required in controlled airspace, whereas UAM operations can fly in uncontrolled Class G and E airspace using current day rules. Keeler et. al identified factors and heuristics for development of routes for UAM operations for integration with airspace close to large airports such as Dallas Fort Worth and Dallas Love Field. This paper describes the heuristics applied to define the corridors, analyzes them with respect to legacy traffic and presents key results.

Urban Air Mobility↗

Enhancing Cloud Cybersecurity: Prescriptive Controls for Operational Technology

This whitepaper provides strategic insights and recommendations into security cloud-based solutions for electric utilities, encompassing operational technology (OT), virtual power plants (VPP), distributed energy resources (DERs), applications, networks, and data storage as they transition to and leverage cloud infrastructure through managed service providers (MSPs) and cloud service providers (CSPs). Principles derived from established frameworks serve as a foundation for best practices across cybersecurity projects and remove the constraints of settling on a single framework. For organizations that prefer not to integrate a specific framework altogether, elements of the proposed approach could be adopted or tailored to best fit defined requirements and expected functionalities. The Cirrus assessment, a utility cloud feasibility tool, and the roadmap it provides serve as a precursor to this paper, which seeks to be a valuable resource for defining next steps following cloud technology integration feasibility appraisal. With its comprehensive approach to adoption, the Cirrus framework offers strategic guidance on responsibly preparing for or deploying a utility cloud solution. The previously published whitepaper, “Use Case-Informed Framework for Utility Cloud Migration,” details the guiding strategy, research, and deployment of cloud solutions within electric and interconnected grid systems. Before implementing the controls suggested in this document, it is recommended that stakeholders complete Cirrus's cloud integration assessment and pair the results with their unique cybersecurity controls to form a comprehensive cloud-based utility cybersecurity plan. The Cirrus outcome will consider a series of future architectures for the grid before and after the energy transition and evaluate the arguments for and against cloud applications for each electric and interconnected grid layer. This document is a companion to the original whitepaper, "Use Case-Informed Framework for Utility Cloud Migration" to further identify and recommend security controls based on Cirrus’s cloud integration assessment output. The following whitepaper outlines the cybersecurity controls that secure cloud-service models pertinent to the electric sector using the predefined categories identify, protect, detect, and respond and recover. The objective is to outline prescriptive security controls based on the type of architecture and data stored in the cloud. The focus includes dissecting the shared responsibility model and elucidating what on-premises Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) entail. A pivotal consideration in this context is allocating responsibility for foundational cybersecurity aspects—having used Cirrus for the cloud integration assessment. The ensuing controls detailed herein also represent a checklist of controls necessary for a secure cloud transition, equipping utilities with the knowledge to navigate this digital transformation with confidence and strategic foresight in a safe and responsible manner.

42 ENGINEERING↗

Geomechanical Framework for Secure CO 2 Storage in Fractured Reservoirs and Caprocks for Sedimentary Basins in theMidwest United States

This report presents final technical results for the project Geomechanical Framework for Secure CO 2 Storage in Fractured Reservoirs and Caprocks for Sedimentary Basins in the Midwest United States (DE-FE0023330). The project was a three-year effort consisting of seven technical tasks focused on defining geomechanical factors for CO 2 storage applications in deep saline rock formations in Ohio and the Midwest United States, because geomechancial issues have been identified as a significant risk factor for large-scale CO 2 storage applications. A basin-scale stress-strain analysis was completed to describe the geomechanical setting for rock formations of Ordovician-Cambrian age in Ohio and adjacent areas of the Midwest United States in relation to geologic CO 2 storage applications. The tectonic setting, stress orientation-magnitude, and geomechanical and petrophysical parameters for CO 2 storage zones and caprocks in the region were cataloged. Ten geophysical image logs were analyzed for natural fractures, borehole breakouts, and drilling-induced fractures. The logs indicated mostly less than 10 fractures per 100 vertical feet in the borehole, with mostly N65E principal stress orientation through the section. Geophysical image logs and other logs were obtained for three wells located near the sites where specific models were developed for geomechanical simulations: Arches site in Boone County, Kentucky; Northern Appalachian Basin site in Chautauqua County, New York; and E-Central Appalachian Basin site in Tuscarawas County, Ohio. For these three wells, 9,700 feet of image logs were processed and interpreted to provide a systematic review of the distribution within each well of natural fractures, wellbore breakouts, faults, and drilling induced fractures. There were many borehole breakouts and drilling-induced tensile fractures but few natural fractures. Concentrated fractures were present at the Rome-basal sandstone and basal sandstone-Precambrian contacts at the Arches and East-Central Appalachian Basin sites. Geophysical logs were utilized to develop local-scale geologic models by determining geomechanical and petrophysical parameters within the geologic formations. These data were ported to coupled fluid-flow and reservoir geomechanics multi-phase CO 2 injection simulations. The models were developed to emphasize the geomechanical layers within the CO 2 storage zones and caprocks. A series of simulations were completed for each site to evaluate whether commercial-scale CO 2 could be safely injected into each site, given site-specific geologic and geomechanical controls. This involved analyzing the simulation results for the integrity of the caprock, intermediate, and reservoir zones, as well quantifying the areal uplift at the surface. Simulation results were also examined to ensure that the stress-stress perturbations were isolated within the subsurface, and that there was only limited upward migration of the CO 2 . Simulations showed capacity to inject more than 10 million metric tons of CO 2 in a single well at the Arches and East Central Appalachian Basin sites without excessive geomechanical risks. Low-permeability rock layers at the Northern Appalachian Basin study area well resulted in very low CO 2 injection capacity. Fracture models developed for the sites suggests that the sites have sparse fracture network in the deeper Cambrian rocks. However, there were indicators in image logs of a moderate fracture matrix in the Rose Run Sandstone at the Northern Appalachian Basin site. Dual permeability fracture matrix simulations suggest the much higher injection rates may be feasible in the fractured interval. Guidance was developed for geomechanical site characterization in the areas of geophysical logging, rock core testing, well testing, and site monitoring. The guidance demonstrates that there is a suitable array of options for addressing geomechanical issues at CO 2 storage sites. Finally, a review of Marcellus and Utica-Point Pleasant shale gas wells and CO 2 storage intervals indicates that these items are vertically separated, except for the Oriskany sandstone and Marcellus wells in southwest Pennsylvania and northern West Virginia. Together, project results present a more realistic portrayal of geomechanical risk factors related to CO 2 storage for existing and future coal-fired power plants in Ohio.

58 GEOSCIENCES↗

Opportunities and challenges for structural health monitoring of radioactive waste systems and structures

Radioactive waste systems and structures (RWSS) are safety-critical facilities in need of monitoring over prolonged periods of time. Structural health monitoring (SHM) is an emerging technology that aims at monitoring the state of a structure through the use of networks of permanently mounted sensors. SHM technologies have been developed primarily within the aerospace and civil engineering communities. This paper addresses the issue of transitioning the SHM concept to the monitoring of RWSS and evaluates the opportunities and challenges associated with this process. Guided wave SHM technologies utilizing structurally-mounted piezoelectric wafer active sensors (PWAS) have a wide range of applications based on both propagating-wave and standing-wave methodologies. Hence, opportunities exist for transitioning these SHM technologies into RWSS monitoring. However, there exist certain special operational conditions specific to RWSS such as: radiation field, caustic environments, marine environments, and chemical, mechanical and thermal stressors. In order to address the high discharge of used nuclear fuel (UNF) and the limited space in the storage pools the U.S. the Department of Energy (DOE) has adopted a 'Strategy for the Management and Disposal of Used Nuclear Fuel and High-Level Radioactive Waste' (January 2013). This strategy endorses the key principles that underpin the Blue Ribbon Commission's on America's Nuclear Future recommendations to develop a sustainable program for deploying an integrated system capable of transporting, storing, and disposing of UNF and high-level radioactive waste from civilian nuclear power generation, defense, national security, and other activities. This will require research to develop monitoring, diagnosis, and prognosis tools that can aid to establish a strong technical basis for extended storage and transportation of UNF. Monitoring of such structures is critical for assuring the safety and security of the nation's spent nuclear fuel until a national policy for closure of the nuclear fuel cycle is defined and implemented. In addition, such tools can provide invaluable and timely information for verification of the predicted mechanical performance of RWSS (e.g. concrete or steel barriers) during off-normal occurrence and accident events such as the tsunami and earthquake event that affected Fukushima Daiichi nuclear power plant. The ability to verify the conditions, health, and degradation behavior of RWSS over time by applying nondestructive testing (NDT) as well as development of nondestructive evaluation (NDE) tools for new degradation processes will become challenging. The paper discusses some of the challenges associated to verification and diagnosis for RWSS and identifies SHM technologies which are more readily available for transitioning into RWSS applications. Fundamental research objectives that should be considered for the transition of SHM technologies (e.g., radiation hardened piezoelectric materials) for RWSS applications are discussed. The paper ends with summary, conclusions, and suggestions for further work. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Proceedings of the 2009 Monitoring Research Review: Ground-Based Nuclear Explosion Monitoring Technologies

These proceedings contain papers prepared for the Monitoring Research Review 2009: Ground -Based Nuclear Explosion Monitoring Technologies, held 21-23 September, 2009 in Tucson, Arizona,. These papers represent the combined research related to ground-based nuclear explosion monitoring funded by the National Nuclear Security Administration (NNSA), Air Force Research Laboratory (AFRL), US Army Space and Missile Defense Command, Comprehensive Test Ban Treaty Organization (CTBTO), and other invited sponsors. The scientific objectives of the research are to improve the United States’ capability to detect, locate, and identify nuclear explosions. The purpose of the meeting is to provide the sponsoring agencies, as well as potential users, an opportunity to review research accomplished during the preceding year and to discuss areas of investigation for the coming year. For the researchers, it provides a forum for the exchange of scientific information toward achieving program goals, and an opportunity to discuss results and future plans. Paper topics include: seismic regionalization and calibration; detection and location of sources; wave propagation from source to receiver; the nature of seismic sources, including mining practices; hydroacoustic, infrasound, and radionuclide methods; on-site inspection; and data processing.

58 GEOSCIENCES↗

Proceedings of the 30th Monitoring Research Review: Ground-Based Nuclear Explosion Monitoring

These proceedings contain papers prepared for the 30th Monitoring Research Review: Ground-Based Nuclear Explosion Monitoring Technologies, held 23-25 September, 2008 in Portsmouth, Virginia. These papers represent the combined research related to ground-based nuclear explosion monitoring funded by the National Nuclear Security Administration (NNSA), Air Force Technical Applications Center (AFTAC), Air Force Research Laboratory (AFRL), US Army Space and Missile Defense Command, Comprehensive Nuclear-Test-Ban Treaty Organization (CTBTO), and other invited sponsors. The scientific objectives of the research are to improve the United States’ capability to detect, locate, and identify nuclear explosions. The purpose of the meeting is to provide the sponsoring agencies, as well as potential users, an opportunity to review research accomplished during the preceding year and to discuss areas of investigation for the coming year. For the researchers, it provides a forum for the exchange of scientific information toward achieving program goals, and an opportunity to discuss results and future plans. Paper topics include: seismic regionalization and calibration; detection and location of sources; wave propagation from source to receiver; the nature of seismic sources, including mining practices; hydroacoustic, infrasound, and radionuclide methods; on-site inspection; and data processing.

58 GEOSCIENCES↗

Remediation Guidance for Major Airports after a Bioterrorist Attack

This document provides general guidelines for airport managers, local officials, and other stakeholders for developing a response and recovery plan for a major airport following the release of a biological warfare agent, with specific guidance for remediation. San Francisco International Airport was selected as the example airport during development of the guidance to illustrate specific details. The spore-forming bacterium Bacillus anthracis was selected as the biological agent of primary concern because it is the most difficult of known bioterrorism agents to inactivate and is considered to be one of the agents most likely to be used as a biological weapon. The focus of the guidance is on cleanup and disposal activities associated with the Characterization, Decontamination, and Clearance Phases that are defined herein. Activities associated with the Notification and First-Response Phases are brieÀy discussed in Appendixes A and B, respectively. In addition to the main text of this Remediation Guidance document and associated appendixes, a data supplement was developed specifically for San Francisco International Airport. Requests for the data supplement must be made directly to the Emergency Planning Operations Division of San Francisco International Airport. This document does not describe public health responses to release of a biological warfare agent. If laboratory analytical results confirm the presence of a biological agent, the responsible public health agency involved in the response will commence appropriate public health actions, such as treatment (CDC 2004) and decontamination of potentially contaminated individuals, distribution of prophylaxis, and medical examinations. See the Centers for Disease Control and Prevention web site for more information on emergency public health responses (http://www.bt.cdc.gov/). Effective communication with the media and the public is an essential component of airport remediation and recovery. Whereas such communication is beyond the scope of this document, many helpful resources are available. (See Section 1.1 for more information.) The concept of operations described in this document for cleanup of a Bacillus anthracis release at a major airport conforms to the National Response Framework (NRF) (DHS 2008) and implementation of the National Incident Management System (NIMS 2004). In most cases, a Unified Command would be formed to direct the cleanup process jointly and to take ultimate responsibility for all cleanup decisions. The Unified Command would likely include the Airport Manager or Airport Emergency Operations Manager, representatives from state and local public health and emergency management agencies, and Federal agencies, such as the U.S. Environmental Protection Agency. The Unified Command and Incident Command Staff would ideally be co-located in an Incident Command Post in an uncontaminated area of the airport. If a release is large or complex, co-location of all key players may not be possible. If a major incident is declared, a Principal Federal Official may be appointed by the Department of Homeland Security to facilitate Federal support to the Unified Command. In some facilities and jurisdictions, additional response plans or procedures (such as BioWatch or other emergency response plans, procedures, or protocols) may govern notification and first response. Facility personnel, responders, and emergency management coordinators should be aware of all applicable plans and procedures and how to implement them. Cleanups following the anthrax attacks of 2001 in the U.S. pre-dated the NRF and NIMS and did not make use of a NIMS Incident Command System as we know it today. Most Incident Commanders for the larger of those cleanups chose to convene a Technical Working Group (TWG) of multi-agency, multi-disciplinary, outside experts to advise in developing sampling and decontamination plans. Most of the Incident Commanders also convened a separate Environmental Clearance Committee (ECC) to independently review pre- and post decontamination sampling data as well as data on decontamination parameters, to evaluate whether the decontamination was effective, and to add credibility regarding a decision that decontaminated areas may be reoccupied. Use of such specialized technical expertise is strongly recommended, although it would now operate within the construct of the NIMS Incident Command System. The TWG, if convened, would act in an advisory capacity to the Environmental Unit within the Planning Section. Likewise, the ECC, if convened, would provide independent peer review of products and recommendations by the Environmental Unit. For maximum impartiality, the ECC could also provide recommendations directly to the Unified Command. Cleanup activities commence with site characterization. The principal goal of characterization is to define the extent of contamination and to gather information needed to design the decontamination approach. Initial sampling data collected by first responders are assessed to approximate the location(s) of contamination. Confirmation of the agent type and viability is obtained from a Laboratory Response Network laboratory. Additional characterization data are collected to determine the extent of contamination and where decontamination actions are needed. Areas suspected of being contaminated are contained and isolated to the degree possible to prevent further movement of an agent to uncontaminated areas or the environment, and to reduce the potential for future exposure from the agent or fumigant, if fumigation is needed. Agent air monitoring in areas adjacent to the contained contamination zones is done to ensure the protection of remediation personnel and to monitor any release from the contained zones. Various sampling approaches are considered. For example, wipe samples can be used to sample hard, nonporous surfaces. Swab samples can be used to sample nooks, crannies, joints, and seams. Appendix I is a template for preparing an incident-specific, operational characterization plan. Upon completion of the characterization plan, an internal review is initiated. Upon approval of the plan by the Unified Command, characterization commences. The Site Safety Officer develops a Health and Safety Plan to ensure that coordinated health and safety measures are in place for all responding personnel. This plan describes physical, chemical, and biological hazards at the site, personal protective equipment, personal decontamination procedures, and emergency procedures to be used by sampling and remediation personnel. An incident-specific Remediation Action Plan is developed, which describes the decontamination methods to be used and other details, including waste disposal. Under NIMS, this overall plan, as well as other plans described below, are implemented through a series of standardized, shorter-term Incident Action Plans, which describe specific activities that will take place during a shift or a day. The template in Appendix J is designed to facilitate preparation of the Remediation Action Plan. If fumigation will be done, a Sampling and Analysis Plan will be needed, as well as an Ambient Air Monitoring Plan, which can be a component of the Remediation Action Plan. These three plans are needed to obtain a crisis exemption from the U.S. Environmental Protection Agency for authorized use of an unregistered sterilant or pesticide during cleanup. If pesticide products become registered for inactivation of B. anthracis in the future, the three plans will likely be required by the product’s labeling, but the plans would no longer be submitted to the U.S. Environmental Protection Agency for approval; rather, the Incident Commander would approve them. If fumigation is used, an Emergency Response Plan is also recommended, although such a plan is not required for a crisis exemption. For some nonpersistent biological warfare agents, natural attenuation may be an adequate decontamination option. In cases where contamination is not extensive or an agent is not persistent, application of surface decontaminants or other methods of medical infection control may be effective. For extensive contamination by persistent agents, such as Bacillus anthracis, fumigation may be necessary. In those cases, the Decontamination Phase commences with source reduction, such as pre-cleaning surfaces to reduce the contaminant load. To expedite cleanup and prevent costs from escalating unnecessarily, a cost–benefit analysis should be incorporated in the decision process related to retention versus disposal of facility items and materials. Certain materials and structural components can be decontaminated for reuse, but it may not be feasible or cost-effective to decontaminate other items. Those items must be pre-treated, packaged (with the package decontaminated externally), and removed for disposal as waste. Site preparation includes sealing openings to prevent leaks and setting up equipment. Decontamination reagents and delivery systems are selected, and pre-testing all systems is done before carrying out chemical treatment(s). The important choice of decontamination technologies depends on characteristics of the agent, the nature and extent of contamination, and other site parameters identified during characterization. Decontamination-related decisions can have a major impact on waste-disposal costs, and it is necessary to develop a disposal plan that identifies a means of disposal, necessary approvals, transportation, and other details. A clearance strategy is developed to ensure that after decontamination, the risk of exposure to residual contamination is negligible. A clearance sampling plan is developed, which sets clearance criteria, specifies how to determine whether the criteria have been met, and describes how and where to collect clearance samples after decontamination. In most cases, clearance sampling includes both surface and aggressive air samples. Appendix K is a clearance plan template that identifies the types of required information. To determine whether the decontaminated area may be reoccupied, the Environmental Unit (and the ECC separately, if one is convened) evaluates the results of clearance samples. For the anthrax incidents to date, and given methods that have been used, cleanup was considered successful only when there was no growth of B. anthracis cultured from any environmental samples taken after decontamination. Other factors that will be considered include the decontamination process parameters (e.g., temperature, relative humidity, decontaminant concentration, and contact time) and the results from post-decontamination culture of biological indicators that may have been used during fumigation or sterilization processes. From such an evaluation the Environmental Unit or ECC, or both, recommend whether the area may be reoccupied, or whether further decontamination is necessary. The UC makes the final decision that a facility is appropriately decontaminated for reoccupancy. The facility owner or responsible public health agency makes the final decision to reopen a decontaminated facility. A theme that is emphasized throughout this document is that many activities can greatly reduce the time required to restore airport operations if those activities are conducted prior to an actual release of biological warfare agent. A summary of specific resources (such as Federal, state, and local agency contacts; contractors; prospective team members; subject-matter experts; laboratory facilities; and other entities) that should be identified in advance by airport officials is provided in each pertinent section of this document, and summary contact lists of such resources are provided in Appendix L. A summary of overall pre-planning actions that should be completed by airport officials is presented at the end of this document.

59 BASIC BIOLOGICAL SCIENCES↗

Review of Enabling Technologies to Facilitate Secure Compute Customization

High performance computing environments are often used for a wide variety of workloads ranging from simulation, data transformation and analysis, and complex workflows to name just a few. These systems may process data for a variety of users, often requiring strong separation between job allocations. There are many challenges to establishing these secure enclaves within the shared infrastructure of high-performance computing (HPC) environments. The isolation mechanisms in the system software are the basic building blocks for enabling secure compute enclaves. There are a variety of approaches and the focus of this report is to review the different virtualization technologies that facilitate the creation of secure compute enclaves. The report reviews current operating system (OS) protection mechanisms and modern virtualization technologies to better understand the performance/isolation properties. We also examine the feasibility of running ``virtualized'' computing resources as non-privileged users, and providing controlled administrative permissions for standard users running within a virtualized context. Our examination includes technologies such as Linux containers (LXC [32], Docker [15]) and full virtualization (KVM [26], Xen [5]). We categorize these different approaches to virtualization into two broad groups: OS-level virtualization and system-level virtualization. The OS-level virtualization uses containers to allow a single OS kernel to be partitioned to create Virtual Environments (VE), e.g., LXC. The resources within the host's kernel are only virtualized in the sense of separate namespaces. In contrast, system-level virtualization uses hypervisors to manage multiple OS kernels and virtualize the physical resources (hardware) to create Virtual Machines (VM), e.g., Xen, KVM. This terminology of VE and VM, detailed in Section 2, is used throughout the report to distinguish between the two different approaches to providing virtualized execution environments. As part of our technology review we analyzed several current virtualization solutions to assess their vulnerabilities. This included a review of common vulnerabilities and exposures (CVEs) for Xen, KVM, LXC and Docker to gauge their susceptibility to different attacks. The complete details are provided in Section 5 on page 33. Based on this review we concluded that system-level virtualization solutions have many more vulnerabilities than OS level virtualization solutions. As such, security mechanisms like sVirt (Section 3.3) should be considered when using system-level virtualization solutions in order to protect the host against exploits. The majority of vulnerabilities related to KVM, LXC, and Docker are in specific regions of the system. Therefore, future "zero day attacks" are likely to be in the same regions, which suggests that protecting these areas can simplify the protection of the host and maintain the isolation between users. The evaluations of virtualization technologies done thus far are discussed in Section 4. This includes experiments with 'user' namespaces in VEs, which provides the ability to isolate user privileges and allow a user to run with different UIDs within the container while mapping them to non-privileged UIDs in the host. We have identified Linux namespaces as a promising mechanism to isolate shared resources, while maintaining good performance. In Section 4.1 we describe our tests with LXC as a non-root user and leveraging namespaces to control UID/GID mappings and support controlled sharing of parallel file-systems. We highlight several of these namespace capabilities in Section 6.2.3. The other evaluations that were performed during this initial phase of work provide baseline performance data for comparing VEs and VMs to purely native execution. In Section 4.2 we performed tests using the High-Performance Computing Conjugate Gradient (HPCCG) benchmark to establish baseline performance for a scientific application when run on the Native (host) machine in contrast with execution under Docker and KVM. Our tests verified prior studies showing roughly 2-4% overheads in application execution time & MFlops when running in hypervisor-base environments (VMs) as compared to near native performance with VEs. For more details, see Figures 4.5 (page 28), 4.6 (page 28), and 4.7 (page 29). Additionally, in Section 4.3 we include network measurements for TCP bandwidth performance over the 10GigE interface in our testbed. The Native and Docker based tests achieved >= ~9Gbits/sec, while the KVM configuration only achieved 2.5Gbits/sec (Table 4.6 on page 32). This may be a configuration issue with our KVM installation, and is a point for further testing as we refine the network settings in the testbed. The initial network tests were done using a bridged networking configuration. The report outline is as follows: - Section 1 introduces the report and clarifies the scope of the proj...

Aderholdt, Ferrol↗