Attachment_0001-_DD_Form_254_PEO-AMMO-17-008-SOL_MAS.pdf

DEPARTMENT OF DEFENSE 1. CLEARANCE AND SAFEGUARDING

CONTRACT SECURITY CLASSIFICATION SPECIFICATION a. FACILITY CLEARANCE REQUIRED

SECRET (PEO-AMMO-17-008-S)

(The requirements of the DoD Industrial Security Manual apply to all aspects of this effort)

b. LEVEL OF SAFEGUARDING REQUIRED

NONE

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

a. PRIME CONTRACT NUMBER

a. ORIGINAL (Complete date in all cases)

Date (YYYYMMDD)

THIS DD254 IS FOR SOLICITATION PURPOSES ONLY.

A PRIME CONTRACT DD254 WILL BE PROVIDED

UPON CONTRACT AWARD.

X 20170718

b. SUBCONTRACT NUMBER b. REVISED REVISION NO. DATE (YYMMDD)

(Supersedes all previous specs)

c. SOLICITATION OR OTHER NUMBER DUE DATE (YYMMDD) c. FINAL (Complete Item 5 in all cases) DATE (YYMMDD)

X W15QKN-17-R-OADP

4. IS THIS A FOLLOW-ON CONTRACT? YES X NO. If Yes complete the following

Classified material received or generated under (Preceding Contract Number) is transferred to this follow-on contract

5. IS THIS A FINAL DD FORM 254? YES X NO. If Yes complete the following

In response to the contractor's request dated ____________ , retention of the identified classified material is authorized for the period of __________

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

a. NAME, ADDRESS, AND ZIP CODE b. CAGE CODE c. COGNIZANT SECURITY OFFICE (Name, Address, and Zip Code) This DD Form 254 is for Solicitation purposes only. A Prime Contract DD254 will be provided upon contract award.

N/A N/A

7. SUBCONTRACTOR

a. NAME, ADDRESS, AND ZIP CODE b. CAGE CODE c. COGNIZANT SECURITY OFFICES ( Name, Address, and Zip Code)

N/A

8. ACTUAL PERFORMANCE

a. LOCATION b. CAGE CODE c. COGNIZANT SECURITY OFFICE (Name, Address, and Zip Code)

TBD

9. GENERAL IDENTIFICATION OF THIS PROCUREMENT

To provide comprehensive program management support for current and future, small, medium and large caliber ammunition programs. This effort is to provide a full range of engineering and management activities, acquisition management.

10. THIS CONTRACT WILL REQUIRE ACCESS TO: YES NO 11. IN PERFORMING THIS CONTRACT, THE CONTRACTOR WILL: YES NO

a. COMMUNICATIONS SECURITY (COMSEC) INFORMATION X a. HAVE ACCESS TO CLASSIFIED INFORMATION ONLY AT ANOTHER

CONTRACTOR’S FACILITY OR A GOVERNMENT ACTIVITY X

b. RESTRICTED DATA X b. RECEIVE CLASSIFIED DOCUMENTS ONLY X

c. CRITICAL NUCLEAR WEAPON DESIGN INFORMATION X c. RECEIVE AND GENERATE CLASSIFIED MATERIAL X

d. FORMERLY RESTRICTED DATA: X d. FABRICATE, MODIFY, OR STORE CLASSIFIED HARDWARE X

e. INTELLIGENCE INFORMATION: e. PERFORM SERVICES ONLY X

(1) Sensitive Compartmented Information (SCI) X f. HAVE ACCESS TO U.S. CLASSIFIED INFORMATION OUTSIDE THE U.S., PUERTO

RICO, U.S. POSSESSIONS AND TRUST TERRITORIES X

(2) Non-SCI X g. BE AUTHORIZED TO USE THE SERVICES OF DEFENSE TECHNICAL

INFORMATION CENTER (DTIC) OR OTHER SECONDARY DISTRIBUTION CENTER X

f. SPECIAL ACCESS INFORMATION X h. REQUIRE A COMSEC ACCOUNT X

g. NATO INFORMATION X i. HAVE A TEMPEST REQUIREMENT X

