DoD Instruction 2040.02, International Transfers of Technology, Articles, and Services, requires that the Department of Defense (DoD) treat dual-use and defense-related technology as valuable national security resources, to be protected and transferred only in pursuit of national security and foreign policy objectives. These objectives include ensuring that: critical U.S. military technological advantages are preserved; transfers that could prove detrimental to U.S. security interests are controlled and limited; proliferation of weapons of mass destruction and their means of delivery are prevented; and diversion of defense-related goods to terrorists is prevented. At the same time, the sharing of defense technology, properly controlled, is a valuable way to ensure our allies and partners participate with the United States in future military operations. In applying export control and technology security policies, due recognition will be given to the importance of interoperability with allies and coalition partners and to impacts on the defense industrial base. DoD will apply export control and other technology security policies and procedures in a way that balances economic and scientific interests with those of national security. It is important that these considerations be taken into account prior to any commitment to disclose or release controlled defense-related information or technology. Table C3.T1. provides definitions for categories of controlled defense-related information and technology discussed in this chapter.

Table C3.T1. Classified and Sensitive Material Definitions

Title	Definition	Reference
Classified Information	Official information that has been determined, pursuant to Executive Order (E.O.) 12356 or any predecessor order, to require protection against unauthorized disclosure in the interest of national security and which has been so designated.	DoD 5220.22-M DTM-09-019
Communications Security (COMSEC)	Protective measures taken to deny unauthorized persons information derived from telecommunications of the U.S. Government (USG) relating to national security and to ensure the authenticity of such communications.	DoD 5220.22-M DTM-09-019
Controlled Cryptographic Item (CCI)	A secure telecommunications or information handling equipment ancillary device, or associated cryptographic component, that is unclassified but controlled. (Equipments and components so designated bear the designator “Controlled Cryptographic Item” or “CCI”).	DoDM 5200.01 Vol.1. DTM-04-009
Controlled Unclassified Information (CUI)	Information that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Government-wide policies, excluding information that is classified under E.O. 13526 of December 29, 2009, or the Atomic Energy Act of 1954, as amended. (P.L. 83-703)	E.O. 13556
Critical Program Information (CPI)	Elements or components of a Research Development, and Acquisition program that, if compromised, could cause significant degradation in mission effectiveness; shorten the expected combat-effective life of the system; reduce technological advantage; significantly alter program direction; or enable an adversary to defeat, counter, copy, or reverse engineer the technology or capability.	DODI 5200.39
Foreign Government Information (FGI)	Information that is: Provided to the United States by a foreign government or governments, an international organization of governments, or any element thereof with the expectation, expressed or implied, that the information, the source of the information, or both, are to be held in confidence; or Produced by the United States pursuant to, or as a result of, a joint arrangement with a foreign government or governments, an international organization of governments, or any element thereof, requiring that the information, the arrangement, or both are to be held in confidence.	DoD 5220.22-M DTM-09-019

C3.2.1. Policy on Disclosure of Classified Military Information (CMI) to Foreign Government and International Organizations. DoD Directive 5230.11 implements National Disclosure Policy (NDP-1). It is U.S. national and DoD policy that CMI is a national security asset that must be protected and shared with foreign governments only when there is a clearly defined benefit to the United States, when authorized by officials designated under the Directive and then only when all requirements of the Directive are met.

C3.2.2. Avoiding False Impressions. U.S. policy is to avoid creating false impressions of USG readiness to make available classified military materiel, technology, or information. Much military hardware is unclassified; however its operation and maintenance or related training may involve sensitive classified information. Some classified information (e.g., sensitive compartmented information (SCI), communications security (COMSEC) information, etc.) may require approval outside of DoD and the National Disclosure Policy Committee (NDPC). Accordingly, proposals to foreign governments or international organizations that result from either U.S. or combined (U.S. and proposed recipient) initial planning, and that will lead to the eventual disclosure of classified military information, must be authorized in advance by designated disclosure officials in the departments and agencies originating the information or by the NDPC. This includes the release of unclassified Price and Availability (P&A) data. Furthermore, it must be explicitly stated and acknowledged that no U.S. commitment to furnish such classified information or materiel is intended or implied until disclosure has been approved.

C3.2.3. Disclosure Authorities. Under the terms of NDP-1, the NDPC is the central authority for formulating, promulgating, administering, and monitoring national disclosure policy. The Secretary of Defense and the Deputy Secretary of Defense are the only officials who may grant unilateral exceptions to NDP-1. However, in most cases, exceptions to policy are granted or denied by the NDPC. Under DoD Directive 5230.11, the Secretary of Defense has delegated disclosure authority to the Secretaries of the Military Departments (MILDEPs) and other DoD officials whose decisions must be compliant with NDP-1. They are required to appoint a Principal Disclosure Authority (PDA) at component headquarters level to oversee the disclosure process and a Designated Disclosure Authority (DDA) at subordinate command and agency levels to oversee disclosure decisions at their level when disclosure authority is delegated. Any commitment to disclosure or release of controlled defense-related information or technology must be authorized by the PDA or DDA unless authority is otherwise delegated in a Delegation of Disclosure Authority Letter (DDL).

C3.2.4. Disclosure Decisions. PDAs or DDAs evaluate proposals for disclosure of classified information relating to defense articles and services on a case-by-case basis in accordance with NDP-1, DoDD 5230.11, and MILDEP regulations. An affirmative disclosure decision requires consent of the PDA or DDA representing the DoD Component that originated the information and the written consent of the official having original classification authority for the information if the information has not already been marked by the originator for disclosure to the intended recipient government or international organization. The PDA or DDA must also ensure that the disclosure criteria, conditions, and limitations in DoDD 5230.11, are satisfied, including the existence of a bilateral General Security Agreement (GSA) concerning the mutual protection of classified information. In the absence of a GSA, the security requirements may be included in a program agreement (e.g., a co-production or cooperative development memorandum of understanding (MOU),) or in a program-specific security agreement described in Section C3.2.6. Disclosure authorizations for classified information are recorded in the National Disclosure Policy System (NDPS). The Chief of the U.S. Diplomatic Mission must approve in-country release of all Security Assistance (SA) information to a purchaser.

C3.2.5. Tentative Security Assistance Plans and Programs. Classified planning information for budget and future years may be released to a foreign government or international organization to the extent it is necessary for participation in the SA planning process; it is necessary for development of related defense plans; the purchaser can maintain security precautions; and the purchaser uses the information only for the intended purposes. If the release involves classified information or Controlled Unclassified Information (CUI), the release must be approved by the supporting DDA. Classified dollar levels of proposed programs may be released only with permission of the Director, DSCA, and Department of State (DoS) concurrence. U.S. officials releasing information under this paragraph must ensure that the recipient understands that the release does not constitute a commitment by the United States.

C3.2.5.1. FMS Agreements. After an LOA is approved, classified information regarding the quantity and projected delivery schedules for articles and services in FMS agreements may be released to facilitate appropriate planning by the recipient, subject to assurance by the recipient that it will maintain adequate security precautions and use the information only for the purposes for which provided. Release is made only to purchaser Government officials who require the information in their official capacity.

C3.2.6. Program Security Agreements. When there is no General Security of Information Agreement (GSOIA) or General Security of Military Information Agreement (GSOMIA) with a purchasing government, provisions for protecting CMI must be included in another related agreement. If, for example, the CMI is being released in conjunction with a co-production or cooperative development and production governed by an MOU, the provisions may be included in the MOU. Letters of Offer and Acceptance (LOAs), however, are not international agreements. If CMI is to be released in support of an FMS sale, and there is no GSOIA or GSOMIA, a program specific security agreement developed and approved by the Defense Technology Security Administration (DTSA) containing the security requirements must be concluded prior to discussion of CMI with the purchasing government. Depending upon the circumstances, this may take the form of a separate international agreement as defined by DoDD 5530.3 or by 22 CFR Part 181, or as a separate arrangement pursuant to the LOA. Questions concerning which form a program-specific security agreement should take should be directed to DSCA (Programs Directorate, Weapons Division and Office of the General Counsel). The agreement will contain, at a minimum, the provisions described in Figure C3.F1. below.

