Attachment 0012 - DD254 CONTRACT SECURITY CLASSIFICATION SPECIFICATION.pdf

Please wait...

If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.

You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.

For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Attachment A Page 1 of 11

JPEO Armaments & Ammunition Attachment A (JPEO AA-21-007-S)

SOLICITATION NUMBER: W52P1J-21-R-0005

Attachment DD254, Block 13 Continuation Sheet:

SECURITY GUIDANCE

Ref 10a: Communications Security (COMSEC): Classified COMSEC material is not releasable to contractor employees who have not received a FINAL clearance at the appropriate security level.

COMSEC access shall be IAW DoD 5220.22-M. Written concurrence of the GCA is required prior to subcontracting. Access to COMSEC material and/or equipment will be required in the performance of this contract. In addition to the DoD 5220.22-M, contractor shall also follow guidance outlined in AR 380-40. When access is required at Government facilities, contractor personnel will adhere to COMSEC rules and regulations as mandated by Command policy and procedures.

The prime contractor must submit a written request (on company letterhead) to the Contracting Officer (PCO) for authorization to grant COMSEC access to a subcontractor. The request must be approved by the PCO prior to prime contractors granting subcontractor access to COMSEC.

Ref 10j and Ref 11l: Controlled Unclassified Information (CUI) generated and/or provided under this contract shall be safeguarded and marked as specified in DoD Instruction 5200.48. See Block 13 Continuation Sheet Security Requirements Attachment additional CUI guidance.

Ref 11c: The contractor requires access to classified information. Any extracts or use of such data requires the contractor to apply derivative classifications and markings consistent with the source documents. Use of “Multiple Sources” on the “Derived From” line necessitates compliance with the NISPOM, paragraph 4-208a, and the use of a bibliography. Contractor will follow the guidelines of Chapters 4 and 5 of the NISPOM for the proper handling of classified information and DoDM

5200.01 for marking guidance of classified information. Contractor will also follow the guidance set forth within Security Classification Guide(s) (SCG) identified in the DD 254. The contractor requires access to classified source data up to and including (Secret) in support of the work effort.

Ref 11d: Contractor must provide adequate storage at their facility for classified material and/or hardware to the level of required safeguarding (See Block 1b above). (SECRET).

Ref 11h: A COMSEC account must be established when accountable COMSEC material is to be provided, acquired, or produced under a contract. The GCA will inform the contractor that a COMSEC account is required. Contractor will require a NSA COMSEC Account. Accountable COMSEC information/material will be processed IAW the NISPOM and NSA Policy/Procedures.

COMSEC custodians are DA civilians or military members. Contractors are considered hand receipt holders. See AR 380-40 for further guidance on COMSEC. The prime contractor must submit a written request (on company letterhead) to the Contracting Officer (PCO) for authorization to grant COMSEC access to a subcontractor. The request must be approved by the PCO prior to prime contractors granting subcontractor access to COMSEC. The prime contractor must notify the NSA Central Office of Record before negotiating or awarding subcontracts.

Ref 11j: The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, to be reviewed and approved by the responsible Government

Attachment A Page 2 of 11

OPSEC officer, per AR 530-1, Operations Security. This SOP/Plan will specify the government’s critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. In addition, the contractor shall identify an individual who will be an OPSEC Coordinator. The contractor will ensure that this individual becomes OPSEC Level II certified per AR 530-1. Training can be received from either the Army OPSEC Support Element (OSE) or the Interagency OPSEC Support Staff (IOSS). Per AR 530-1, Operations Security, new contractor employees must complete Level I OPSEC training within 30 calendar days of their reporting for duty. All contractor employees must complete annual OPSEC awareness training. Enclosure 1 of this Attachment provides guidance regarding the format of the OPSEC plan. The contractor shall deliver an OPSEC SOP/Plan to the COR for review and approval by the responsible Government OPSEC officer.

Ref 11k: The PCO and/or the COR will obtain written approval from the Commander, Defense Courier Service (DCS), ATTN: Operations Division, Ft. George Meade, MD 20755-5370, in order to impose this requirement on the contractor. DCS Accounts will be handled IAW DoD 5200.33, Defense Courier Service Regulation. Only certain classified information qualifies for shipment by DCS. Information regarding the establishment of an account can be found in the U.S.