h. FOREIGN GOVERNMENT INFORMATION X j. HAVE OPERATIONS SECURITY (OPSEC) REQUIREMENTS X

i. LIMITED DISSEMINATION INFORMATION X k. BE AUTHORIZED TO USE THE DEFENSE COURIER SERVICE X

j. FOR OFFICIAL USE ONLY INFORMATION X l. OTHER (Specify) X

k. OTHER Specify) Controlled Unclassified Information (CUI)

X

Access USG IT Systems & Networks, SIPRNet accounts required at Picatinny Arsenal, NJ & Ft. Benning, GA

DD Form 254, DEC 1999 Previous editions are obsolete

12. PUBLIC RELEASE. Any information (classified or unclassified) pertaining to this contract shall not be released for public dissemination except as provided by the industrial Security Manual or unless it has been approved for public release by appropriate U.S. Government authority. Proposed public release shall be submitted for approval prior to release

Direct X

Through (Specify):

Request for public release of material requires approval through the office of the Project Manager Maneuver Ammunition Systems (SFAE-AMO-MAS), Building 354, Picatinny Arsenal, NJ 07806-5000 to the Picatinny Public Affairs Office. Non- SCI intelligence information is not authorized for public release.

to the Directorate for Freedom of Information and Security Review, Office of the Assistant Secretary of Defense (Public Affairs)* for review.

*In the case of non-DoD User Agencies, requests for disclosure shall be submitted to that agency.

13. SECURITY GUIDANCE. The security classification guidance 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 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 document/guides/extracts referenced herein. Add additional pages as needed to provide complete guidance.)

This DD 254 is for planning purposes only. NO CLASSIFIED INFORMATION WILL BE PROVIDED DURING THE SOLICITATION PHASE. Upon contract award, a contract-specific DD 254 will be generated and provided to the contractor.

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/materials will be provided to contractor prior to verification of company’s facility clearance and storage capability.

Contractor personnel shall comply with AR 381-12, Threat Awareness and Reporting Program (October 2010) and reporting requirements prescribed therein. The contractor Facility Security officer (FSO) is responsible for the retrieval and return of all DoD issued credential (i.e, CAC, installation badges, vehicle decals) when personnel terminate employment.

SEE DD254, BLOCK 13, CONTINUATION SHEETS FOR ADDITIONAL SECURITY GUIDANCE.

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

Ref 13b: Classified information transmitted under this agreement is authorized to be submitted directly to/from: COMMANDING GENERAL, US ARMY Program Executive Officer AMMUNITION, ATTN: SFAE-AMO, Bldg. 1 Buffington Rd., Picatinny Arsenal, NJ 07806-5000.

Ref 13c: CONTRACTING OFFICER & CONTRACTING OFFICER’S REPRESENTATIVE ACKNOWLEDGEMENT AND SIGNATURE: The undersigned has reviewed this Security Specification, understands the security provisions outlined therein, and will ensure that the prime contractor complies with them as best possible within the limits of his/her responsibility, and that any violations are brought to the attention of the PCO and certifying security official identified in block 16.

Margaret Heyrich, Contracting Officer Thomas Brown, Contracting Officer’s Representative Margaret.a.heyrich.civ@mail.mil (973) 724-3871 thomas.m.brown146.civ@mail.mil (973) 724-5272

14. ADDITIONAL SECURITY REQUIREMENTS. Requirements, in addition to ISM requirements, 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 cognizant security office. Use Item 13 if additional space is needed.)

X Yes No

OPSEC Requirements; See Block 13 Continuation Sheet

NO CLASSIFIED INFORMATION WILL BE PROVIDED DURING THE SOLICITATION PHASE.