Figure C3.F1. Sample Text for a Program-Specific Security Agreement

Full Size Image PDF Version of Figure

C3.2.7. National Industrial Security Program (NISP). U.S. security depends on the proper safeguarding of classified information released to industry. The NISP ensures that classified information released to cleared U.S. contractor facilities is safeguarded during all phases of the contracting, licensing, and grant processes. The NISP also applies to all classified information not released under a contract, license certificate, or grant, and to Foreign Government Information (FGI) furnished to contractors that requires protection in the interest of national security. DoD 5220.22-R and DTM-09-019 provides procedures used by DoD to ensure maximum uniformity and effectiveness in application of NISP policies to industry. The NISP Operating Manual (NISPOM), DoD 5220.22-M, Supplement 1, contains detailed security requirements for U.S. contractors’ use in safeguarding classified information. The NISPOM is applied to industry by management’s execution of the DoD Security Agreement (DD Form 441), and by direct reference in the “Security Requirements” clause in the contract. The Defense Industrial Security Clearance Office (DISCO) verifies the eligibility of industry personnel to access classified defense information.

C3.2.8. U.S. Contracts with Foreign Firms. Implementing Agencies (IAs) may award (or permit a contractor to award) a classified contract to a foreign contractor if the classified information is releasable to the government of the foreign contractor under NDP-1. Foreign disclosure implications are identified by the program office and resolved by the supporting DDA prior to any announcements that could lead to foreign involvement. Classified information must be requested and transferred through government channels in compliance with the DoD Component documentary request procedures. Prior to any activity that may result in the disclosure of classified information to a foreign contractor, the IA will request that DISCO seek a Facility Security Clearance Assurance (FSCA) from the security authorities of the foreign contractor. The FSCA verifies the facility security clearance of the foreign contractor and advises the other government that U.S. classified information is to be transferred to a contractor under its jurisdiction under the terms of the relevant bilateral security agreements with the other government. IA responsibilities are contained in DoD 5220.22-R and DTM-09-019.

C3.2.9. Contracts Requiring Overseas Deliveries. When an IA places a contract with a cleared U.S. contractor for delivery of classified information or materiel to a foreign government, the IA is responsible for delivery. See Chapter 7 for more information regarding transportation of classified information.

C3.3.1. International Traffic in Arms Regulations (ITAR) Requirements. DoS policies and procedures for the permanent export of items on the U.S. Munitions List (USML), purchased under the FMS program, are set forth in the ITAR. Export of USML items, including certain services and technical information, requires a license unless it is done via FMS. The Defense Technology Security Administration (DTSA) researches and validates license applications for DoD.

C3.3.2. ITAR Exemptions. The ITAR includes many exemptions from the licensing requirements. Some are self-executing by the contractor who is to use them and normally are based on prior authorizations. Other exemptions, such as the exemption in 22 CFR 125.4(b)(1), may be requested or directed by the DoD Component. Only a PDA or DDA has the authority to exercise certain of these exemptions in compliance with the National Industrial Security Program Operating Manual (NISPOM), DoD 5220.22-M. For an exemption to be used for follow-on support by a contractor, the LOA and the contract must be specific regarding the exporter, the specific service or information to be provided, any sub-contractors involved, intermediate consignees, the end-use, and the end-user. Failure to fully document this information may result in program delays and requirements for obtaining additional export authorizations by the supporting contractor.

C3.3.3. DoD-Sponsored Shipments of FMS Materiel.

C3.3.3.1. Export Requirements for DoD-Sponsored Shipments. A DSP Form 94 is required, in addition to the LOA, pursuant to ITAR, Part 126.6(c)(6)(ii). When classified material is involved, a Transportation Plan is required in accordance with ITAR, Part 126.6(c)(6)(iii). See Chapter 7 for procedures. Exports of FMS materiel through the Defense Transportation System (DTS) requires entry of the electronic export information (EEI) into the Automated Export System (AES)” should replace If a continental United States (CONUS)-located shipping activity offers FMS shipments directly to commercial air carriers for lift to a purchaser's country, it may be necessary for the shipper to prepare an EEI to enable the materiel to depart CONUS. (Item 16 in the EEI must contain "M"s to identify the materiel as FMS exports. The Census Bureau maintains a web page and customer assistance phone number to assist shippers with EEI preparation.)

C3.3.3.2. Overseas Customs Clearance Requirements for DoD-Sponsored Shipments. The purchaser is responsible for obtaining overseas customs clearances and for all actions and costs associated with customs clearances for deliveries of FMS materiel using DTS, including any intermediate stops or transfer points.

C3.3.3.3. Reporting of FMS Export Shipments for DoD-Sponsored Shipments. All USG and DoD-sponsored shipments of FMS export materiel moving overseas within DTS are reported monthly to the Foreign Trade Division, Bureau of Census, Department of Commerce (DoC), by the IA sponsoring the sale. The Census Bureau Shipment Report (CBSR) assures compliance with conditions under which exemptions are granted and satisfies the export data requirements of the U.S. Department of Commerce.

C3.3.3.4. Purchaser-Sponsored Shipments of FMS Materiel.

C3.3.3.4.1. Export License Requirements for Purchaser-Sponsored Shipments. An export license is not required when FMS materiel is transferred to the purchaser within the United States; however, ITAR Form DSP-94, accompanied by a signed and implemented LOA, including all Amendments or Modifications, must be used to export these shipments and lodged at a U.S. Customs Port. Further detail is in Table C7.T1. outlines responsibilities for FMS purchasers and FMS freight forwarders. To use a DSP-94, a freight forwarder must: be registered with the DoS, Directorate of Defense Trade Controls (DDTC); file a letter with DDTC from the foreign embassy or government appointing it as a forwarding agent for that government's shipments; file a statement with DDTC assuming full responsibility for compliance with the ITAR; and if it is to handle classified consignments, have a Facility Security Clearance (FCL) issued by the Defense Security Service (DSS) and U.S. citizen personnel with the required security clearance. If a foreign purchaser acts as its own freight forwarder, it must register with DDTC and file a statement that it will comply with the ITAR. If the materiel involves classified articles or data, a Transportation Plan is required. See 22 CFR 126.6 and Chapter 7 for requirements.

C3.3.3.4.2. U.S. Customs Clearance Requirements for Purchaser-Sponsored Shipments. The purchaser or its designated FMS freight forwarder must obtain Customs clearances for FMS materiel exported from the United States. The purchaser's representative or freight forwarder prepares Electronic Export Information (EEI) using the Automated Export System (AES). EEIs must be filed with and authenticated by U.S. Customs and Border Protection (CBP) at the primary port of exit. Laws and regulations concerning export declarations are found on the DDTC web page, AES Direct web site, and in 22 CFR 123.9, 123.22, 123.25, and 126.6. All exports of FMS materiel from the U.S. must be reported to the U.S. DoC, as required by current Federal statutes or regulations.

C3.3.3.4.3. Overseas Customs Clearance Requirements for Purchaser-Sponsored Shipments. The purchaser is responsible for all actions and costs associated with obtaining overseas customs clearances for deliveries of FMS materiel to a purchaser's port of discharge (including delivery to third countries) using commercial means.

