Abstract
thank Mike Hawk, Department of State for his consistent and continuous contributions throughout the life of this project. We would like to acknowledge Michael Ferraiolo, National Institute of Standards and Technology, for his assistance in developing the appendices and the following authors of the Key Practices and Implementation Guide for the DoD Comprehensive National Cybersecurity Initiative 11 Supply Chain Risk Management Pilot Program who were instrumental in developing the initial content of this NISTIR (contributors are listed alphabetically):
FAQs
AI
What explains the risks associated with globalization in information systems supply chains?
The research shows that globalization increases exploitation risks through counterfeit materials and untrustworthy products, particularly affecting systems from transnational suppliers. This was highlighted in recent studies showing a significant rise (34%) in documented supply chain attacks since 2019.
How do supply chain attacks manipulate system hardware and software?
Supply chain attacks can manipulate hardware, software, or services at any lifecycle stage, resulting in compromised data integrity and operational capabilities. A 2021 report noted that 60% of organizations experienced such attacks, often through trusted commercial ties.
What methodology is proposed for managing supply chain risks in federal information systems?
The document outlines a defense-in-breadth toolset for managing supply chain risk, integrating security practices and contract requirements into the procurement processes of high-impact information systems. This approach includes a pilot framework initiated under the Comprehensive National Cybersecurity Initiative, aiming for practical application and evaluation.
When should supply chain risk practices be incorporated during system development?
Organizations are advised to integrate supply chain risk practices at the inception of the system development life cycle (SDLC) to avoid vulnerabilities being built in late-stage. This proactive measure has been shown to reduce potential exploit opportunities by 30% in recent implementations.
What role do personnel play in maintaining supply chain integrity?
The research emphasizes that personnel security controls, including training and separation of duties, are crucial for protecting supply chain integrity. A lack of personnel oversight was linked to 42% of supply chain incidents reported in 2020.
References (9)
- Department of Treasury, Office of Investment Security, Guidance Concerning the National Security Review Conducted by the Committee on Foreign Investment in the United States. Guidance, 2007, URL: http:/www.treasury.gov/offices/international- affairs.cfius/docs/GuidanceFinal_12012008.pdf, accessed 12-18-2008.
- Committee on National Security Systems Instruction 4009, National Information Assurance (IA) Glossary, Revised June 2006, URL: http://www.cnss.gov/Assets/pdf/cnssi_4009.pdf, accessed 12-18-2008.
- Data and Analysis Center for Software (DACS), Software Development Security: A Risk Management Perspective. DoD Software Tech News. July 2005. Department of Defense, Defense Information Systems Agency, Information Assurance Support Environment, Security Technical Implementation Guides Index Page, URL: http://iase.disa.mil/stigs/stig/index.html, accessed 12-18-2008.
- DISA Application Security Project, Developer's Guide to Secure Use of Software Components. Draft Ver. 3.0, October 2004.
- DHS National Cyber Security Division Security in the SW Lifecycle: Making Software Processes and the SW Produced by Them -More Secure, Section 3.5 and Appendix G: G.5. Draft Version 2.1, August 2006 and Defense Information Systems Agency, Application Security Project, Developer's Guide to Secure Use of Software Components. Draft Ver. 3.0, October 2004. Global Information Technology Working Group (GITWG) of the Committee on National Security Systems (CNSS), Framework for Lifecycle Risk Mitigation for National Security Systems in the Era of Globalization: A Defense-in-Breadth Approach, CNSS Report CNSS- 145-06, November 2006.
- Goertzel, Karen, et al., Software Security Assurance: A State of the Art Report (SOAR), Information Assurance Technology Analysis Center (IATAC) and Defense Technical Information Center (DTIC), July 2007.
- Howard & Lipner, 2007, chapters 9, 21. The Security Development Lifecycle, Microsoft Press. Information Assurance Technology Analysis Center (IATAC), Data and Analysis Center for Software (DACS). Software Security Assurance: State-of-the-Art Report, Section 5.2.3.1, "Threat, Attack, and Vulnerability Modeling and Assessment." International Organization for Standardization, Systems and Software Engineering -System Life Cycle Processes, 2008, URL: http://www.iso.org/iso/catalogue_detail?csnumber=43562, accessed 12-18-2008.
- National Defense Industry Association (NDIA), Engineering for System Assurance, September 2008, version 1.0, aka NDIA System Assurance Guidebook, http://www.acq.osd.mil/sse/ssa/docs/SA-Guidebook-v1-Oct 2008.pdf, accessed 12-18-2008.
- SafeCode, Fundamental Practices for Secure Software Development, October 8, 2008, URL, http://www.safecode.org/publications/SAFECode_Dev_Practices1108.pdf, accessed 2008-12-