Transportation Command Defense Courier Division Customer Service Guide:

https://www.ustranscom.mil/cmd/associated/dcd/files/Customer_Service_Guide_Feb_2016.pdf.

The contractor will abide by requirements outlined in the Service Guide regarding contractor accounts. Prior written approval from the PCO is required before a prime contractor can authorize a subcontractor to use the services of DCS.

Ref 11m: Access to Automated Information Systems (AIS). IAW AR-25-2, AR 380-67 and affiliated regulations, if access to AIS is a requirement, a favorable investigation is required to access the Cognizant Mainframe Systems and all Local Area Network Server Accounts. Interim access prior to the completion of investigations will be considered on a case-by-case basis. The COR and/or AOR and the Cognizant Security Office will make interim access determinations.

Additional Training Requirements:

Antiterrorism Training. All contractor employees requiring access to any Federally-controlled facility and logical access to Federally controlled information systems except for national security systems as defined by 44 U.S.C. 3542(b)(2), shall be certified in Level 1 Anti Terrorism Training.

The training is accessible from any computer with access to the World Wide Web and is available at https:/atlevel1.dtic.mil/at. The contractor is responsible for ensuring that the training has been satisfactorily completed within 30 calendar days after contract award and that valid certificates of completion have been submitted to the Contracting Officers Representative (COR) with a copy furnished to the Contracting Officer. The Certificates are valid for one year; therefore, training shall be completed every year for the duration of the contract. AT level I awareness training is available at the following website: http://jko.jten.mil/courses/atl1/launch.html.

Access to Government Information Systems. All contractor employees with access to a government information system shall be registered in the Army Training Certification Tracking System (ATCTS) at the commencement of any services, and shall successfully complete the DoD https://www.ustranscom.mil/cmd/associated/dcd/files/Customer_Service_Guide_Feb_2016.pdf http://jko.jten.mil/courses/atl1/launch.html

Attachment A Page 3 of 11

Information Assurance (IA) awareness training before issuance of network access and annually thereafter.

iWATCH Training. The contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days after contract award and within 30 calendar days of new employees commencing performance. The contractor is responsible for ensuring that the training has been satisfactorily completed with the results reported to the COR.

Threat Awareness Reporting Program (TARP). Per AR 381-12, contractor employees must receive mandatory TARP training within thirty (30) days of employment and annually thereafter. Only TARP training by a CI agent is authorized unless the conditions in paragraph 2-4i apply. In addition, contractors will report threat-related incidents, behavioral indicators and other matters of CI interest specified in AR 381-12, Chapter 3.

Attachment A, Enclosure 1 Page 4 of 11

JPEO Armaments & Ammunition Attachment A (JPEO AA-21-007-S)

Attachment DD254, Block 13 Continuation Sheet:

SECURITY GUIDANCE

Enclosure 1 – OPSEC Plan Format

I. COVER PAGE

The cover page for an OPSEC Plan shall clearly present, at a minimum, the following information:

1. Title of the Acquisition Program

2. Title of the Document (i.e. “Operations Security Plan”)

3. Reference to the government contract number

4. Date of latest revision

5. Name, signature and title of the preparer of the OPSEC Plan

6. Name, signature and title of the approver of the OPSEC Plan

7. Reference for whom the document was prepared (Contracting activity)

8. Reference by whom the document was prepared (Corporation)

9. All appropriate distribution or classification statements

II. TABLE OF CONTENTS PAGE

The Table of Contents for an OPSEC Plan shall outline each section contained in the OPSEC Plan.

III. PREFACE PAGE

The purpose of the Preface is to provide a brief, unclassified, overview of the program and the need for OPSEC measures. The specific objectives of the contracted effort shall be introduced with reference to all strategic participants and partnerships required to make the program a success. The anticipated development of any innovative concepts or technologies shall also be introduced in the Preface.

The Preface shall reference all links between the OPSEC Plan and any corporate OPSEC Program(s).

The Preface may conclude by referencing requirement documents such as the contract number, Contract Security Classification Specification (DD254), Contract Data Requirements List (DD1423) and any other pertinent guidance provided by the contracting activity. It shall also provide an OPSEC point of contact, with contact information, for additional guidance or assistance such as the OPSEC program manager or contractor program manager.