C3.3.3.4.4. Purchaser-Sponsored Shipments of Classified FMS Materiel. If a purchasing country proposes to take possession of classified defense articles purchased under the FMS program within the United States, it must obtain an export authorization (DSP-94).

C3.3.3.4.4.1. Transportation Plan for Purchaser-Sponsored Shipments. The LOA must contain the requirement for, and describe the specific responsibilities for preparing, the Transportation Plan. The Transportation Plan must provide a specific description of the transfer arrangements and nationality of freight forwarders and carriers to be used, all of which shall be consistent with DoDM 5200.01 Vol. 1, DTM-04-009, DTM-04-010, and DoD 5220.22-M, Supplement 1. A Transportation Plan is required for the use of any carrier, whether commercial or DTS. The Transportation Plan must be approved by the IA before delivery of the material. A detailed description and standardized format are available in Chapter 7.

C3.3.3.4.4.2. Foreign Government Representative. Classified materiel may be released only to a person who has been designated by the purchasing government in writing as its Designated Government Representative (DGR) or as its transfer agent (e.g., a cleared freight forwarder) that is used for onward movement to the point where custody of the shipment is assumed by the Government’s DGR. The Military Assistance Program Address Directory (MAPAD) must be consulted for the verification of freight forwarders that have been approved to handle classified shipments. The identity of the transfer agent, carrier, and DGR is included in the Transportation Plan or in the Notice of Availability (NOA) (DD 1348-5) for individual shipments as identified in Chapter 7. An NOA for classified material is sent to notify a purchaser’s representative, as listed in the MAPAD, that classified material is ready for shipment. The purpose of the NOA is to delay release of materiel requiring special receipt and export processing. Each entity that has custody of a classified shipment shall be required to sign for the shipment in accordance with the NISPOM (paragraph 10-406).

C3.3.4. Temporary Imports. When it is known at the time of LOA negotiation that items will be returned to the United States for any purpose, including maintenance, overhaul, repair, or other follow-on support, the LOA, contract, and original Transportation Plan must provide for the return shipment or other support, consistent with Chapter 7.

C3.3.4.1. Temporary Import of Unclassified Defense Articles. A Temporary Import License, ITAR Form DSP-61 is required for the import and re-export from the United States of unclassified defense articles that are not otherwise exempted by 22 CFR Part 123.4.

C3.3.4.2. Temporary Import of Classified Defense Articles. ITAR Form DSP-85 is required for any import and re-export from the United States of classified defense articles being temporarily imported into the United States.

C3.3.4.3. Temporary Import of Offshore Procurements. Materiel procured outside of the United States under USG and DoD procurement actions for the FMS program must be imported and exported under a DSP-61 if it passes through the United States en route to the purchasing country unless an exception under 22 CFR Part 123.4 applies. (There are additional exceptions for Canada and Mexico under 22 CFR Parts 123.19 and 126.5.) The DSP-61, filed by the purchaser or its agent, is required whether the materiel is imported or exported intact, or is incorporated into another defense article that is subsequently exported to the purchasing country.

C3.3.4.4. Temporary Import of Defense Articles for Repair. Articles temporarily imported into the United States for overhaul, repair, modification, calibration, etc., are subject to the DDTC license approval requirements listed in 22 CFR Part 123.1 unless the temporary import and subsequent re-export qualifies for an exemption pursuant to 22 CFR Part 123.4. When it is anticipated that FMS-origin unclassified articles will be returned to the United States for overhaul, repair, calibration, or modification, the import requirements should be included in the LOA for the original sale. For classified FMS-origin materiel the requirements should be included in the Transportation Plan, the LOA, or both. The FMS purchaser or its agent is responsible for filing documentation with U.S. CBP upon entry of the FMS-origin materiel into the United States (on temporary import basis) for Repair and Return. The entry documentation must contain the statement,

“This shipment is being imported in accordance with and under the authority of 22 CFR Part 123.4.(a)(subsection____)”

A complete list and description of the defense articles being imported must be included. The description includes quantity and value in U.S. dollars. When the materiel is subsequently re-exported, the purchaser or its agent must submit EEI., using AES Direct, to CBP that identifies 22 CFR Part 123.4 as the authority for the export and provide, as requested by CBP, the entry document number or a copy of the CBP document under which the FMS-origin defense article was imported on a temporary basis for Repair and Return. This requirement applies to both FMS customer-arranged shipments and shipments made through the DTS. IAs preparing FMS LOAs for Repair and Return programs should include a LOA note indicating the requirement for the foreign country to report imports and exports made under the LOA to CBP. See Appendix 6 on LOA Notes.

C3.3.4.5. Temporary Imports of Defense Articles without Subsequent Export of the Same Article. Under 22 CFR Part 123.4(b), a license is not required for the temporary import (but not the subsequent export) of unclassified defense articles that are to be incorporated into another article or modified, enhanced, upgraded, altered, improved or serviced in any other manner that changes the basic performance or productivity of the article. A DSP-5 is required for the re-export of these enhanced defense articles unless FMS exceptions apply.

C3.3.5. Permanent Imports. The Department of Justice, Bureau of Alcohol, Tobacco, Firearms, and Explosives (BATFE), regulates the permanent import of defense articles, as listed in the 27 CFR Part 447, United States Munitions Import List (based on the USML), pursuant to the AECA and implementing federal regulations. Permanent imports of defense articles into the U.S. require an approved BATFE Form 6 in accordance with 27 CFR Part 447. See http://www.atf.gov for more information.

C3.3.6. Contractor Proposals and Presentations. Policy and procedures for DoS approval regarding sales proposals or presentations of Significant Military Equipment (SME) are in 22 CFR Part 126.8. These requirements do not apply to SME that has been approved for sale under FMS.

C3.3.6.1. Export License Requirement. If marketing efforts involve the disclosure of technical data or temporary export of defense articles, the contractor must obtain the appropriate export license.

C3.3.6.2. Prior Approval for Contractor Presentations and Proposals. DoS approval must be obtained before any marketing efforts for sales that meet ALL of the following criteria: SME valued at $14 million or more; end-use by foreign armed forces other than NATO countries, Australia, Japan, South Korea, Israel, or New Zealand; export of any defense article or the furnishing abroad of any defense service including technical data; and identical SME has not been previously licensed for permanent export or approved for sale under the FMS program. This prior approval permits the contractor to conduct unclassified discussions and propose a sale of a specific item of SME to a particular country.

C3.3.6.3. Advance Notification for Contractor Presentations and Proposals. When the identical equipment meets the first three conditions in Section C3.3.6.2. and has not been previously licensed for permanent export or approved for sale under the FMS program to any foreign country, the contractor must notify the DoS in writing at least 30 days in advance of the proposal or presentation.

C3.3.6.4. Prior Approval for Manufacturing License Agreements (MLA) and Technical Assistance Agreements (TAA). Prior approval must be obtained for all proposals to enter into a MLA or TAA with a foreign country for the production or assembly of SME. An MLA or TAA is not required during the period in which the FMS case and implementing USG FMS contracts and subcontracts are in effect if the LOA and the contract contain all of the information normally required by a license; e.g. identification of exporter, specific service or information to be exported, intermediate consignees, end-use, and end-user. Under 22 CFR Part 126.6, the LOA and the implementing contracts serve as the authorization for the transfers without a license, provided the transaction is fully documented.

