DI-MGMT-81826D
F/A-18 and EA-18 Aircraft / System Program Protection Implementation Plan
The DID defines requirements for the Contractor's F/A-18 and EA-18G Aircraft / System Program Protection Implementation Plan, covering program protection and OPSEC activities under the contract.
Approval DateJune 12, 2018
AMSC NumberN9951
Preparing ActivityAS
Project NumberMGMT-2018-038
OPR—
DTIC Applicable—
GIDEP ApplicableYes
Limitation—
Applicable Forms—
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantYes
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Application & Interrelationship
—
Use & Relationship
The Contractors F/A-18 (All Series) and EA-18G Program Protection Implementation shall be defined within the F/A-18 (All Series) and EA-18 Aircraft / System Contractors Program Protection Implementation Plan (PPIP) which is a result of the program protection requirements set forth in the DD-254, Statement of Work (SOW), DoD Contract, the Government's F/A-18 and EA-18G Program Protection Plan (PPP) (including Annexes) most current issuance, the Security Guidance for F/A-18 Hornet (All Series) and the EA-18G Growler Aircraft / Systems and Security Classification Guides applicable for the F/A-18 (All Series) and EA-18G Aircraft and Systems.
This Data Item Description (DID) contains the format, content, and intended information for the data product resulting from the work task described in the contract SOW.
This DID DI-MGMT-81826D cancels and replaces DI-MGMT-81826C.
Preparation Instructions
1Reference documents.The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.
Note: For PPIP Reference Documents see Paragraph 4 and its subparagraph's:
2Format.The required document shall be in Contractor format:
2.1The PPIP shall be used as a focal point for the Contractors Program Security.The PPIP is derived from the PPP and should not restate what is written in the PPP but simply state "how" the contractor will implement Program Protection.
2.2The PPIP is used to identify and monitor how a Contractor develops and performs Program Protection / Operations Security (OPSEC) activities during performance of the contract.
3Content.The Contractor's PPIP shall contain the following:
3.1Delivered document at a minimum shall include a cover page identifying the Subject, Contractors Name and Address, Contact number, DID identification, Distribution Statement, Export Control, and Destruction Notice.
3.2Security Management organization.
3.2.1The Contractor's Program Security / OPSEC Management structure, including relationships with the corporate hierarchy, program subcontractors and suppliers.
3.3A section detailing the Contractors approach to the PPIP.
3.4General methodologies that will be applied to protection requirements.
3.5Critical Program Information including the following; Critical Components (CC), Critical Program Information (CPI), Critical Systems (CS), and Critical Technologies, (CT); hereafter referred to as CPI.
3.6The Contactor's process / procedures for identifying any existing / proposed CPI during developmental and RDT&E phases, and its protection / identification in the ECP process prior to ECP acceptance by the Government.
3.7A section describing an effective and efficient protection of CPI; whichever are applicable and shall include the following:
3.7.1An overview of all Contractor's System Security Engineering (SSE) (NIST SP 800-160) approach to activities, operations, tests, and other associated activities to be undertaken in performance of the contract; identifying those in which classified information could manifest itself; identifying the topics of the classification guide that specify the information that is classified; determine how, where, and when the classified information is embodied in the hardware, software or operations; determine what type access (visual, physical) permits knowledge of the classified information.
3.7.2Identification of the CPI and physical locations under the Contractor's or its subcontractors' control and how the CPI is to be managed / tracked / secured throughout the CPI's life-cycle.
3.7.3An SSA assessment of the vulnerability of the CPI to intelligence collection in the following areas: Human Intelligence (HUMINT), Open Source Intelligence (OSINT), Signals Intelligence (SIGINT), Imagery Intelligence (IMINT), and Computer Network Operations (CNO.)
3.7.4Identification of the planned countermeasures at each site where CPI is utilized / secured from the following security domains: Physical security; personnel security; telecom and network security, application, systems development, cryptography, and security architectures.
3.7.5All special handling procedures required for CPI, and procedures for recovering CPI in the event of a mishap; address these procedures for all phases of the program, including: Program / System Technology Development, System Development & Demonstration, RDT&E, Production Deployment, Operations, Maintenance, Logistics, Transportation, Training, and Disposal under this contract for which the Contractor has control.
3.7.6A Description of the process that shall be used to assess new acquisitions (Incremental / Spiral upgrades, Engineering Change Proposal(s) (ECP's)) for CPI.
3.7.7A Description of how the Contractor shall comply with procedures for ensuring compliance with U.S. Government export statutes and regulations that affect CPI in the contracted program.
3.7.8A Description of the Contractor's procedures for public release of program information.
3.7.9A Description of the Contractor's Information Security Program (ISP) as a part of their PPIP.As an integral part of the ISP, describe the Contractor procedures for identifying, reporting and resolution of Facility Security Breaches; Classified Information Compromises / Spillages including notification of DSS, DCMA, and Government Program Security Manager (PSM) within the constraints specified in the DD 254 / CDRL / Contract.
3.7.10Describe how the Contractor shall implement the Department of Defense (DoD) PKI policy.PKI encryption is the chosen compliant DoD standard for protecting Controlled Unclassified Information (CUI) during transmission. CUI encompasses For Official Use ONLY (FOUO) and Sensitive Information. Failure to encrypt CUI during electronic transmission is considered a security weakness and shall be reported to the PSM / Cyber Security Manager (CSM).
3.7.11Describe the how Security classification guidance and original classification authority (OCA) for Defense Industrial Base (DIB) information shall be developed in order to mitigate risks to critical DoD unclassified information supporting present and future DoD warfighting capabilities and residing on, or transiting, the Contractors/ Sub-contractors private networks.
3.7.12Describe All special handling procedures required for CC / CPI / CS / CT, and procedures for recovering CC / CPI / CS / CT in the event of a mishap; address these procedures for all phases of the program, including: Program / System Technology Development, System Development & Demonstration, RDT&E, Production Deployment, Operations, Maintenance, Logistics, Transportation, Training, and Disposal under this contract for which the Contractor has control.
3.7.13Describe how the contractors DIB Cyber Security is addressed in the Contractors facility and addressed in subcontracts and how incidents are addressed and reported to DSS / DCMA.Framework Agreements and contracts that contain DIB cyber security requirements for safeguarding DoD classified and unclassified information. DIB participants shall handle classified and sensitive unclassified information, such as CUI; CPI (as described in applicable DoD documents, as required by law and regulation, Risk Management Framework Agreements, and contracts.
3.8Supply Chain Risk Management (SCRM) / Counterfeit Prevention:
3.8.1The Supply Chain Risk Management (SCRM) / Counterfeit Prevention portion of the PPIP shall include the establishment / identification of a SCRM / Counterfeit Prevention program tailored to fit the contractor's acquisition program identifying how supply chain risks shall be addressed across the entire system lifecycle through a defense-in-breadth approach to managing the risks to the integrity of information and communications technology (ICT) within covered / applicable systems.
3.8.2PPP requires the contractor to establish policy and a defense-in-breadth strategy for managing supply chain risk for mission-critical functions which would degrade the system effectiveness in achieving the core mission for which it was designed.A mission-critical component is a component that is or contains information and communications technology (ICT), including hardware, software, and firmware, whether customer, commercial, or otherwise developed, and which delivers or protects mission critical functionality of a system or which, because of the system's design, may introduce vulnerability to the mission critical functions of an applicable system and shall be described in the Contractors PPIP.
Level I and or Level II components are identified by a criticality analysis of mission-critical functions consistent with NIST SP 800-53R4 and supplemental guidance, and identify the critical functions in which a failure of which would result in either (catastrophic) (Level I) or unacceptable compromise of mission capability or significant mission degradation (critical) (Level II).
Suppliers shall utilize the following criticality levels:
Level I (Catastrophic) protection failure that results in total compromise of mission capability
Level II (Critical) protection failure that results in unacceptable compromise of mission capability or significant mission degradation
Level III (Marginal) protection failure that results in partial compromise of mission capability or partial mission degradation
Level IV (Negligible) protection failure that results in little or no compromise of mission capability.
3.8.3Describe how the contractor and its subcontractors shall prepare and submit the Naval Aviation Supply Chain Risk Management (SCRM) process report as described in the SOW.
3.8.4The PPIP shall include the following elements / requirements as described in the Contractors Product Specification (Parts, Materials and Processes Selection List (PMPSL) / "As Designed" and "As Built" Parts List.
3.8.4.1Incorporation of all-source intelligence analysis into assessments of the supply chain for covered systems.(CPI Review using the Navy Standard CPI Identification WBS Tool (most current version).)
3.8.4.2Procurement practices and procedures to include procurement of all parts and materials from original qualified parts / materials equipment manufacturer (OEM) or it franchised / authorized distributor.
3.8.4.3Procurement practices and internal processes used for exceptions to buying from OEM or OEM franchised distributors in cases where items are no longer available including a process to qualify / certify non-OEM parts & materials.
3.8.4.4Monitoring procedures to include the delivery of test results from random sampling and supply chains surveillance that does not assume any source is safe to identify possible penetration of OEM supply chain.
3.8.4.5Processes to control the quality, configuration, and security of software, hardware, and systems throughout their lifecycles, including components or subcomponents from secondary sources.Monitor processes at all subcontractor levels processes and verify compliance through on-site audits.
3.8.4.6Processes to detect the occurrence, reduce the likelihood of occurrence, and mitigate the consequences of products containing counterfeit components or malicious functions.
3.8.4.7Processes to ensure that the fabrication of integrated circuits that are custom-designed and / or custom-manufactured (generally referred to as "application-specific integrated circuits") for a specific DoD end use within covered systems are, as appropriate to the risk, performed by suppliers of integrated circuit-related services accredited through an authority designated by the Under Secretary of Defense for Acquisition, Technology, and Logistics (USD(AT&L)), unless expressly waived by the Milestone Decision Authority (MDA).
3.8.4.8Describe how the contractor shall report suspected counterfeit / malicious / counterfeit parts via Government Industry Data Exchange Program GIDEP Counterfeit / malicious modified parts, also reference (http://www.gidep.org/data/submit.htm) / DI-QCIC-80125B for reporting as a guide.
3.9The OPSEC portion of the PPIP shall provide for program development, planning, training, assessment, surveys, and readiness training.Including the results of the five-step OPSEC analysis Identifying Critical Information (CI), Analyzing Threats, Analyzing Vulnerabilities, Assessing Risk; and Applying Countermeasures, including those aspects of the foreign intelligence threats that are applicable to the contract. The following shall be addressed:
3.9.1General:Details of the OPSEC management concept to include contract identification, assignment of responsibilities, definition of milestones with target dates, provisions for continuous analysis, and how periodic revision as the contract activities evolve and become more specific and detailed.
3.9.2Threat:The known threats to the contracting activity and include only that portion deemed applicable to the specific contract activities in addition to how threats will be mitigated.
3.9.3Sensitive Aspects of the Contract:An overview of all activities, operations, tests, etc. to be undertaken in performance of the contract; identifying those in which classified information could manifest itself; identify the topics of the classification guide that specify the information that is classified; determine how, where, and when the classified information is embodied in the hardware, software or operations; determine what type access (visual, physical) permits knowledge of the classified information, what tools / equipment / capability are required, and the specific national defense advantage provided by that information if it is protected. Use of electromechanical equipment is an operation that shall be included, as are subcontracting, hardware-in-the-loop testing, calibration and check-out, fabrication, static tests, breadboard and brass board fabrication and testing, and laboratory experiments. A list of critical information, based on the above analysis, shall include all the information considered essential to the success of the effort, and all the information that must be protected to preserve the military advantage potentially provided by the effort. Additionally, the list shall include all the activities, operations, and tests that could reveal the "critical" information to foreign intelligence.
3.9.4Vulnerabilities:The vulnerabilities derived by comparing identified threats to sensitive activities to determine which activities can be observed by foreign intelligence. "Observe" is defined to include all physical and chemical properties that can be noted and recorded by any type sensor. One such property is unintentional electromagnetic emanations, which may convey classified information. On this basis, TEMPEST is a part of OPSEC, and TEMPEST vulnerabilities shall be identified and mitigated. National security information shall not be compromised by emanations from Classified Information Processing Systems.
3.9.5Countermeasures:The unacceptable risks of the vulnerabilities identified above shall include; the protective measures deemed appropriate to negate or reduce the potential damage to the project / program.
3.9.6Organizational OPSEC Communications and Interfaces:A description as to how the Plan will be communicated to personnel supporting the program.
3.9.7OPSEC guidance shall identify all interfaces internal to the corporation such as Senior Corporate Leadership, OPSEC Working Group, OPSEC Coordinators, and program personnel.
3.9.8OPSEC guidance shall identify all external points of contact; Contracting activity, Defense Contract Management Agency (DCMA), Defense Security Service (DSS), Federal Bureau of Investigation (FBI) and local Law Enforcement.The guidance shall identify the contacts primary role within the OPSEC program. Subcontractor and supplier OPSEC points of contact shall be similarly identified.
3.9.9The categories of Potential Critical Information (CI) that shall be protected and planned for in the PPIP are:
3.9.9.1Current and Future Operations
3.9.9.2Travel Itineraries
3.9.9.3Usernames and Passwords
3.9.9.4Access / Identification Cards
3.9.9.5Operations Planning Information
3.9.9.6Personal Identification Information
3.9.9.7Entry / Exit (Security) Procedures
3.9.9.8Capabilities and Limitations
3.9.9.9Address and Phone Lists
3.9.9.10OPSEC Budget Information
3.9.9.12VIP / Distinguished Visitor Schedules
3.9.9.13Release of corporate information describing current business.
3.9.9.14Describe how the contractors Counterintelligence Awareness and Reporting, and the contractors plan to comply with the training and reporting requirements of the above.
3.10When contractually required, describe how the contractor shall protect Anti Tamper (AT) Plans and associated information.
4References:For CJCSI Documents see: http://www.dtic.mil/cjcs_directives/cjcs/instructions.htm
For OPNAV / SECNAV / Navy Documents see: http://doni.daps.dla.mil/default.aspx
For DoD Documents see: http://www.dtic.mil/whs/directives/
For Mil Documents see: http://quicksearch.dla.mil/
For PMA / Classified Documents formally request from PCO / PMA265
Documents are also available via the internet
4.1Chairman Joint Chiefs Publications (http://www.dtic.mil/cjcs_directives/cjcs/instructions.htm):
4.1.1CJCSI 6211.02D, Defense Information System Network (DISN), Responsibilities (current as of 4 Aug 15)
4.1.2CJCSM 6510.01B, Cyber Incident Handling Program (10 July 12, Current as of 18 Dec 2014) http://www.jcs.mil/Library/CJCS-Manuals/udt_48785_param_orderby/Info/udt_48785_param_direction/ascending/
4.2DoD Publications / Manuals (http://www.dtic.mil/whs/directives/):
4.2.1DoDM 5200.01, Volume 1, DoD Information Security Program: Overview, Classification, and Declassification (24 Feb 12)
4.2.2DoDM 5200.01, Volume 2, DoD Information Security Program: Marking of Classified Information (24 Feb 12, C-2 19/3/13)
4.2.3DoDM 5200.01, Volume 3, DoD Information Security Program: Protection of Classified Information (24 Feb 12, C-2 19/3/13)
4.2.4DoDM 5200.01, Volume 4, DoD Information Security Program: Controlled Unclassified Information (CUI) (24 Feb 12)
4.2.5DoD 5200.08-R, Physical Security Program (9 Apr 2007 C-1, 27 May 09) (also see DTM-09-012 (C 7, 17 Apr 17)
4.2.6DoD 5205.02E, DoD OPSEC Program (20 Jun 12)
4.2.7DoD M O-5205.13, Defense Industrial Base (DIB) Cyber Security and Information Assurance (CS / IA) Program Security Classification Manual (SCM) (26 Apr 12)
4.2.8DoD 5220.22 M, National Industrial Security Program Operating Manual (NISPOM) (C-2, 18 May 16)
4.2.9DoD 5240.1-R, Procedures Governing the Activities of DoD Intelligence Components That Affect United States Persons, (1 Dec 82) also see DTM 08-052, DoD Guidance for Reporting Questionable Intelligence Activities and Significant or Highly Sensitive Matters (17 Jun 09 Incorporating Change 3, 30 Jul 12) and DTM-08-011, Intelligence Oversight Policy Guidance (26 Mar 2008 Incorporating Change 3, 27 Jul 12)
4.3DoD Directives (http://www.dtic.mil/whs/directives/):
4.3.1DoDD 5000.01, The Defense Acquisition System (12 May 03; Certified Current as of 20 Nov 2007)
4.3.2DoDD 5205.02E, DoD OPSEC Program (20 June 12)
4.3.3DoDD 5230.09, Clearance of DoD Information for Public Release (22 Aug 08, Cert Current Thru 22 Aug 15)
4.3.4DoDD 5230.11, Disclosure of Classified Military Information to Foreign Governments and International Organizations (16 Jun 92)
4.3.5DoDD 5230.20, Visits and Assignments of Foreign Nationals (22 Jun 05)
4.3.6DoDD 5230.25, Withholding of Unclassified Technical Data from Public Disclosure (6 Nov 84; Incorporating Change 1, 18 Aug 95)
4.3.7DoDD 8100.02, Use of Commercial Wireless Devises, Services and Technologies in the DoD Global Information Grid (14 Apr 04, Cert. Current as of 23 Apr 07)
4.4DoD Instructions (http://www.dtic.mil/whs/directives/):
4.4.1DoDI 2040.02, International Transfers of Technology, Articles, and Services (27 Mar 14)
4.4.2DoDI 4140.01, DoD Supply Chain Materiel Management Policy (14 Dec 11)
4.4.3DoDI 4140.67, DoD Counterfeit Prevention Policy (26 Apr 13)
4.4.4DoDI 4240.01, DoD Supply Chain Materiel Management Policy (14 Dec 11) (counterfeit))
4.4.5DoDI 4160.28, DoD Demilitarization (DEMIL) Program (7 Apr 11)
4.4.6DoDI 5000.02, Operation of the Defense Acquisition System (7 Jan 15)
4.4.7DoDI 5200.01, DoD Information Security Program and Protection of Sensitive Compartmented Information (9 Oct 08, C-1 13 Jun 11)
4.4.8DoDI 5200.08, Security of DoD Installations and Resources and the DoD Physical Security Review Board (PSRB) (10 Dec 2005, C-3, 20 Nov 15 (Also see DTM-09-012))
4.4.9DoDI 5200.39, Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E) (28 May 15)
4.4.10DoDI 5200.44, Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN) (5 Nov 12, C2 2 Jul 17)
4.4.11DoDI 5230.24, Distribution Statements on Technical Documents (23 Aug 12)
4.4.12DoDI S-5230.28, Low Observable (LO) and Counter Low Observable (CLO) Programs (U), CLASSIFIED DOCUMENT (26 May 05) Authorized users may contact the OPR / COR. (OPR: USD (AT&L), 703-697-0016)
4.4.13DoDI O-5240.24, Counterintelligence (CI) Activities Supporting Research, Development, and Acquisition (RDA) (8 Jun 11, C-1 15 Oct 13)
4.4.14DoDI 8420.01, Commercial Wireless Local-Area Network (WLAN) Devices, Systems, and Technologies (3 Nov 09)
4.4.15DoDI 8500.01, Cybersecurity (14 Mar 14)
4.4.16DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT) (IA) 12 Mar 14
4.4.17DoDI 8520.02, Public Key Infrastructure (PKI) and Public Key (PKI) Enabling (21 May 11)
4.4.18DoDI 8340.04, Item Unique Identification (IUID) Standards for Tangible Personal Property (Sep 15) (counterfeit))
4.4.19DoDI 8580.1, Information Assurance (IA) in the Defense Acquisition System (9 Jul 04)
4.4.20DoDI 8582.01, Security of Unclassified DoD Information on Non-DoD Information Systems (6 Jun 12)
4.5Department of the Navy (OPNAV/SECNAV) (available via http://doni.daps.dla.mil/SECNAV.aspx):
4.5.1OPNAVINST 3432.1A, OPSEC, (4 Aug 11)
4.5.2OPNAVINST 3750.6S, Naval Aviation Safety Program (13 May 14)
4.5.3OPNAVINST 3811.1E, Threat Support to the Defense Acquisition System, (04 Jan 12)
4.5.4OPNAVINST 5239.3A, Navy Implementation of DoD Intelligence Information System (DODIIS) Public Key Infrastructure (PKI) (18 Jan 08)
4.5.5OPNAVINST 5513.2C, Security Classification Guide (SCG) (21 Jul 08), (Encl (02-26) for the F/A-18 Hornet (All Series) and Electronic Attack EA-18G Aircraft, (29 Oct 14) most current version)
4.5.6OPNAVINST 5530.14E, Navy Physical Security and Law Enforcement Program (28 Jan 09, C-2 23 Sep 14)
4.5.7SECNAVINST 5000.2E, DoN Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System (1 Sep 11)
4.5.8SECNAVINST M-5000.2, DoN Acquisition and Capabilities Guidebook (May 12)
4.5.9SECNAVINST 5200.39A, Participation in the Government Industry Data Exchange (GIDEP), (25 Dec 05)
4.5.10SECNAVINST 5510.36A, DoN Information Security Program (ISP) Instruction (6 Oct 06)
4.5.11SECNAV M- 5510.36, DoN Information Security Program, (Jun 06)
4.6Other DoD / Navy Publications (Available via ASSIST / internet):
4.6.1DAG Chapter 13, Program Protection (The Defense Acquisition Guidebook) (Most current Defense Acquisition University version) (Available via DAU on the internet)
4.6.2Key Practices and Implementation Guide for the DoD Comprehensive National Cybersecurity Initiative 11 Supply Chain Risk Management Pilot Program (25 Feb 10)
4.6.3DI-QCIC-80125B, Government Industry Data Exchange Program (GIDEP) Alert/Safe-Alert Report (05 May 03) (Available via internet)
4.6.4DI-QCIC-80126B, Government Industry Data Exchange Program (GIDEP) (05 May 03) (Available via internet)
4.7Presidential Executive Orders (Available via internet) / Public Laws (P.L.) (Available via internet):
4.7.1E.O. 12968, Access to Classified Information, (2 Aug 95, as amended)
4.7.2E.O. 13526, Classified National Security Information (29 Dec 09)
4.7.3E.O. 13587, Structural Reforms to Improve the Security of Classified Networks and the Responsible Sharing and Safeguarding of Classified Information, 7 Oct 11
4.7.4NSPD-54 / HSPD23, National Security Presidential Directive 54, in conjunction with Homeland Security Directive-23 (2 Mar 10)
4.7.5NSDD 298, National Security Decision Directive, National Operations Security Program (22 Jan 88)
4.7.6OMB A-130 Appendix III, Security of Federal Automated Information Resources (Circular No A-130) (IA)
4.7.7OMB Policy Letter 91-3, Reporting Nonconforming Products, (9 Apr 1991)
4.7.8Defense Authorization Act 254, National Defense Authorization Act, Senate Report 109-254 (9). P.L. 87-794, Trade Expansion Act of 1962 (76 Stat. 872, enacted October 11, 1962, 19 U.S.C. Section 1801)
4.7.9P.L. 96-72, Export Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq) (1979)
4.7.10P.L. 104-106, Information Technology Management Reform Act, Division E, (Clinger-Cohen Act) (10 Feb 1996)
4.7.11P.L. 104-231, Freedom of Information Act, As Amended By 104-231, 110 Stat5 U.S.C. Section 552, 3048
4.7.12P.L. 112-81, Section 818 (f)(2) and (c)(2), Defense Auth. Act for Fiscal Year 2012
4.7.13P.L. 112-239, Section 833, Defense Auth. Act for Fiscal Year 2013
4.8Federal Acquisition Regulations (FARS) / Defense Acquisition Regulations (DFARS) (Available via internet / COR / PCO):
4.8.1DFARS Disclosure of Information (Oct 2016)
4.8.2DFARS 252-204-7012, Safeguarding of Unclassified Controlled Technical Information (18 Nov 13)
4.8.3DFARS 246.407, Nonconforming Supplies/Services, Government Contract Quality Assurance (1 Aug 10)
4.8.4DFARS 252.246-7003, Defense Federal Acquisition Regulations Supplement "Notification of Potential Safety Issues" (Revised March 3, 2008)
4.8.5DFARS 2012-D055, Detection and Avoidance of Counterfeit Electronic Parts
4.8.6DFARS 2013-27311, Requirements Relating to Supply Chain Risk
4.8.7FAR 45.101, Demilitarization
4.8.8FAR Subpart 46.4, Government Contract Quality Assurance
4.8.9FARS 252.217.7026, Identification of Sources of Supply
4.9Other Applicable National Standards / Publications (Available via internet / COR / PCO):
4.9.1CNSSI 1001, National Instruction on Classified Information Spillage (Feb 08) (Available via internet)
4.9.2CNSSD 505, Supply Chain Risk Management (SCRM) (7 Mar 12)
4.9.3FISMA, (2014) Title III, Public Law 107-347; Federal, Information Security Management Act of 2002 (H. R. 2458-48) (& Dec 2002) (IA) (Available via internet) (PL 113-283, 44 USC 3554)
4.9.4Title 18 Section 1831, Economic Espionage, et seq of, (Jan 08) (Available via internet)
4.9.5Title 22, Chapter 39, Arms Export Control Act, (U.S.C., Sec 2751, et seq.) (4 Jan 12) (Available via internet)
4.10Military Standards (Available via ASSIST @, http://quicksearch.dla.mil/)
4.10.1MIL-STD-464C, DoD Interface Standard: Electromagnetic Environmental Effects Requirements for Systems (01 Dec 2010)
4.10.2Mil-STD 882E, Department of Defense safety Standard Practice System (SCRM) (11 May 2012)
4.11Supply Chain Risk Management (SCRM) Program Management (Available via Internet / NIST / commercial sources)
4.11.1NISTIR 8179 Criticality Analysis Process Model
4.11.2NISTIR 7622, Piloting Supply Chain Risk Management Practices for Federal Information Systems (Jun 10)
4.11.3NIST SP 800-37 Rev 1, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach (Feb 10)
4.11.4NIST SP 800-39, Managing Information Security Risk: Organization, Mission, and Information System View (Mar 11)
4.11.5NIST SP 800-59, Guideline for Identifying an Information System as a National Security System (Aug 03) (Available via internet/NIST)
4.11.6NIST SP 800-160, SYSTEMS SECURITY ENGINEERING (Jan 18)
4.11.7NIST SP 800-171, Protecting Controlled Unclassified Information (CUI) in Nonfederal Information Systems and Organizations (June 2015)
4.11.8DoD Key Practices and Implementation Guide for the DoD Comprehensive National Cybersecurity Initiative 11 Supply Chain Risk Management Pilot Program (25 Feb 10)
4.11.9CNSS No. 505, Supply Chain Risk Management (7 Mar 12)
4.12SCRM Industry Standards (pertain to electronic components, standard industry practice available via commercial sources):
4.12.1ANSI / EIA-4899B, Standard for Preparing an Electronic Component Management Plan (2016)
4.12.2IDEA-STD-1010B, Acceptability of Electronic Components Distributed in the Open Market (Apr 11)
4.12.3AS 9120 Rev C, Quality Management Systems for Aerospace Product Distributors (Jun 12)
4.12.4SAE-AS 5553B, Counterfeit Electronic Parts; Avoidance, Detection, Mitigation and Disposition (2016)
4.13Program Office applicable Documents (Formally request via PCO/Contracting Officer)
4.13.1F/A-18E/F and EA-18G Program Protection Plan ((9 Apr 14))
4.13.2Security Guidance F/A-18 Hornet (All Series) and EA-18 G Growler Aircraft and Systems (most current versions)
Schema v3.0Community-maintained · Verify against ASSIST