IV. OPSEC PLAN INTRODUCTION

Purpose and Scope: The purpose of the OPSEC Plan shall be effectively communicated in this section and include a description of the scope of the OPSEC Plan (unique physical locations, subcontractors, suppliers, period of performance, etc.).

Authorities: The requirement to protect critical information shall be documented within this section.

Documenting the requirement can be achieved by referencing the Corporate OPSEC Program (Policy) and Plan, DODM 5205.-2M, specific contract documents including the DD254 for contracts involving classified data, or other contracting activity specific guidance.

Attachment A, Enclosure 1 Page 5 of 11

OPSEC Plan Major Activity Timeline: This section shall include a list of all major OPSEC Plan activities such as quarterly OPSEC Working Group Meetings, Annual Assessments, scheduled OPSEC awareness training, Sub-contractor OPSEC Assessments and Surveys, Threat and Vulnerability Reviews, etc. This section shall also include scheduled OPSEC Plan reviews.

Responsibilities: The OPSEC Plan shall identify who is responsible for the major activities described in the Plan. For example (not intended as an inclusive The OPSEC Officer shall be identified by name and include a list of duties that may include:

1. Coordinate all OPSEC policy responsibilities/ procedures within the program

2. Revise the Program OPSEC Plan as necessary

3. Convene and coordinate the annual Program OPSEC Assessment

4. Disseminate updated threat information to program personnel

5. Assist in the review of contract requirements for OPSEC considerations

6. Conduct OPSEC Training IAW AR 530-1, Chapter 4.

7. Achieve OPSEC Level II certification

8. Develop/Disseminate Program Critical Information List (CIL)

9. Promote OPSEC awareness within the program

A short description of the expectations and responsibilities of all program personnel (including subcontractors and suppliers) shall be provided and may typically include:

1. Remain compliant with all applicable OPSEC Plans

2. Maintain an awareness of all applicable CIL

3. Attend all OPSEC program briefings

4. Timely reporting of any OPSEC concerns to the Contractor Program Manager and/or the

Program OPSEC Manager

5. Generation of OPSEC Plans (sub-contractors or suppliers only)

Organizational OPSEC Communications and Interfaces: A description as to how the OPSEC Plan will be communicated to all personnel supporting the program (hardcopy, via a webpage, briefings, etc.)

Marking, Handling and Distribution of Documents: This section shall provide a description of marking, handling, storage, access and transmission authorizations and procedures for any critical information provided to, or generated by, the contractor. Reference to the program classification guide, Freedom of Information Act and any additional guidance provided by the contracting activity may be cited as applicable.

V. CRITICAL INFORMATION

General: Critical information shall be identified within this section of the plan and a comprehensive program Critical Information List (CIL) shall be included.

Critical Information List: Guidance on the creation of a CIL is contained within “Applying OPSEC to Government Acquisitions and Contracts,” available at https://www.iad.gov/ioss/, AR 530-1, DODM 5205.02M, or may be provided by the contracting activity. Ideally the CIL shall remain unclassified to facilitate wide internal distribution, but may provide reference to classified information as applicable

VI. THREAT

General Threat: This section shall identify and demonstrate an understanding of the overall threat to https://www.iad.gov/ioss/

Attachment A, Enclosure 1 Page 6 of 11 program critical information throughout the anticipated duration of the contract/program. The section shall conclude with a brief description of all identified intelligence/information collection methods that may be expected to be used by an adversary or competitor to acquire Critical Information. Note:

For current information see, “Targeting US Technologies: A Trend Analysis of Cleared Industry Reporting.” You can also contact your local FBI field office for relevant information.

Program Detailed Threat: This section shall be similar to section above referencing any known direct threats to acquisition specific elements of critical information within the program/contract. As complete a description of each threat as possible shall be provided while maintaining the overall plan classification at the unclassified level.

Threat Analysis: Each threat identified in above sections shall be analyzed to determine the level of threat to the corresponding critical information. The results of this analysis shall be presented in this section. A description of the specific threat analysis method used by the contractor to quantify each threat shall be included in this section. Note: For additional guidance and a sample threat analysis methodology see, “Applying OPSEC to Government Acquisitions and Contracts” at https://www.iad.gov/ioss/ and DODM 5205.02.

VII. VULNERABILITIES

General: The Vulnerability section of the OPSEC Plan shall describe the analysis of activities (indicators) that point to OPSEC vulnerabilities an adversary can exploit to acquire critical information. This section shall contain a list of all identified OPSEC vulnerabilities.

List of OPSEC Vulnerabilities: All vulnerabilities shall be described in sufficient detail as to communicate to the contracting activity the extent of the vulnerability. The Vulnerability List shall remain unclassified. Note: A list of typical OPSEC vulnerabilities which may require OPSEC measures may be found within “Applying OPSEC to Government Acquisitions and Contracts”, available at https://www.iad.gov/ioss/. These sample vulnerabilities are not all inclusive and the submitted vulnerability list shall be tailored to the specific acquisition or contract.

Vulnerability Analysis: Once potential program vulnerabilities have been identified, the magnitude of each vulnerability shall be determined using a consistent methodology identified and documented in this section of the OPSEC Plan. The results of this analysis shall also be described in this section.

Note: For additional guidance and a sample vulnerability methodology see, “Applying OPSEC to Government Acquisitions and Contracts” at https://www.iad.gov/ioss/, AR 530-1 and DODM 5205.0- 2M.

VIII. RISK ASSESSMENT

General: The OPSEC risk of a program represents the probability of compromise of critical information and the impact to the program/contract taking into account the threat and vulnerabilities.

The acceptable level of OPSEC risk (as determined by senior leadership, or the contracting activity) shall be described in this section in terms consistent with the selected OPSEC methodology.

Risk Assessment: The specific OPSEC risk shall be described in terms consistent with the OPSEC methodology selected for determining OPSEC threat and vulnerability. The method, and the results of the assessment, shall be presented in this section. The conclusion of the risk assessment shall result in an ordinal ranking of OPSEC risk (highest to lowest). Note: Additional guidance and a sample risk methodology are available in “Applying OPSEC to Government Acquisitions and Contracts” at https://www.iad.gov/ioss/, AR 530-1 and DODM 5205.0-2M.

http://www.dss.mil/documents/ci/2017_CI_Trends_Report.pdf http://www.dss.mil/documents/ci/2017_CI_Trends_Report.pdf https://www.iad.gov/ioss/ https://www.iad.gov/ioss/

Attachment A, Enclosure 1 Page 7 of 11

IX. OPSEC MEASURES

General: This section of the OPSEC Plan shall identify specific OPSEC Measures proposed for mitigating OPSEC risk to acceptable levels including the cost to implement each measure. A sampling of common OPSEC measures is available in “Applying OPSEC to Government Acquisitions and Contracts” at https://www.iad.gov/ioss/. This list is not to be considered exhaustive and is provided as guidance for the development of the program/contract specific list of potential OPSEC measures.

Residual Risk: This section shall contain an analysis of residual OPSEC risk, in terms consistent with the OPSEC methodology selected, as a result of implementation of each OPSEC measure presented.

This section shall identify which OPSEC measures will be implemented and the rationale for those that will not.

X. OPSEC PROGRAM CHRONOLOGY:

This section shall document significant program OSPEC events throughout the lifecycle of the program. Significant events may include changes to the CIL, changes in program leadership or results of program assessments and surveys (including subcontractors). At a minimum, this section shall include a brief description of the event, date of occurrence, actions taken by the contractor and final disposition. A known compromise of critical information need only be referenced in keeping with the intended classification of this document. Note: The history contained herein may be used by the government as a part of an OPSEC or security audit conducted by the contracting activity, DSS or other authorized agency.

XI. ACRONYMS:

This section shall include a complete list of acronyms used in the Program OPSEC Plan.

XII. REFERENCES:

This section shall include a complete list of all references cited in the Program OPSEC Plan.

Attachment B Page 8 of 11

JPEO Armaments & Ammunition Attachment B (JPEO AA-21-007-S)

DD254, Block 13, Section 10j and 11l Continuation Sheet:

Controlled Unclassified Information (CUI)

10j. CONTROLLED UNCLASSIFIED INFORMATION (CUI)

1. The definition of CUI is unclassified information that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Government-wide policies. It does not include information that is classified pursuant to Executive Order 13526, dated December 29, 2009, or the Atomic Energy Act, as amended.

2. Contractor employees will require access to CUI in performance of this contract. Contractor personnel shall follow DoD Instruction (DoDI) 5200.48, Army CUI policies, and this document regarding access to CUI, and the marking, handling, storage, transmission, and destruction of CUI while working on this contract. Contractor employees are required to complete initial CUI training within 30 days of start of performance on the contract, and then annually thereafter.

Proof of completion shall be provided to COR/Technical Representative and/or PCO. Training is available at https://securityhub.usalearning.gov/index.html.

3. Specific Handling Instructions: All email correspondence containing CUI will be digitally encrypted IAW AR 25-1, para. 4-10c, dated 15 July 2019. In the event that encrypted email cannot be used to transmit CUI, there are several encryption tools available for use to accomplish this requirement: The DoD Safe Access File Exchange (SAFE) website (https://safe.apps.mil/) and/or the Encryption Wizard tool (http://spi.dod.mil/).

4. When CUI is to be provided to or generated by DoD contractors, the controls and protective measures to be applied shall be described in the pertinent contract documents (e.g., contract clause; statement of work; or DD Form 254, “Department of Defense Contract Security Classification Specification”). Solicitations and contracts shall use a non-disclosure of information clause that prohibits release of unclassified information to the public without approval of the contracting activity.

5. The Contractor shall not release to anyone outside the Contractor's organization any unclassified information, regardless of medium (e.g., film, tape, document), pertaining to any part of this contract or any program related to this contract without prior approval from the government.

6. GOVERNMENT DISTRIBUTION STATEMENTS: Will be added to all technical documents generated during the execution of this contract, in accordance with DoD Instruction

5230.24. Consult the security classification guide(s) (SCGs) identified in the DD Form 254 for guidance on the applicable distribution statements associated with the program or project. For additional guidance regarding the application of a distribution statement, consult with the COR/Technical Representative and/or the PCO.

https://securityhub.usalearning.gov/index.html https://safe.apps.mil/

Attachment B Page 9 of 11

7. Technical Documents are any recorded information that conveys scientific and technical information or technical data. This includes such informal documents as working papers, memoranda, and preliminary reports when such documents have utility beyond the immediate mission requirement or will become part of the historical record of technical achievements. It can also refer to any recorded information related to experimental, developmental, or engineering works that can be used to define an engineering or manufacturing process or to design, procure, produce, support, maintain, operate, repair, or overhaul program material. The data may be graphic or pictorial delineations in media, such as computer software, drawings, or photographs, text in specifications, or related performance or design documents, or computer printouts.

Examples of technical data include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software.

8. The contractor shall protect CUI from unauthorized disclosure by appropriately marking, safeguarding, disseminating, and destroying such information.

9. CUI may be identified in security classification guides to ensure the information receives appropriate protection. Contractor personnel are responsible for reading and understanding the guidance outlined in the SCG(s) used by the program(s) they are directly supporting and following the determinations and decisions documented in the SCG(s).

10. DFARS Clause 252.204-7012 applies to this contract. Any information identified and/or marked as FOUO, CUI, or containing a Distribution Statement B-F shall be considered “Covered Defense Information” as defined in DFARS Clause 252.204-7012.

11. For unauthorized disclosures of CUI, no formal security inquiry or investigation is required.

However, appropriate management action shall be taken to fix responsibility for unauthorized disclosure of CUI whenever feasible or required by other guidance, and appropriate disciplinary action shall be taken against those responsible. The FSO shall notify the PCO and the DoD Component that originated the CUI of its unauthorized disclosure. The unauthorized disclosure for CUI protected by the Privacy Act may result in criminal sanctions and disciplinary action may be taken against those responsible.

ADDITIONAL GUIDANCE FOR INFORMATION MARKED AS FOR OFFICIAL USE

ONLY (FOUO)

1. The “FOR OFFICIAL USE ONLY” (FOUO) marking is assigned to information at the time of its creation in a DOD User Agency. It is not authorized as a substitute for a security classification marking but it is used on official government information that may be withheld from the public under exemptions 2 through 9 IAW Army Regulation 25-55, The Department of the Army Freedom of Information Act Program and DoD Manual (DoDM) 5200.01, Vol. 4.

Attachment B Page 10 of 11

2. With the issuance of DoDI 5200.48, the DoD cancelled DoDM 5200.01, Vol.4, making the FOUO marking obsolete and legacy. Information provided to or held by the contractor that is marked as FOUO shall be handled in the following manner:

a. Legacy FOUO information and materials are not required to be re-marked or redacted while it remains under contractor control. However, when the legacy information is incorporated into, or cited in, another document or material, it must be reviewed for CUI and marked in accordance with DoDI 5200.48.

b. Legacy FOUO does not automatically become CUI. It must be reviewed by the owner of the information to determine if it meets or falls under one of the CUI categories listed in the CUI Registry. If it meets the new CUI requirements, it will be marked in accordance with DoDI 5200.48.

3. When no longer needed, all FOUO material will be destroyed by shredding. Electronic media will be purged with approved software or destroyed through a physical process.

4. Use of the above marking does not mean that the information cannot be released to the public, only that it must be reviewed by the Government prior to its release to determine whether a significant and legitimate government purpose is served by withholding the information, or portions of it, from the public.

Attachment C Page 11 of 11

JPEO Armaments & Ammunition Attachment C (JPEO AA-21-007-S)

DD254, Block 18, Required Distribution

PLEASE ENSURE ALL PARTIES LISTED ON THIS DISTRIBUTION RECEIVE A

COPY OF THE DD254 WITH ALL ATTACHMENTS

SECTION 18: REQUIRED DISTRIBUTION:

a. CONTRACTOR (all locations listed in Block 8a):

TBD

c. COGNIZANT SECURITY OFFICE FOR PRIME CONTRACTOR:

**In the event of a possible compromise of classified information under the control of the contractor, the contractor will immediately notify:

Defense Counterintelligence & Security Agency (DCSA)

TBD

e. CONTRACTING OFFICER:

Molly J. Lewis Army Contracting Command – Rock Island Munitions & Industrial Base Directorate Building 60, 3rd Floor 3055 Rodman Avenue Rock Island, IL 61299-8000 309-782-1837 molly.j.lewis4.civ@mail.mil

CONTRACTING OFFICER’S

TECHNICAL REPRESENTATIVE:

Alexander Hoover FCDD-ACM-FF, Building 14 Picatinny Arsenal, NJ 07806-5000 973-724-5116 alexander.j.hoover.civ@mail.mil

f. OTHERS AS NECESSARY:

Naomi Shareef or Jason Hayman Command Security Managers JPEO Armaments & Ammunition, SFAE-AA Picatinny Arsenal, NJ 07806-5000 (973)724-9877 or (973) 724-9775 naomi.j.shareef.civ@mail.mil and/or jason.j.hayman.civ@mail.mil mailto:molly.j.lewis4.civ@mail.mil mailto:naomi.j.shareef.civ@mail.mil mailto:jason.j.hayman.civ@mail.mil

DRAFT

SAMPLE

PREVIOUS EDITION IS OBSOLETE.

Page of

DD FORM 254, APR 2018

NEEDS DD67

DEPARTMENT OF DEFENSE

CONTRACT SECURITY CLASSIFICATION SPECIFICATION

(The requirements of the National Industrial Security Program (NISP) apply to all security aspects of this effort involving classified information.)

OMB No. 0704-0567 OMB approval expires:

May 31, 2022 The public reporting burden for this collection of information, 0704-0567, is estimated to average 70 minutes per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Washington Headquarters Services, at whs.mc-alex.esd.mbx.dd-dod-information-collections@mail.mil. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

RETURN COMPLETED FORM AS DIRECTED IN THE INSTRUCTIONS.

1. CLEARANCE AND SAFEGUARDING

2. THIS SPECIFICATION IS FOR: (X and complete as applicable.)

3. THIS SPECIFICATION IS: (X and complete as applicable.)

a. ORIGINAL (Complete date in all cases.)

b. REVISED (Supersedes all previous specifications.)

4. IS THIS A FOLLOW-ON CONTRACT?

If yes, complete the following:

Classified material received or generated under

5. IS THIS A FINAL DD FORM 254?

If yes, complete the following:

6. CONTRACTOR (Include Commercial and Government Entity (CAGE) Code)

7. SUBCONTRACTOR(S) (Click button if you choose to add or list the subcontractors -- but will still require a separate DD Form 254 issued by a prime contractor to each subcontractor)

8. ACTUAL PERFORMANCE (Click button to add more locations.)

10. CONTRACTOR WILL REQUIRE ACCESS TO: (X all that apply. Provide details in Blocks 13 or 14 as set forth in the instructions.)

e. NATIONAL INTELLIGENCE INFORMATION:

11. IN PERFORMING THIS CONTRACT, THE CONTRACTOR WILL: (X all that apply. See instructions. Provide details in Blocks 13 or 14 as set forth in the instructions.)

12. PUBLIC RELEASE

Any information (classified or unclassified) pertaining to this contract shall not be released for public dissemination except as provided by the National Industrial Security Program Operating Manual (NISPOM) or unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for review and approval prior to release to the appropriate government approval authority identified here with at least office and phone contact information and if available, an e-mail address. (See instructions)

13. SECURITY GUIDANCE

The security classification guidance for classified information needed for this effort is identified below. If any difficulty is encountered in applying this guidance or if any other contributing factor indicates a need for changes in this guidance, the contractor is authorized and encouraged to provide recommended changes; to challenge the guidance or the classification assigned to any information or material furnished or generated under this contract; and to submit any questions for interpretation of this guidance to the official identified below. Pending final decision, the information involved shall be handled and protected at the highest level of classification assigned or recommended.

(Fill in as appropriate for the classified effort. Attach, or forward under separate correspondence, any documents/guides/extracts referenced herein. The field will expand as text is added. When removing any expanded text area, use delete key or backspace key, then click out of the text field for it to shrink after the text has been deleted. Also allows for up to 6 internal reviewers to digitally sign. See instructions for additional guidance or use of the fillable PDF.)

List of Attachments (All Files Must be attached Prior to Signing, i.e., for any digital signature on the form)

14. ADDITIONAL SECURITY REQUIREMENTS

Requirements, in addition to NISPOM requirements for classified information, are established for this contract.

If Yes, identify the pertinent contractual clauses in the contract document itself, or provide an appropriate statement which identifies the additional requirements. Provide a copy of the requirements to the CSO. The field will expand as text is added or you can also use item 13. When removing any expanded text area, use delete key or backspace key, then click out of the text field for it to shrink after the text has been deleted. (See instructions for additional guidance or use of the fillable PDF.)

15. INSPECTIONS

Elements of this contract are outside the inspection responsibility of the CSO.

If Yes, explain and identify specific areas and government activity responsible for inspections. The field will expand as text is added or you can also use item 13. When removing any expanded text area, use delete key or backspace key, then click out of the text field for it to shrink after the text has been deleted. (See instructions for additional guidance or use of the fillable PDF.)

16. GOVERNMENT CONTRACTING ACTIVITY (GCA) AND POINT OF CONTACT (POC)

17. CERTIFICATION AND SIGNATURES

Security requirements stated herein are complete and adequate for safeguarding the classified information to be released or generated under this classified effort. All questions shall be referred to the official named below. Upon digitally signing Item 17h, no changes can be made as the form will be locked.

18. REQUIRED DISTRIBUTION BY THE CERTIFYING OFFICIAL

9.0.0.2.20120627.2.874785 DD 254, "DoD Contract Security Classification Specification" Show Attachment Bar

This Solicitation DD Form 254 is for planning purposes only. A Prime Contract DD Form 254 will be issued upon contract award.

Field Office - TBD Enter cognizant security office(s) (Name, Address, ZIP Code, Telephone required; Email Address optional).: Defense Counterintelligence & Security Agency (DCSA) Field Office - TBD

Classified material must be handled in accordance with the current National Industrial Security Program Operating Manual (NISPOM DoD 5220.22M) requirements, and source documents. No classified information and/or materials will be provided to contractor prior to verification of company’s facility clearance and storage capability. In the event that a company needs access to classified information and/or materials as part of this solicitation, a separate contractor-specific DD Form 254 will be issued to each company.

Contractor personnel shall have the appropriate level of investigation and/or security clearance for each site of performance of work. The Contractor shall observe and comply with all security provisions in effect at each selected site. Only U.S. Citizens are authorized to work with U.S. Government classified information and/or material. All contractor personnel working on this contract that require access to classified information and/or material will be required to have a final Secret clearance (interim clearances are not acceptable) and must maintain that clearance throughout the duration that they are assigned to this contract. Only U.S. Persons are authorized to work with U.S. Government Controlled Unclassified Information (CUI), however, the exception for performance by Non-U.S. Persons are subject to U.S. Export regulation including, but not limited to, the requirements of the Arms Export Control Act, 22 U.S.C. §2751-2794, including the International Traffic in Arms Regulation (ITAR), 22 C.F.R. §120 et seq.; and the Export Administration Act, 50 U.S.C. app. §2401- 2420. Release of CUI to a Non-U.S. Person is not authorized. The contractor will observe and comply with all security provisions outlined in this DD Form 254 and associated SOW/PWS, and all local policies in effect while accessing or working on U.S. Government Installations (as identified in this DD Form 254). Information Disclosure: A Certificate of Non-Disclosure shall be signed and returned to the PCO/COR/ACOR prior to contract award. Copies will be maintained by the PCO/COR/ACOR for the life of the contract/agreement. The contractor shall return all classified/sensitive material, to include program material, to the Government at the completion of this contract.

SECURITY CLASSIFICATION GUIDES (SCGs) will be supplied to the contractor by the COR/COTR/PCO, as needed and under separate cover, depending on which programs the contractor will be performing on in support of this contract. The SCGs applicable to this contract are:

- Fuze, Multi-Option, Artillery, M782 and Variants Security Classification Guide, dated 8 April 2020

- Anti-Tamper Security Classification Guide, dated 30 July 2020

SEE DD254, BLOCK 13, CONTINUATION SHEET FOR ADDITIONAL SECURITY GUIDANCE. (Located in Attachment Bar in PDF program)

The FSO shall provide a copy of all subcontractor DD254s issued under this contract to the JPEO Armaments & Ammunition (JPEO A&A) Security Office and the COR within 5 days of issuance. While not required, it is recommended that FSO notify the JPEO A&A Security Office of its intent to issue subcontractor DD 254 prior to issuance.

Ref 13a: Army regulations available at: www.apd.army.mil.

Ref 13b: No classified information will be transmitted electronically. All classified information and/or material will be hand carried or mailed using an authorized carrier service as outline in NISPOM. For transmission of classified material to JPEO A&A entities, contractor will ship materials via USPS (via Registered Mail), unless prior approval is granted by Technical Representative or PCO to use a commercial carrier (tracking number must be provided upon shipment), to the following address: COMMANDING GENERAL, US ARMY Joint Program Executive Office Armaments & Ammunition, ATTN: SFAE-AA, Bldg. 1 Buffington Rd., Picatinny Arsenal, NJ 07806-5000.

Ref 13c: All contractor employees, including subcontractor employees, shall comply with the MOFA program protection plan (PPP). The contractor shall comply with DOD and DA technology protection requirements in DODI 5200.39, AR 70-1 and DA PAM 70-3.

REVIEWER ACKNOWLEDGEMENT AND SIGNATURE: The undersigned have reviewed this DD Form 254 and its accompanying attachment(s) and concur with the security requirements outlined therein. The PCO/COR will ensure that the prime contractor complies with these requirements as best as possible within the limits of his/her responsibility, and that any violations are brought to the attention of the PCO and the JPEO A&A Security Office.

text: Alexander Hoover alexander.j.hoover.civ@mail.mil 973-724-5116 text: Jennifer Mabalot Siegfried jennifer.m.siegfried.civ@mail.mil 973-724-3704 text: Molly J. Lewis

(309) 782-1837 molly.j.lewis4.civ@mail.mil

PM CAS

rep: Contracting Officer ACC - Rock Island

Program Protection: Contractor shall be provided a copy of the Program Protection Plan (PPP) for the Artillery M782 Multi-Option Fuze dated 10 Aug 2007, after contract award. Contractor shall abide by and implement protection requirements outlined in the PPP.

Munitions & Industrial Base Directorate Building 60, 3rd Floor 3055 Rodman Avenue Rock Island, IL 61299-8000 Enter address (include zip code).: 1 Buffington Rd.

ATTN: SFAE-AA

Picatinny, NJ 07806-5000