C3.4.1. Many disclosures of classified information occur as a result of visual demonstrations or verbal exchanges during meetings or visits. DoD Directive 5230.20 contains standard procedures governing visits, assignments, and exchanges of foreign nationals to the Department of Defense (DoD) and to DoD contractor facilities over which the DoD Components have security responsibility. Approval of a classified visit by a Designated Disclosure Authority is a disclosure decision and constitutes an exemption to the licensing requirements of the ITAR if the visit request or the response to the request fully documents the information to be “exported” (Part 125.5 of the ITAR). With few exceptions, visits and assignments requiring access to classified material are processed through the DoD Foreign Visit System (FVS) of the DoD Security Policy Automation Network (SPAN). One exception is for visits by students under Security Assistance-sponsored training programs where the DD Form 2285, “Invitational Travel Orders (ITO)” provides the necessary security information. Visits are categorized as one-time, recurring, or extended.

C3.4.1.1. One-Time Visit Authorizations. Approval of a one-time visit request permits a single, short-term (normally less than 30 days) visit for a specified purpose.

C3.4.1.2. Recurring Visit Authorizations. A recurring visit authorization permits intermittent visits over a specified period of time to support a Government-approved license, contract or agreement, or other program when the information to be released has been defined and approved for release in advance by the USG.

C3.4.1.3. Extended Visit Authorizations. An extended visit authorization permits a single visit for an extended period of time (beyond 30 days) to support a foreign government contract or joint program (e.g., joint venture, representative to a joint or multinational program), or for a liaison officer, exchange officer, or cooperative program personnel under authorized international agreements. Before any commitment is made to assign a liaison officer to a cleared defense contractor facility in support of the sale of defense articles or services, the assignment must be coordinated with and agreed to by the contractor and the supporting Defense Security Service office in order to fix responsibility for security oversight. The specific terms of the assignment, including security responsibility, should be set forth in the supporting contract.

C3.5.1. Freedom of Information Act (FOIA). Records containing security assistance-related information, including LOAs and FMS procurement contracts, are released in accordance with the Freedom of Information Act, 5 U.S.C. §552 as implemented in DoD 5400.7-R, DoD Administrative Instruction 108, and DoDM 5200.01 Vol. 1, DTM-04-009, and DTM-04-010.

C3.5.1.1. Any request under the FOIA for an LOA or FMS procurement contract should be referred to the appropriate legal counsel of the DoD Component for action. Proposed final decisions to withhold or release, in whole or in part, LOAs already accepted or in preparation must be coordinated with DSCA (Office of General Counsel). The DoD Component need not coordinate an FMS procurement contract with DSCA.

C3.5.1.2. Under FOIA Exemption 4, 5 U.S.C. §552(b)(4), commercial or financial information provided to the USG in confidence by a person (including an agency of a foreign government or a domestic or foreign business) may be exempt from disclosure to the public, if it is the type of information that is not released by the submitter; if disclosure is likely to cause substantial competitive harm to the submitter; if disclosure is likely to impair the ability of the USG to obtain necessary commercial or financial information in the future; or if disclosure will harm other legitimate USG interests. This exemption is intended to protect both the interests of commercial entities that submit proprietary information to the government and the interests of the government in receiving continued access to such data. Such information is to be marked “For Official Use Only” in compliance with DoDM 5200.01 Vol. 1. If the DoD Component determines that it may be required to disclose commercial information obtained from a person, corporation, or foreign government, it should notify the submitter of the information in accordance with DoD 5400.7-R, and E.O. 12600.

C3.5.1.3. Under FOIA Exemption 3, 5 U.S.C. §552(b)(3) and 10 U.S.C. §130c, effective October 1, 2000, information provided by, made available by, or produced in cooperation with, a foreign government or international organization may be withheld from release. DoD Components must ensure the foreign entity has met all of the requirements outlined in the Section 130c in order to justify the withholding of information pursuant to the FOIA.

C3.5.2. Release of Unclassified Information. Except as provided in Section C3.2., unclassified information pertaining to systems for which the purchaser has been authorized release may be provided by the USG to the purchaser country or international organization, as appropriate, for purposes related to security cooperation.

C3.5.3. Foreign Government Information (FGI). Information provided by a foreign government (both classified and unclassified) in confidence is held in confidence. Similar information produced by the USG as a result of a joint arrangement with a purchaser is also held in confidence. DoD 5200.1-R, DTM-04-009, DTM-04-010, provides instructions for protecting such information. FGI is classified in accordance with DoD 5200.1-R, DTM-04-009, DTM-04-010. FGI classification decisions should be honored and under no circumstances modified without the express written consent of the Government that provided the information. Requests for mandatory review for the declassification of FGI are processed in accordance with DoD 5200.1-R, DTM-04-009, DTM-04-010.

C3.5.4. Technical Data.

C3.5.4.1. Definition of Technical Data. The ITAR defines technical data as: information, other than software, that is required for the design, development, production, manufacture, assembly, operation, repair, testing, maintenance, or modification of defense articles. This includes information in the form of blue prints, drawings, photographs, plans, instructions, or documentation; classified information relating to defense articles and services; information covered by an invention secrecy order; and software, as defined in the 22 CFR Part 121.8(f), directly related to defense articles. Technical data does not include information concerning general scientific, mathematic, or engineering principles commonly taught in schools, colleges and universities, or information in the public domain. It also it does not include basic marketing information on function or purpose or general system descriptions of defense articles.

C3.5.4.2. Release of Technical Data. Releasability of technical data is considered in the same manner as other potentially sensitive parts of the program. In accordance with 22 CFR Part 124.2, the release of technical data is limited to the provision of training in basic operations and maintenance of defense articles lawfully exported. This specifically excludes the release of technical data for training in support of intermediate and depot level maintenance. Release in support of intermediate and depot level maintenance must be reviewed to ensure that the Technical Data Package (TDP) does not contain information that can be used for design, development, or production of an item. Controlled Unclassified Information (CUI) may be exempt from public disclosure under 5 U.S.C. §552 (Freedom of Information Act) and must be reviewed in foreign disclosure channels before release to foreign Governments or international organizations.

C3.5.4.2.1. Release of USG-Owned Technical Data. USG-owned TDPs are released under FMS procedures and only in support of a specifically defined, lawful, and authorized USG purpose. The LOA must cover the full cost of preparation, reproduction, and handling of technical data.

C3.5.4.2.2. Release of Privately Owned Technical Data. Foreign representatives normally request release of privately owned technical data through commercial channels subject to export licensing requirements. If DoD Components release such information under a Security Cooperation program, the owner must authorize its release and the data must be properly marked. The LOA must cover the full cost of preparation, reproduction, and handling.

C3.5.4.3. Requests for Technical Data Packages. TDP requests must specify whether the TDP is to be used for operating and maintaining U.S.-origin defense equipment; for study purposes to determine whether to request production authorization; or for production, follow-on development, or improvement of a U.S. defense article, component, or derivation thereof. The LOA must identify the approved purpose for which the TDP is provided. See Appendix 6 for exact note placement and wording.

C3.5.4.4. Restrictive Markings on TDPs. IAs must ensure the TDP includes markings showing the authorized rights, the security classification, and other restrictions or unauthorized uses. Each separate part of the technical information is marked. If individual part marking is not possible, TDP cover information provides the restrictions. DoD Directive 5230.24 and DoD Directive 5230.25 provide DoD policy and procedures for marking and handling export-controlled technical data that are critical technology.

C3.5.4.4.1. Sale of TDPs for Operation and Maintenance (O&M). TDPs are sold for O&M only if the IA verifies that the article was provided to the purchaser through authorized transfer and there is no other viable means of maintaining the U.S.-origin equipment. The IA provides the LOA (or other documentation that validates the authorized transfer of the U.S.-origin equipment) and Table C3.T2. information to the release and disclosure authority for use in making a release determination. If the proposed release involves classified information or CUI, the decision must be approved by a Designated Disclosure Authority appointed pursuant to DoD Directive 5230.11. See Appendix 6 for the wording of a standard note included in LOAs that contain O&M TDPs.

