Date Published: February 6, 2023
Comments Due:
Email Questions to:
Author(s)
Yang Guo (NIST), Ramaswamy Chandramouli (NIST), Lowell Wofford (Amazon.com), Rickey Gregg (HPCMP), Gary Key (HPCMP), Antwan Clark (Laboratory for Physical Sciences), Catherine Hinton (Los Alamos National Laboratory), Andrew Prout (MIT Lincoln Laboratory), Albert Reuther (MIT Lincoln Laboratory), Ryan Adamson (Oak Ridge National Laboratory), Aron Warren (Sandia National Laboratories), Purushotham Bangalore (University of Alabama), Erik Deumens (University of Florida), Csilla Farkas (University of South Carolina)
Announcement
Executive Order 13702 established the National Strategic Computing Initiative (NSCI) to maximize the benefits of high-performance computing (HPC) for economic competitiveness and scientific discovery. Securing HPC systems is challenging due to their size; performance requirements; diverse and complex hardware, software, and applications; varying security requirements; the nature of shared resources; and the continuing evolution of HPC systems.
Draft SP 800-223 provides guidance on standardizing and facilitating the sharing of HPC security postures by introducing a zone-based HPC system reference model that captures common features of HPC systems and serves as a foundation for a system lexicon. The draft also discusses HPC system threat analysis, security postures, challenges, and recommendations.
The public comment period for this initial public draft is open through April 7, 2022. Additional information can be found at the NIST HPC Security Working Group website. A 3rd High-Performance Computing Workshop will be held March 15-16, 2023; see the event page for more details and a registration link.
NOTE: A call for patent claims is included on page ii of this document. For additional information, see the Information Technology Laboratory (ITL) Patent Policy--Inclusion of Patents in ITL Publications.
Security is an essential component of high-performance computing (HPC). HPC systems often differ based on the evolution of their system designs, the applications they run, and the missions they support. An HPC system may also have its own unique security requirements, follow different security guidance, and require tailored security solutions. Their complexity and uniqueness impede the sharing of security solutions and knowledge. This NIST Special Publication aims to standardize and facilitate the information and knowledge-sharing of HPC security using an HPC system reference model and key components as the basics of an HPC system lexicon. This publication also analyzes HPC threats, considers current HPC security postures and challenges, and makes best-practice recommendations.
Security is an essential component of high-performance computing (HPC). HPC systems often differ based on the evolution of their system designs, the applications they run, and the missions they support. An HPC system may also have its own unique security requirements, follow different security...
See full abstract
Security is an essential component of high-performance computing (HPC). HPC systems often differ based on the evolution of their system designs, the applications they run, and the missions they support. An HPC system may also have its own unique security requirements, follow different security guidance, and require tailored security solutions. Their complexity and uniqueness impede the sharing of security solutions and knowledge. This NIST Special Publication aims to standardize and facilitate the information and knowledge-sharing of HPC security using an HPC system reference model and key components as the basics of an HPC system lexicon. This publication also analyzes HPC threats, considers current HPC security postures and challenges, and makes best-practice recommendations.
Hide full abstract
Keywords
high-performance computing (HPC); HPC security; HPC reference model; security guidance; HPC threat analysis; HPC security posture
Control Families
None selected
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