15. INSPECTIONS. Elements of this contract are outside the inspection responsibility of the cognizant security office. (If Yes, explain and identify specific areas or elements carved out and the activity responsible for inspections. Use Item 13 if additional space is needed.

Yes X No

DSS does not conduct security reviews for Sensitive Compartmented Information (SCI) but is still responsible for security reviews involving Non-SCI (collateral classified information) in the possession of a contractor or subcontractor.

16. CERTIFICATION AND SIGNATURE. 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.

a. TYPED NAME OF CERTIFYING OFFICIAL

Naomi J. Griggs

b. TITLE Security Specialist Program Executive Office Ammunition c.TELEPHONE (Include Area Code)

(973) 724-9877

d. ADDRESS (Include ZIP Code) 17. REQUIRED DISTRIBUTION

Program Executive Office – Ammunition X a. CONTRACTOR

Buffington Road, Building 1 b. SUBCONTRACTOR

Picatinny Arsenal, NJ 07806-5000 X c. COGNIZANT SECURITY OFFICE FOR PRIME AND SUBCONTRACTOR

e. SIGNATURE d. U.S. ACTIVITY RESPONSIBLE FOR OVERSEAS SECURITY

ADMINISTRATION

X e. ADMINISTRATIVE CONTRACTING OFFICER

X f. OTHERS AS NECESSARY

DD Form 254 (Back), DEC 1999 mailto:Margaret.a.heyrich.civ@mail.mil mailto:thomas.m.brown146.civ@mail.mil

PEO Ammunition Attachment (PEO AMMO-17-008-S)

SOLICITATION NUMBER: W15QKN-17-R-OADP

Attachment DD254, Block 8 Continuation Sheet :

Contractor access to classified information and materials will occur only at another government and/or contractor facility. Contractor access to classified materials will occur at the following locations:

1. Bldg. 70, Ft. Benning, GA

2. Bldg. 7, Lake City Army Ammunition Plant (LCAAP), Independence, MO

3. Picatinny Arsenal, NJ

Also, for the purposes of this contract, the prime contract could require access to the following U.S.

Army installations for meetings, testing and/or training purposes:

1. Aberdeen Proving Ground, MD

2. Rock Island Arsenal, IL

3. Ft Bliss, TX

4. Ft Sill, OK

5. Ft Hood, TX

6. Ft Lewis, WA

7. Ft Carson, CO

8. Ft Irwin, CA

9. Ft Bragg, NC

10. Ft Campbell, KY

11. Ft Drum, NY

12. Ft Stewart, GA

13. Ft Riley, KS

14. Camp Atterbury, IN

15. Camp Shelby, MS

16. Camp Ripley, MN

17. Gowen, Field, ID

18. Ft Richardson, AK

19. Pentagon, Washington, DC

20. Yuma Proving Ground, Yuma, AZ

21. Camp Edwards, MA

22. Cannon AFB, MN

23. Ft Wainwright, AK

24. Ft Shafter, HI

25. Schofield Barracks, HI

26. Yakima Training Center, WA

Prior to the start of work (or any visit), the contractor Facility Security Officer (FSO) will submit a JPAS visit request to the agency/organization where work will be performed (or being visited) (using that organization’s SMO code) no later than one week prior to the visit. For personnel being assigned to and/or visiting PEO Ammunition, send all visit request to SMO code W6DTAA4.

All contractor personnel will comply with all host installation policies and procedures for gaining access to the facilities where the visit will be conducted or work performed. The COR and/or the local POC will be responsible for providing all necessary guidance to the contractor.

Contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by Government representative). The contractor shall also provide all information required for background checks to meet installation access requirement to be accomplished by the FSO or PEO Ammunition Security Office as appropriate. Contractor workforce must comply with all personal identity verification requirements as directed by DoD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

Attachment DD254, Block 13 Continuation Sheet :

SECURITY GUIDANCE

SECURITY CLASSIFICATION GUIDES (SCGs) will be supplied to the contractor by the COR, 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:

• XM1158 (formerly, “Advanced Armor Piercing for Advanced Armor (ADVAP)”), dtd 27 Nov 2013

• Small Arms Ammunition, Caliber .50 and below, dtd 9 Dec 2009

• M433 (LV40mm), dtd 24 Apr 2006

• M919 (25mm APFSDS KE), dtd 1 Jul 2001

• M430A1 (HV 40mm), dtd Apr 1995