Table C3.T2. Data Sheet for TDPs Transferred for Operations and Maintenance

#	Data Sheet for TDPs Transferred for Operations and Maintenance (O&M)
1	Nomenclature of hardware, major end item, or component, as applicable
2	Major assemblies or components in the TDP having USG patent or other proprietary rights not releasable without prior approval
3	Statement as to whether the TDP requirement could be met by means of pertinent DoD instructions, maintenance manuals, or other similar publications
4	In-country inventory of major end items requiring maintenance support derived from the requested TDP
5	Current status of DoD maintenance capability (e.g., is there an excess depot level capability at the DoD facility?)
6	Estimated date by which USG repair parts support terminates
7	Security classification of the TDP
8	Identification of any classified information or CUI
9	Verification of legal rights to release the TDP for this purpose
10	The DoD Component recommendation on releasing the TDP
11	Copies of pertinent correspondence with purchaser

C3.5.4.4.2. Sale of TDPs for Study or Production. TDPs are offered for study only when DoD is prepared to release the TDP for production. Foreign manufacture of U.S. equipment benefits the United States when it strengthens friendly defense forces, improves U.S. defense relationships, or enhances interoperability. It may also benefit the United States when it serves to maintain the purchaser’s defense industrial base or to improve general defense capabilities. Requests for TDPs for study or production are normally denied if an article is in limited supply or if foreign production would adversely impact the U.S. industrial base. The IA provides the LOA and information (as specified in Table C3.T3.) to the release and disclosure authority for use in making a release determination. If the proposed release involves classified information or CUI, a Designated Disclosure Authority appointed pursuant to DoD Directive 5230.11 must approve the decision. The purchaser can be provided technical data and authority necessary to operate and maintain or manufacture the defense article through an LOA, through an international agreement (such as for cooperative development), or through the combination of an LOA and a complementary international agreement in the form of a Memorandum of Understanding (MOU) or a Memorandum of Agreement (MOA). See DoD Directive 5530.3. See Appendix 6 for the wording of standard notes included in LOAs that contain TDPs for study or production.

Table C3.T3. Data Sheet for TDPs Transferred for Study or Production

#	Data Sheet for TDPs Transferred for Study or Production
1	Nomenclature of defense article to be studied or produced
2	Quantity to be produced by, and production schedule of, the requesting Government
3	Use of article to be produced, with names of third country purchasers if for third country sale
4	Stock on hand; show separately any quantity beyond approved acquisition objective
5	U.S. and foreign production history for last five years
6	Production plans underway approved, and proposed
7	Estimated date by which USG repair parts support terminates
8	Known U.S. source(s) of supply
9	USG cost of the article
10	Security classification of the TDP and of the article to be produced
11	Other countries authorized to produce the article
12	Anticipated impact of TDP sale on U.S., FMS, or other programs
13	Whether production recipients previously obtained the article and quantities obtained
14	Verification of legal rights to release the TDP for this purpose
15	TDP elements having patent or other proprietary rights not releasable without prior approval
16	Whether TDP requirement could be met by maintenance manuals or other publications
17	The DoD Component recommendation regarding release of the TDP
18	Attach copy of pertinent correspondence with purchaser

C3.5.4.4.3. Revisioning Services. After TDPs have been approved for transfer, revisioning services can be offered that provide purchasers updates as TDPs are revised. Revisioning services may appear as a separate line item on the LOA transferring the TDP, or they may be offered on a separate LOA. Revisioning services require a unique LOA note shown in Appendix 6. If previous TDP transfer notes on the case require updating, the revisioning services LOA must contain the complete current provisions required for initial transfer of the TDP.

C3.6.1. Anti-Tamper (AT) Policy Compliance. The USG reserves the right to incorporate AT technologies and methodologies in weapons systems and components that contain Critical Program Information (CPI)* offered under any Security Cooperation Program. In the normal course of system Research, Development, and Acquisition (RDA), the DoD Anti-Tamper Executive Agent (DoD ATEA) approves a final AT plan prior to Critical Design Review (CDR), which is later subject to Validation and Verification (V&V) testing.

* Elements or components of a Research, Development and Acquisition program that, if compromised, could cause significant degradation in mission effectiveness; shorten the expected combat effective life of the system; reduce technological advantage; significantly alter program direction; or enable an adversary to defeat, counter, copy or reverse engineer the technology or capability. DODI 5200.39, 16 July 2008.

C3.6.2. When preparing a response to an LOR for weapons systems or components containing CPI, the IA will coordinate with the DoD ATEA (atexecutiveagent@pentagon.af.mil) to ensure that sensitive technology or program information is defended against unlawful exploitation or loss and that an approved AT plan is in place. The IA must ensure that any necessary AT sustainment mechanisms and associated costs are included in the LOA and certify compliance with AT requirements on the LOA transmittal memorandum forwarded to DSCA for LOA processing.

C3.6.3. An LOA that includes any weapons system or components that contain CPI may not be offered until the DoD ATEA has issued written approval of the AT plan. If an AT plan has not already been established and approved for the system or components containing CPI, the Program Office must submit an AT plan to the DoD ATEA at least 60 days prior to planned offer of an LOA. The IA may not offer the LOA prior to receipt of written DoD ATEA (or designee) approval of the initial plan. Validation and Verification (V&V) testing must be completed 60 days prior to hardware export. Exports of weapons systems or components that contain CPI may not be made until the DoD ATEA has issued final written concurrence of satisfactory V&V testing.

C3.7.1. Missile Technology Control Regime (MTCR). The Missile Technology Control Regime is an informal and voluntary international political arrangement designed to control the proliferation of rocket and unmanned air vehicle (UAV) systems and associated equipment and technology capable of delivering weapons of mass destruction. Although the regime is a political commitment rather than a treaty with international legal obligation, many countries, including the United States, have passed laws restricting the export of MTCR-controlled items. See Arms Export Control Act (AECA), Chapter 7.

C3.7.1.1. MTCR Screening Process. Regime controls are applicable to all items on the MTCR annex as listed in 22 CFR Part 121.16. The DoS, DoC, and DoD each has a role in regulating the export of MTCR-controlled items from the United States. DoD identifies MTCR-controlled items that purchasers have requested via FMS. To ensure technical reviews are standardized, reviewers must complete a DSCA-approved Missile Technology Proliferation Course. IAs maintain a roster of personnel trained and/or knowledgeable on MTCR controls to be updated and provided quarterly to DSCA (Programs Directorate).

C3.7.1.1.1. Upon receipt of an LOR, prior to LOA development, the System Program Office (SPO), Program Manager (PM), or equivalent will perform a technical review of each LOA to identify MTCR-controlled items contained in the LOA or envisioned to be part of the associated program. (Special reporting requirements apply to bulk compounds (Item 4) and fuses (Item 2.A.1.f.))*

*The reviewer must report the compounds listed in Item 4 of the MTCR Annex if they are to be exported in bulk or in any other manner or form that might support the creation of a propellant for a missile or a UAV. However, the reviewer is not to report Item 4 explosive compounds if they are molded or poured into a form that precludes their use as rocket propellant (e.g., as a bursting, propelling, or gas generating charge in a shell, cartridge, squib, or actuator). Even though all fuses meet the criteria of Item 2.A.1.f. in the MTCR Annex (i.e., “weapon or warhead safing, arming, fusing and firing mechanisms...”), the reviewer is not to report any common type munitions fuse as a possible MTCR controlled item unless the fuse in question is of an unusual type, a rough equivalent of which is not likely to be found in most foreign arsenals, or unless the fuse uses sophisticated means (e.g., radar) to determine burst height.

