The Acquisition Security Framework (ASF) is a collection of leading practices for building and operating secure and resilient systems across the systems lifecycle. These practices enable programs to evaluate risks and gaps in their processes for acquiring, engineering, and deploying secure systems and to exercise more insight and control over their supply chains. The ASF provides a roadmap for building security/resilience into a system rather than “bolting them on” after deployment. ASF practices promote proactive dialogue across all program and supplier teams, helping to integrate communication channels and facilitate information sharing. The framework helps programs coordinate their management of engineering and supply chain risks across the many components of a system. These risks require ongoing monitoring and management across all phases of the systems lifecycle due to the dynamic nature of the threat environment and the rapid evolution of technologies. The ASF is consistent with cybersecurity engineering, supply chain management, and risk management guidance from the International Organization for Standardization (ISO), National Institute of Standards and Technology (NIST), and Department of Homeland Security (DHS). This report builds on a previous report, Acquisition Security Framework (ASF): Managing Systems Cybersecurity Risk, and includes a full set of ASF practices.
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 2024 Carnegie Mellon University.