Ref 10a: Communications Security (COMSEC): Access to COMSEC material and/or equipment will be required in the performance of this contract. 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 and 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 10b: Restricted Data: Restricted data information is not releasable to contractor employees who have not received a FINAL clearance at the appropriate security level. Written concurrence of the KO is required prior to subcontracting.

Ref 10d: Formerly Restricted Data: The contractor is permitted access to Formerly Restricted Data (FRD) in the performance of this contract. Access to FRD requires a final U.S. Government clearance at the appropriate level. Written concurrence of the KO is required prior to subcontracting.

Ref 10e: Intelligence Information: The Director of National Intelligence (DNI) has jurisdiction and control of intelligence information. If the contract requires access to intelligence information, the PCO is responsible for ensuring that the additional security requirements outlined in the DNI Directives are incorporated in the guidance provided to the contractor.

Ref 10e(2): Intelligence Information. Non-SCI Information is not releasable to contractor employees who have not received a clearance at the appropriate security level. Written concurrence of the PCO is required prior to subcontracting. The Director of National

Intelligence (DNI) has jurisdiction and control of intelligence information and additional security requirements for controlling and protecting intelligence are outlined in “Section 10e(2) Continuation Sheet: Non-SCI Intelligence Information Guidance (from ARDEC SIO)”.

Ref 10h: Foreign Government Information (FGI): This is information that is provided to the U.S.

Government by a foreign government(s), an international organization, or any element thereof, and can be classified or unclassified. This does not include NATO information. Access to classified foreign government information requires a final U.S. Government clearance at the appropriate security level. The prime contractor must receive written approval from the PCO prior to subcontracting and granting access to a subcontractor. AR 380-5, Chapter 4, Section VII applies.

Ref 10j and Ref 10k: SEE DD254, BLOCK 13, CONTINUATION SHEET FOR

FOUO/CUI GUIDANCE.

Ref 11a: Have access to classified information: Contractor access to clasisifed information/materials restricted to the locations identified in Block 8a and Block 8a continuation sheet. Government agency or activity will provide security classification guidance for performance of this contract. Submit visit request to the KO and/or Security Management Office for need-to-know verification.

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 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.

Ref 11l: Access to SIPRnet will be required for contractor personnel performing at Picatinny Arsenal, NJ and Ft. Benning, GA. Contractor personnel shall comply with the local security procedures for establishing SIPRnet accounts.

Ref 11l: All classified information/material will be hand carried or mailed registered through the USPS only.

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.

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 www.ioss.gov, 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 http://www.ioss.gov/ overall threat to 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 www.ioss.gov 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 www.ioss.gov. 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 www.ioss.gov, 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 www.ioss.gov, AR 530-1 and DODM 5205.0-2M.

http://www.dss.mil/documents/ci/2013%20Unclass%20Targeting%20US%20Technologies_FINAL.pdf http://www.dss.mil/documents/ci/2013%20Unclass%20Targeting%20US%20Technologies_FINAL.pdf http://www.ioss.gov/ http://www.ioss.gov/

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 www.ioss.gov. 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.

DD254, Block 13, Section 10e(2) Continuation Sheet:

Non-SCI Intelligence Information Guidance (from ARDEC SIO)

As defined in Executive Order 12333 of December 4, 1981, "United States Intelligence Activities", foreign intelligence is defined as" ... information relating to the capabilities, intentions and activities of foreign powers, organizations or persons including information on international terrorist activities."

In accordance with DCID 6/6, pursuant to the provisions and definitions of Executive Order 12333, the following guidance is provided to you regarding the release, control, dissemination and use of intelligence information in support of ARDEC contracts:

1. All intelligence material, reproductions thereof, and all other material generated based on, or incorporating data there from (including authorized reproductions), will be controlled in the same manner as the originals, and remain the property of the US Government and may be withdrawn at any time.

2. You must maintain a record of all intelligence material, regardless of classification, released to your custody.

3. You must accomplish a verification of all materials, if held for at least one year, released under the contract. Further, such verification will be conducted upon the anniversary date of the contract, or on a mutually agreed date, and the Senior Intelligence Officer, ARDEC, will be furnished a copy of the verification list. The objective of this requirement is not only to afford the required security for intelligence data, but should be viewed as an opportunity to return documents no longer needed or superseded.