C3.7.1.1.2. The reviewer transmits a list of the MTCR-controlled items to the IA MTCR point of contact (POC) at the earliest opportunity to ensure minimal delays in the LOA processing time. This list includes: the case identifier; a general case description identifying major associated systems; the Military Articles and Services List (MASL) number of each MTCR-controlled item; the MTCR Annex Category and item identifier, the nomenclature of each item; and a detailed description of each item including the manufacturer.

C3.7.1.1.3. The IA MTCR POC verifies the list and forwards it via memorandum by email to DSCA (Programs Directorate, Weapons Division) at mtcr@dsca.mil. The memorandum should include the name, telephone and fax number, and e-mail address of the IA MTCR POC.

C3.7.1.1.4. DSCA (Programs Directorate, Weapons Division) reviews and forwards the memorandum to the DoS, Deputy Director, Office of Chemical, Biological, and Missile Threat Reduction, Bureau of International Security and Nonproliferation (ISN/MTR), for review and approval. DSCA will relay DoS’s reply to the IA and Case Writing Division.

C3.7.2. MTCR Category I ISR UAVs/UCAVs. Below list is not inclusive.

RQ-1/MQ-1 Predator MQ-9 Reaper RQ-4 Global Hawk Broad Area Maritime Surveillance (BAMS) Sky Warrior NATO Alliance Ground Surveillance (NATO AGS)

C3.7.2.1. USG policy stipulates a “strong presumption to deny” the transfer of MTCR Category I ISR UAVs/UCAVs. If the SCO becomes aware that the host country is considering submission of an LOR for an MTCR Category I ISR UAV or UCAV prior to development and submission of an LOR for such a system, the SCO should initiate a requirements analysis and pre-screening. This process begins with a Security Cooperation Organization Assessment (SCOA) providing all elements of information in Table C3.T4. below. In the preparation of the SCOA, the SCO should consult and confer with the IAs, including the IA’s Foreign Disclosure Office; the Country Team; and the Combatant Command (CCMD). When complete, the SCOA will be forwarded to the CCMD for comment on each of elements 1-17 addressed in the SCOA in a subsequent CCMD Comment (CC). The SCOA and the CC should be forwarded to the Joint Staff/J5 and DSCA. This process forms the basis for a collaborative effort, to analyze the recipient nation’s military requirements in order to identify a platform/payload combination (manned aircraft, Cat II UAV/UCAV, or Cat I UAV/UCAV) that fulfills those requirements and complies with the MTCR and other USG security requirements. If the SCO is not able to develop the SCOA in advance of submission of an LOR for an MTCR Category I ISR UAV or UCAV, SCOA required information should be submitted as part of the Country Team Assessment (CTA). See Table C5.T1b.

Table C3.T4. MTCR Category I ISR UAV or UCAV
Security Cooperation Organization Assessment (SCOA)

#	Required Information
1	What are the military requirements and operational intentions or plans for the ISR UAV/UCAV that might be requested, to include: Description of the primary mission and secondary missions for the ISR UAV/UCAV? Extent of anti-terrorist, border patrol/ coast guard, and/or humanitarian missions for the UAV/UCAV(s) endorsed.
2	Specify performance characteristics of the desired air vehicle in terms of range (km), payload (kg), payload performance parameters or desired capabilities, altitude ceiling (ft), flight endurance (hrs). Are there any desired modifications or changes to the basic configuration for the desired air vehicle or payload?
3	How the ISR UAV or UCAV would affect the military capabilities of the proposed recipient, including the ability of the recipient effectively to field, support, and appropriately employ the system in accordance with its intended end-use.
4	How the ISR UAV or UCAV would contribute to U.S. strategic and foreign policy goals.
5	Justification for number and type of ISR UAV/UCAV that might be requested with an explanation of how the quantity endorsed is the minimum required consistent with the legitimate military requirements of the recipient. What is the estimated or approximate monthly number of sorties and flight hours? Where will the ISR UAV/UCAVs be based?
6	What are the communications resources that the recipient nation would utilize to support its ISR UAV/UCAV flight operations? Does the recipient nation require beyond line-of-sight flight operations? Will air-ground communications and/or data transfer require encryption?
7	If applicable, would the ISR UAV/UCAV fulfill or contribute to NATO force goals?
8	Explain why an MTCR Category I ISR UAV or UCAV would fulfill the requirements and a manned aircraft or non-MTCR Category 1 ISR UAV or UCAV cannot.
9	Is this the first introduction of this system/capability to the recipient/region?
10	Anticipated reactions of neighboring nations to the introduction of the ISR UAV/UCAV capability into the region.
11	Analysis of how the proposed sale would affect the relative military strengths of countries in the region and of the impact of the proposed sale on U.S. relations with the countries in the region.
12	Extent of military interoperability missions/training with U.S. Forces?
13	The availability of comparable systems from foreign suppliers.
14	Assessment of the nation’s ability to account for, safeguard, operate, maintain, and support the ISR UAV or UCAV. What is the nation’s maintenance concept? Two level? Three level? Does the nation expect it will provide depot level repair or will it elect contractor provided depot level maintenance? What level of repairable stocks does the nation anticipate it will require?
15	A plan for end-use monitoring for sensitive and advanced war fighting technology and the SCO’s plan for compliance verification.
16	Training required either in-country or in the United States and anticipated reactions resulting from the presence of U.S. trainers in-country. How many pilots, sensor operators, and maintainers will it need to be trained either in-country or in the United States? Approximately when, if elected, the nation needs to commence/end U.S.-based training? Will the nation need in-country flight simulators? If so, how many? Will the nation need to participate in related USAF/ISN UAV user-groups, forums, or other USAF/USN programs concurrent with adopting a U.S. UAV.
17	Possible impact of any in-country U.S. presence that might be required as a result of providing the ISR UAV or UCAV.
18	Is the potential recipient a: Member of NATO? MTCR Partner? Signatory to the Nuclear Non-Proliferation Treaty? Signatory to the Chemical Warfare Convention? Signatory to the Biological Weapons Convention?
19	Has the SCO consulted with the Foreign Disclosure Office of the FMS Implementing Agency regarding the need for disclosure of information actions in regard to a potential transfer of a Category I ISR UAV/UCAV? Yes/No
20	Any additional information in support of, or that would recommend against, the transfer request.

C3.7.3. Command, Control, Communications, Computer, Intelligence, Surveillance and Reconnaissance (C4ISR).

C3.7.3.1. C4ISR Definition. C4ISR encompasses systems, procedures, and techniques used to collect and disseminate information. It includes intelligence collection and dissemination networks, command and control networks, and systems that provide the common operational/ tactical picture. It also includes information assurance products and services, as well as communications standards that support the secure exchange of information by C4ISR systems. Under the C4ISR umbrella, systems exchange digital, voice, and video data to appropriate levels of command. The two key aspects of C4ISR systems are access to secure networks controlled by Information Security (INFOSEC) products and services, and the classified data resident in the C4ISR networks. See CJCSI 6510.06B (not for public release) for information on the release of U.S. INFOSEC products (Communications Security (COMSEC), cryptographic algorithms, cryptographic key material, security infrastructure) to foreign purchasers. Transfers of U.S. C4ISR capabilities to countries and international organizations must support a U.S. Combatant Commander’s (CCDR) interoperability requirements or otherwise clearly benefit U.S. objectives. A purchaser’s desire to be interoperable with the United States is insufficient justification for release. A purchaser must obtain approval from the supporting CCMD for access to classified U.S. C4ISR and INFOSEC prior to submitting a Letter of Request (LOR) for C4ISR. Pre-LOR coordination activities will take place between the requesting foreign purchaser (via SCO in country or Embassy in the United States) and DSCA (Programs Directorate). See Section C3.3.4. Prior to physically receiving any U.S. INFOSEC products or services associated with a secure C4ISR system, the purchaser must negotiate and sign a Communication Interoperability and Security Memorandum of Agreement (CISMOA) or other INFOSEC agreement (e.g., COMSEC MOU, INFOSEC Equipment Agreement) with the CCMD.

