2022_004_001_889225.pdf (898.79 kB)
Download file

Acquisition Security Framework (ASF): Managing Systems Cybersecurity Risk

Download (898.79 kB)
report
posted on 11.11.2022, 21:46 authored by Christopher AlbertsChristopher Alberts, Michael BandorMichael Bandor, Charles WallenCharles Wallen, Carol WoodyCarol Woody

Supply chain cyber risks stem from many organizational dependencies,  including processing, transmitting, and storing data; information  technology; and communications technology. These risks are broad,  significant, and growing as outsourcing options expand. Important  mission capabilities can be undermined by an adversary’s cyber attack on  the organization’s contracted third parties, even when the organization  does not explicitly contract for technology. Virtually all products and  services an organization acquires are supported by or integrate with  information technology that includes third-party components/services.  Practices critical to monitoring and managing these risks can be  scattered across the organization, resulting in inconsistencies, gaps,  and slow response to disruptions. The Acquisition Security Framework  (ASF) contains leading practices that support pro-grams  acquiring/building a secure, resilient software-reliant system to manage  these risks. It defines the organizational roles that must effectively  collaborate to engineer systematic resilience processes to avoid gaps  and inconsistencies. It also establishes how an organization should  ensure it has effective supply chain risk management that supports its  mission and objectives. The ASF contains proven and effective goals and  leading practices, and it is consistent with supply chain risk  management guide-lines from the International Organization for  Standardization (ISO), National Institute of Standards and Technology  (NIST), and Department of Homeland Security (DHS). 

History

Publisher Statement

This material is based upon work funded and supported by the Department of Defense under Contract No. FA8702-15-D-0002 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The view, opinions, and/or findings contained in this material are those of the author(s) and should not be construed as an official Government position, policy, or decision, unless designated by other documentation. References herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by Carnegie Mellon University or its Software Engineering Institute. This report was prepared for the SEI Administrative Agent AFLCMC/AZS 5 Eglin Street Hanscom AFB, MA 01731-2100. NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN "AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. [DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribution. Please see Copyright notice for non-US Government use and distribution.

Copyright Statement

Copyright 2022 Carnegie Mellon University.

Usage metrics

Exports