4. You will not reproduce intelligence material released to your custody without the express written permission of the Senior Intelligence Officer, ARDEC.

5. When written permission is received to reproduce intelligence materials, you will control and account for such reproductions in the same manner as pertains to the originals.

6. Prior to granting an employee access to the intelligence materials, you will brief the employee on his obligation to safeguard the information. The appropriate portion of SF312, "Classified Information Non-Disclosure Agreement", will be executed at the time of briefing.

7. You and the Project Officer will jointly determine those employees who require access to the intelligence material and you will maintain records to identify completely by name and title all employees so authorized. Requests for additions or personnel changes should be provided to the Project Officer prior to access. Additionally, you will maintain records of authorized visitors who have had access to the intelligence material.

8. You will not release intelligence material to any activity, employee or other person not directly engaged in providing services under the contract unless specific written authorization for such release is received from this office. This prohibition precludes release without authority to another contractor, including a sub-contractor, government agency, private individual or organization.

9. The intelligence materials will not be released to foreign nationals or non-US citizens except with the specific written authorization from the Senior Intelligence Officer, ARDEC, whether or not they are also consultants, U.S. contractor employees, and regardless of the level of their access authorization.

10. The intelligence materials released to you will not be destroyed unless written authorization for such destruction is received from the Senior Intelligence Officer, ARDEC. In the event such authorization is received, you will effect such destruction in accordance with Chapter 5, Section 7 of the National Industrial Security Program Operating Manual, DoD 5220.22-M, dated February 2006.

11. If access to SIPRnet and INTELINK-S is granted, the following guidelines apply:

a. The computer account will be used in support of an official government project.

b. You will not willfully compromise the account password.

c. You will notify the Project Officer when the account is no longer needed, or account information needs revising, or the account password has been knowingly compromised.

d. The account will be used in accordance with all existing instructions, policy directives, and guidelines to ensure no improper or fraudulent use.

e. Data and files associated with this account are subject to random review.

f. The account password will be changed in accordance with current Army policy.

g. You are responsible for not only safeguarding the classified contents of this account, but also the physical configuration of the network.

12. Upon expiration of a contract, all substantive intelligence materials released to you, all reproductions thereof, and all other materials incorporating material there from will be returned to this office for disposition. In the event that the contract is extended, or that a new similar contract requiring the released data is negotiated, it is the responsibility of the Project Officer to affect an extension or document transfer with the Senior Intelligence Officer, ARDEC.

13. The name and address of the Senior Intelligence Officer, ARDEC, is as follows:

Commander, U.S. Army ARDEC Intelligence and Technology Protection Office Attn: RDAR-CIS (Mr. Michael Santaspirt) Senior Intelligence Officer, Bldg. 93 Picatinny Arsenal, NJ 07806-5000

DD254, Block 13, Section 10j and 10k Continuation Sheet:

For Official Use Only (FOUO) and Controlled Unclassified Information (CUI)

10j. FOR OFFICIAL USE ONLY (FOUO)

1. The “FOR OFFICIAL USE ONLY” 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.

2. Control, marking, and protection of FOUO information will be in accordance with this document and DoD Manual 5200.01, Vol. 4.