C3.7.3.1.1. C4ISR Responsibilities. Table C3.T5. lists organizations and their C4ISR responsibilities.

Table C3.T5. C4ISR Responsibilities

Organization	Responsibility
Security Cooperation Organization	Informs host country of the requirement for NATO or CCMD sponsorship of requests for INFOSEC-enabled C4ISR systems Coordinates pre-LOR C4ISR requirements with CCMD and DSCA (Programs Directorate through Operations Directorate) Forwards LOR after pre-coordination to Implementing Agency
Purchaser	Signs bilateral CISMOA or other binding INFOSEC agreement Coordinates with SCO on pre-LOR C4ISR requirements Submits LOR for a dedicated INFOSEC facility and staffing by two U.S. accredited COMSEC custodians to Implementing Agency. See Section C3.7.3.2.6.
U.S. Combatant Commander	Establishes interoperability requirement for specific C4ISR capabilities requiring INFOSEC products and services Initiates CJCSI 6510.06 INFOSEC release process Following delegation from the Chairman, Joint Chiefs of Staff, negotiates and signs the CISMOA or other appropriate bilateral INFOSEC agreement governing the transfer of INFOSEC products and services to non-NATO nations, excluding Australia and New Zealand
DSCA	DSCA (Operations and Programs Directorates) reviews C4ISR pre-LOR requirements in coordination with NSA and CCMD, and, as appropriate, assigns the lead Implementing Agency Monitors planning activities
Implementing Agencies	Receive and review C4ISR LORs after pre-LOR review by DSCA Obtain DSCA (Operations Directorate) approval before processing LOR Generate Price and Availability (P&A) data and/or FMS case
National Security Agency (NSA)	Identifies the appropriate INFOSEC solution to satisfy CCMD validated interoperability requirements Delegates authority through the Joint Chiefs of Staff to the CCMD to negotiate the COMSEC portion of the CISMOA, or to negotiate INFOSEC Equipment Agreements Generates FMS case for foreign purchase of U.S. INFOSEC products and services; under limited circumstances, provides written authority to MILDEPs to include specific INFOSEC products and services on Military Department FMS cases. See National COMSEC Instruction (NACSI) 6001 (not public).
Chairman, Joint Chiefs of Staff	Validates CCMD interoperability requirements associated with the requests for U.S. INFOSEC products and services Delegates final authority to CCMD to negotiate and conclude the CISMOA

C3.7.3.2. C4ISR Release Process.

C3.7.3.2.1. Release of Classified Military Data. Interoperable systems that exchange classified military information are subject to a releasability review and approval as defined in NDP-1. In addition to classified system hardware and software information, all data flowing between foreign and secure U.S. C4ISR systems are classified. Approvals for release of U.S. classified data flowing over secure coalition networks are required before issuance of LOA and/or P&A data. See Section C3.6.

C3.7.3.2.2. INFOSEC Release. The release process for INFOSEC products is defined in CJCSI 6510.06B. INFOSEC releases to non-NATO nations (excluding Australia and New Zealand) are limited to specific quantities in support of a specific interoperability requirement with the exception of GPS/PPS and IFF Mode 4 releases, which are not limited to a specific quantity or platform. Once GPS/PPS and IFF Mode 4 devices are approved for release, the purchaser may obtain them through National Security Agency-authorized channels.

C3.7.3.2.3. INFOSEC LOAs. The Director, National Security Agency, (DIRNSA) is the National Manager for INFOSEC products to include both external COMSEC equipment and embedded cryptographic modules. The IA for COMSEC and embedded cryptographic modules is determined by the Acquisition Manager of a particular device. DIRNSA may allow some NSA-managed INFOSEC materiel to be included on other IA managed LOAs due to urgent operational requirements, end of fiscal year funding issues, etc. Requests for exceptions to allow NSA-managed INFOSEC materiel on other IA LOAs will not be granted due to the lack of an existing NSA LOA or to avoid the Small Case Management Line. Special Purpose INFOSEC equipment (“S” Type COMSEC) will be provided to Non-NATO Nations on NSA-managed FMS cases only. Requests to allow “S” Type COMSEC equipment on other IA LOAs will not be granted.

C3.7.3.2.4. INFOSEC Validation/Authorization. All IAs, even those responsible for the acquisition of the INFOSEC equipment and embedded cryptographic modules, must request DIRNSA determination as to whether INFOSEC equipment and embedded cryptographic modules are releasable and whether they can be included on an LOA written by an IA other than NSA. Requests must include a copy of the purchaser’s LOR, nomenclature of the INFOSEC and/or embedded cryptographic modules, quantities, and identify the weapon system or platform in which the INFOSEC equipment will be integrated. DIRNSA will provide a written response to the IA within 30 days of the request. Some responses may include special instructions for INFOSEC materiel that requires special handling.

C3.7.3.2.5. Classification of INFOSEC. The association of a specific INFOSEC product with a foreign government may be classified; however, classifying the entire FMS case will be avoided, when possible. See Section C5.4.10. for more information on classified FMS cases.

C3.7.3.2.6. INFOSEC Accounts, Facilities, and Custodians. C4ISR purchasers may be required to establish a dedicated INFOSEC account and purchase an INFOSEC facility manned by two U.S.-accredited INFOSEC custodians. The CCMD determines whether an INFOSEC account is required during the negotiation phase of the CISMOA with the purchaser. NSA and the CCMD may assign additional duties to INFOSEC custodians.

C3.7.4. Electronic Warfare (EW) Systems and EW Integrated Reprogramming Database (EWIRDB).

C3.7.4.1. Definition. EW Systems (e.g., radar warning receivers and jammers) are designed to deny or counteract the enemy's use of electromagnetic (EM) emitters (e.g., radar, communications, guidance, detection, and control devices). The sale of an EW capability involves the transfer of the EW system hardware, firmware, and software. The software typically includes a mission data file (MDF) or library that contains information/data related to EM emitters. The EWIRDB is the primary DoD source for technical parametric performance data on EM emitters and is used to program/reprogram the MDF to correctly identify emitters by their EM characteristics. Prior to offering an LOA to the FMS customer that includes an EW system, the FMS IA must review all EW system components to verify that the system, to include the MDF, has been approved for release and certified in writing by the appropriate DoD authorities (i.e. National Security Agency (NSA), National Air and Space Intelligence Center (NASIC), Defense Intelligence Agency (DIA), and applicable program offices). If an EW system is not certified in writing prior to sale, the FMS purchaser must be advised and the FMS IA must ensure a plan is in place to obtain data protection certification from the NSA prior to delivery. Delivery cannot take place without this certification unless the FMS customer uses its own technical parametric performance data instead of DoD data.

C3.7.4.2. FMS EWIRDB Types. The FMS EWIRDB is used to create the MDF or library for EW systems. There are two types of FMS EWIRDB, Direct and Indirect. A Direct FMS EWIRDB is delivered directly to the FMS customer and provides data required for an In-Country Reprogramming (ICR) capability for the EW system. An Indirect FMS EWIRDB is delivered to the U.S. reprogramming facility that will develop the MDF for the requesting country’s EW system. Both Direct and Indirect EWIRDBs must go through the release processes described below prior to the FMS sale.

C3.7.4.3. EW Release Process. An LOR advisory should be issued to NSA and the applicable MILDEPs by DSCA (Operations Directorate) when an LOR is received for an EW system that will be used on a country’s weapon system for the first time. This advisory will notify the EW community of the pending request so that the evaluation process can begin. It is critical that the evaluation process be initiated as soon as possible due to the amount of time required to complete the process. Table C3.T6. lists organizations and their EW responsibilities.

Table C3.T6. EW Responsibilities

Organization	Responsibility
DSCA	Prepares LOR Advisory for potential sale of EW system Reviews LOA prior to offer to ensure appropriate reviews have been accomplished
Implementing Agencies	Provides copy of LOR to DSCA with details on what EW system will be proposed for potential platform sale, to be used for LOR advisory Determine if proposed EW system has been certified by NSA for handling of classified data Incorporate required EW costs and program schedule impacts into LOA; advise purchaser of certification status and potential schedule risks and impacts Reviews LOA and verifies appropriate reviews have been accomplished prior to being offered to customer
Implementing Agency EW Points of Contact Air Force (Deputy Under Secretary of the Air Force for International Affairs Regional Weapons Division) (SAF/IARW) Army (Deputy Assistant Secretary of the Army for Defense Exports and Cooperation) (SAAL-NI) Navy (Navy International Programs Office Strategic Planning Directorate) (Navy IPO-03)	Process any required disclosure requests for applicable classified military information Work with program office and vendor to develop technical documentation required for evaluation of EW systems data protection Evaluate requirement to determine if Release in Principle (RIP) has been granted for a particular system. If not, submit request for RIP to DIA, NSA and SIGCOM for approval/authorization Upon LOA signature work with purchaser as applicable to identify data base requirements and submit request for Release in Specific (RIS) to DIA, NSA and SIGCOM for approval/authorization Validate that LOA is written appropriately to incorporate specific EW verbiage.
Defense Intelligence Agency (DIA)	Review and process Service requests for EW system RIP and RIS
National Security Agency (NSA)	Review and process Service requests for EW system RIP and RIS Review and provide guidance for data protection certification for EW systems
National SIGINT Committee (SIGCOM)	Review and process Service requests for EW system RIP and RIS
Purchaser	Upon LOA signature participate in dialog with IA FMS offices to identify required data to be included in EW data base

C3.7.4.3.1. Release of Classified Military Information. EW systems that use classified military information are subject to a releasability review and approval as defined in the NDP-1. In addition to possible classified system hardware and software, the system MDF may include classified data. Approvals for release of U.S. classified data are required before an LOA can be offered to a purchaser.

C3.7.4.3.2. FMS EWIRDB Release in Principle. Prior to offering an LOA for FMS EWIRDB support, there must be an approved and valid Release in Principle (RIP) in place for the use of the Direct or Indirect FMS EWIRDB. The FMS EWIRDB RIP is issued by NSA for a particular country on a specific weapon system platform, and is not related to a COMSEC RIP. Once the IA Program Office or vendor determines there is an FMS EWIRDB requirement, a request for a RIP should be submitted to the appropriate IA EW point of contact listed in Table C3.T4. The IA will designate a point of contact for receipt of these requirements to ensure consistency in the submissions to the DoD authorities. The request for a RIP will be submitted to the DoD disclosure authorities (Table C3.T4.). At a minimum, these requests will identify the requesting country, platform, type of database (Direct/Indirect) and EW system nomenclature, if known. Once the RIP is granted, an LOA for FMS EWIRDB support can be offered to the purchaser. The IA should enter comments in Defense Security Assistance Management System (DSAMS) case remarks stating that an EW RIP has been granted, citing the approving agency, date of grant, and point of contact.

C3.7.4.4. FMS EWIRDB Release in Specific. Upon acceptance by the customer of an LOA for an EW system with FMS EWIRDB support, the IA EW point of contact will coordinate with the country to determine the desired data to be incorporated into the FMS EWIRDB. This information, along with the identified recipient country, platform, type of database (Direct/Indirect) and EW system will be used by the EW points of contact at the applicable IA to develop a request for a Release in Specific (RIS). The RIS will be submitted to the DoD disclosure authorities for approval. If approved, the RIS will authorize the EWIRDB executive agent, NASIC, to begin the development of an FMS EWIRDB for a particular country, platform, and EW system as funded by an FMS LOA. Table C3.T4. lists organizations and their EW responsibilities.

C3.7.4.5. LOA Requirements. All LOAs that offer EW systems and/or data base support must clearly identify, in the LOA notes, the nomenclature of the EW system components, the type of data base support being provided and the platforms associated with the EW system and/or data base support. The LOA notes must clearly state if an EW system is not certified prior to the LOA being offered.

C3.7.4.6. Identification, Friend or Foe (IFF) Systems. IFF systems are sensitive identification devices that emit signals used to identify whether a platform is friend or foe and thereby prevent fratricide. See DSCA Policy Memo 11-40.

C3.7.4.7. IFF Release Requirements. Release of IFF Mode 4 capability to foreign governments must be handled according to the COMSEC release process of CJCSI 6510.06B, Communications Releases to Foreign Nations, March 31, 2011 as described in Section C3.7.3.1. IFF Mode 4 is typically approved on a general release basis, which means it is not tied to a specific quantity or platform. Transfers of dual IFF Mode 4/5 (Mark XIIA) systems are based on validated interoperability requirements. Any dual IFF Mode 4/5 systems sold will initially, provide IFF mode 4 operational capability only. Table C3.T7. lists organizations and their release coordination responsibilities.

Table C3.T7. IFF Release Coordination Responsibilities

Organization	Responsibility
DSCA	Review LOA prior to offering, to ensure appropriate reviews have been accomplished and approvals are in place.
Implementing Agencies	Prior to offering an LOA for IFF Mode 4 or 5, request approval from NSA to sell associated COMSEC equipment. Upon identification of appropriate IFF system for platform, ensure DoD AIMS PO has certified the IFF system prior to delivery.
National Security Agency (NSA)	Review and process COMSEC release requests in accordance with applicable release processes. Provide "approval to sell" letters to Implementing Agencies (IA) for IFF COMSEC devices. Provide IFF Mode 5 test key, as required.
DoD AIMS PO	Evaluate systems to determine whether they comply with relevant standards; certify those that do.
Purchaser	Nations National Distribution Authority (NDA) or COMSEC custodians should request COMSEC keying materiel from the controlling authority, i.e., Joint COMSEC Management Office (JCMO), McDill Air Force Base, FL.

C3.7.4.7.1. IFF systems that use classified military information are subject to a disclosure review and approval as defined in the NDP-1. Per NDP-1, approvals for release of U.S. classified data are mandatory before an LOA can be offered to a purchaser.

C3.7.4.7.2. IFF Mode 4 Keying Materiel is obtained by COMSEC Accounts from the Controlling Authority. The Controlling Authority for the IFF Mode 4 is the Joint COMSEC Management Office (JCMO). Until IFF Mode 5 is in operational use, only the Mode 5 test key will be available. An IFF Mode 5 test key must be obtained through the National Security Agency. The procedure for release of IFF Mode 5 operational key will be determined once IFF Mode 5 is in operational use by U.S. forces.

C3.7.4.7.3. The DoD AIMS PO is responsible for ensuring Mark XIIA systems meet the interoperability requirements described in the DoD AIMS 03-1000 series standards. Prior to transfer of IFF Mode 5 or dual Mode 4/5 systems, the IA must ensure the system has been certified for interoperability by the AIMS PO.

C3.7.4.7.4. All LOAs for the provision of IFF Mode 4 or 5 systems must clearly identify the IFF system components in an LOA note. The LOA notes should also clearly state whether or not an IFF system has been certified as meeting AIMS standards, to ensure the FMS customer is aware of the certification status.