3. Specific Handling Instructions: All emails containing (FOUO) will be digitally encrypted in accordance with AR 25-1, para. 4-1 f.(1)(b), dated 25 June 2013. There are several encryption tools available for use to accomplish this requirement: The AMRDEC Safe Access File Exchange (SAFE) website (https://safe.amrdec.army.mil/SAFE/) and/or the Encryption Wizard (http://spi.dod.mil/).

4. FOR OFFICIAL USE ONLY is restricted to personnel with a valid need to know unless public release authorization has been obtained. Information marked as FOUO, in any media format, may only be disseminated to those individuals or organizations with direct affiliation with the given program or project. Further dissemination of such information will be at the discretion of the Contracting Officer (PCO) or Contracting Officer’s Representative (COR).

Personnel no longer requiring access to FOUO must destroy or surrender any materials in their possession and terminate future access to it. The contractor may disseminate “FOR OFFICIAL USE ONLY” (FOUO) information to their employees who have a need to know for the information in connection with this contract.

5. 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.

6. 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.

7. An unclassified document containing FOUO information will be marked IAW with DoD Manual 5200.01, Vol. 4, Enclosure 3, paragraph 2c.

https://safe.amrdec.army.mil/SAFE/

8. Within a classified document, an individual page that contains both FOUO and classified information will be marked at the top and bottom with the highest security classification of the information appearing on the page, as outlined in the NISPOM, AR 380-5, and DoD Manual 5200.01.

9. Removal of the “For Official Use Only” marking can only be accomplished by the originator or other competent authority. When the “For Official Use Only” status is terminated, all known holders will be notified to the extent practical.

10. During working hours, “For Official Use Only” information shall be placed in an out-of-sight location if the work area is accessible to persons who do not have a need for the information. During non-working hours, the information shall be stored to preclude unauthorized access. Filing such material with other unclassified records in unlocked files or desks is adequate when internal building security is provided during non-working hours. When such internal security is not exercised, locked buildings or rooms will provide adequate after-hours protection or the material can be stored in locked receptacles such as file cabinets, desks, or bookcases. “For Official Use Only” information may be sent via First Class US Mail or by parcel post. Bulky shipments may be set by Fourth Class US Mail.

11. Unauthorized disclosure of “For Official Use Only” information does not constitute a security violation but the Government Customer should be informed of any unauthorized disclosure. The unauthorized disclosure for FOUO information protected by the Privacy Act may result in criminal sanctions and disciplinary action may be taken against those responsible.

10k. 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 (References (m) and (n)). Within the Department of Defense, examples of CUI include materials marked as “For Official Use Only (FOUO)”, “Law Enforcement Sensitive (LES),” or any unclassified technical documents with a Distribution Statement B-F.

2. 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.

3. 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.

4. Technical Data is 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 pictoral 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, catalog-item identifications, and related information, and computer software documentation.

5. GOVERNMENT DISTRIBUTION STATEMENTS: Will be added to all technical data generated during the execution of this contract, in accordance with DoD Directive 5230.24.

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

7. CUI may be identified in security classification guides to ensure the information receives appropriate protection.

8. 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 DoD Component that originated the CUI shall be informed of its unauthorized disclosure.

DD254, Block 17, Required Distribution

PLEASE ENSURE ALL PARTIES LISTED ON THIS DISTRIBUTION RECEIVE A COPY

OF THE DD254 WITH ALL ATTACHMENTS

SECTION 17: REQUIRED DISTRIBUTION:

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

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 Security Service

e. CONTRACTING OFFICER:

Margaret Heyrich ACC-NJ, Bldg. 10 Picatinny Arsenal, NJ 07806-5000 (973)724-3871 margaret.a.heyrich.civ@mail.mil

CONTRACTING OFFICER’S REPRESENTATIVE:

Thomas Brown PEO Ammunition, Bldg. 354, SFAE-AMO-MAS Picatinny Arsenal, NJ 07806-5000

(973) 724-5272 thomas.m.brown146.civ@mail.mil

f. OTHERS AS NECESSARY:

Naomi Griggs or Jason Hayman Industrial Security Specialist PEO Ammunition, SFAE-AMO Picatinny Arsenal, NJ 07806-5000 (973)724-9877 or (973) 724-9775 naomi.j.griggs.civ@mail.mil and/or jason.j.hayman.civ@mail.mil

Michael Santaspirt Senior Intelligence Officer U.S. Army ARDEC, RDAR-CIS Picatinny Arsenal, NJ 07806-5000

(973) 724-9774 michael.a.santaspirt.civ@mail.mil mailto:margaret.a.heyrich.civ@mail.mil mailto:thomas.m.brown146.civ@mail.mil mailto:naomi.j.griggs.civ@mail.mil mailto:jason.j.hayman.civ@mail.mil mailto:michael.a.santaspirt.civ@mail.mil