J.2 DD254_Bidding.pdf

(Updated 20250815) CLASSIFICATION (When filled in): Unclassified

CLASSIFICATION (When filled in): Unclassified PREVIOUS EDITION IS OBSOLETE. Page 1 of 5DD FORM 254, APR 2018

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:

August 31, 2028

The public reporting burden for this collection of information, 0704-0567, is estimated to average 36 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

a. LEVEL OF FACILITY SECURITY CLEARANCE (FCL) REQUIRED

(See Instructions)

Secret

b. LEVEL OF SAFEGUARDING FOR CLASSIFIED INFORMATION/

MATERIAL REQUIRED AT CONTRACTOR FACILITY

None (See instructions)

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

a. PRIME CONTRACT NUMBER (See instructions.)

b. SUBCONTRACT NUMBER

c. SOLICITATION OR OTHER NUMBER

N0017826R2500

DUE DATE (YYYYMMDD)

TBD

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

a. ORIGINAL (Complete date in all cases.)

DATE (YYYYMMDD)

20260805

b. REVISED (Supersedes all previous specifications.)

REVISION NO. DATE (YYYYMMDD)

c. FINAL (Complete Item 5 in all cases.) DATE (YYYYMMDD)

4. IS THIS A FOLLOW-ON CONTRACT? No Yes 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? No Yes If yes, complete the following:

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

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

a. NAME, ADDRESS, AND ZIP CODE

*****Bidding DD254*****

b. CAGE CODE c. COGNIZANT SECURITY OFFICE(S) (CSO) (Name, Address, ZIP Code, Telephone required; Email Address optional)

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) Add Row Remove Last Row Delete All Rows

a. NAME, ADDRESS, AND ZIP CODE

b. CAGE CODE c. COGNIZANT SECURITY OFFICE(S) (CSO) (Name, Address, ZIP Code, Telephone required; Email Address optional)

8. ACTUAL PERFORMANCE (Click button to add more locations.) Add Row Remove Last Row Delete All Rows

a. LOCATION(S) (For actual performance, see instructions.)

Naval Surface Warfare Center Dahlgren Division Dam Neck Annex (NSWCDD DNA) 1922 Regulus Ave Virginia Beach, VA 23461-2097

b. CAGE CODE (If applicable, see Instructions.)

c. COGNIZANT SECURITY OFFICE(S) (CSO) (Name, Address, ZIP Code, Telephone required; Email Address optional)

a. LOCATION(S) (For actual performance, see instructions.)

Central Shipping and Receiving 2089 Tarter Ave., BLDG 559 Virginia Beach, VA 23461-2097

b. CAGE CODE (If applicable, see Instructions.)

c. COGNIZANT SECURITY OFFICE(S) (CSO) (Name, Address, ZIP Code, Telephone required; Email Address optional)

9. GENERAL UNCLASSIFIED DESCRIPTION OF THIS PROCUREMENT

The Contractor shall provide technical, project, analytical, program, and supply chain management support of policy and compliance in the areas of OM&S, Plant PP&E and AM. The Contractor shall support all OM&S and PP&E/AM management functions including policy

PREVIOUS EDITION IS OBSOLETE. Page 2 of 5DD FORM 254, APR 2018 development, financial and physical accountability, training, performance monitoring, and process improvements. The Contractor shall also support the warehousing and delivery of materials and equipment.

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

a. COMMUNICATIONS SECURITY (COMSEC) INFORMATION f. SPECIAL ACCESS PROGRAM (SAP) INFORMATION

b. RESTRICTED DATA g. NORTH ATLANTIC TREATY ORGANIZATION

(NATO) INFORMATION

c. CRITICAL NUCLEAR WEAPON DESIGN INFORMATION (CNWDI) (If CNWDI applies, RESTRICTED DATA must also be marked.) h. FOREIGN GOVERNMENT INFORMATION

d. FORMERLY RESTRICTED DATA i. ALTERNATIVE COMPENSATORY CONTROL MEASURES

(ACCM) INFORMATION

e. NATIONAL INTELLIGENCE INFORMATION:

(1) Sensitive Compartmented Information (SCI)

(2) Non-SCI

j. CONTROLLED UNCLASSIFIED INFORMATION (CUI) (See instructions.)

k. OTHER (Specify) (See instructions.)

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

a. HAVE ACCESS TO CLASSIFIED INFORMATION ONLY AT

ANOTHER CONTRACTOR'S FACILITY OR A GOVERNMENT

ACTIVITY

(Applicable only if there is no access or storage required at contractor facility.

See instructions.)

b. RECEIVE AND STORE CLASSIFIED DOCUMENTS ONLY

c. RECEIVE, STORE, AND GENERATE CLASSIFIED

INFORMATION OR MATERIAL

d. FABRICATE, MODIFY, OR STORE CLASSIFIED HARDWARE

e. PERFORM SERVICES ONLY

f. HAVE ACCESS TO U.S. CLASSIFIED INFORMATION OUTSIDE

THE U.S.,PUERTO RICO, U.S. POSSESSIONS AND TRUST

TERRITORIES

g. BE AUTHORIZED TO USE THE SERVICES OF DEFENSE

TECHNICAL INFORMATION CENTER (DTIC) OR OTHER

SECONDARY DISTRIBUTION CENTER

h. REQUIRE A COMSEC ACCOUNT

i. HAVE A TEMPEST REQUIREMENT

j. HAVE OPERATIONS SECURITY (OPSEC) REQUIREMENTS

k. BE AUTHORIZED TO USE DEFENSE COURIER SERVICE

l. RECEIVE, STORE, OR GENERATE CONTROLLED UNCLASSIFIED

INFORMATION (CUI).

(DoD Components: refer to DoDI 5200.48, only for specific CUI protection requirements. Non-DoD Components: see instructions.)

m. OTHER (Specify) (See 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)

DIRECT THROUGH (Specify below)

NSWCDD DNA, Code 104 1922 Regulus Ave, Virginia Beach, VA 23461-2097

Public Release Authority:

NSWCDD.info@us.navy.mil 540-653-8152

13. SECURITY GUIDANCE Add Signature Remove Last Signature Delete All Signatures

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

1. NISPOM, 32 Code of Federal Regulation Part 117, published 12 December 2020, effective 24 February 2021, applies to this contract.

2. The Contractor is not authorized to release any Export-controlled technical information outside the U.S. Government or to U.S.

Government contractors without first verifying the recipient’s eligibility and authority to receive export-controlled technical information by verifying that they have a current, valid Department of Defense Form 2345, Militarily Critical Technical Data Agreement.

PREVIOUS EDITION IS OBSOLETE. Page 3 of 5DD FORM 254, APR 2018

3. Block 10j: Controlled Unclassified Information (CUI), formerly For Official Use Only (FOUO), and Personally Identifiable Information (PII) generated and/or provided under this contract shall be safeguarded and marked as specified in DODI 5200.48 and DoDM 5400.07.

4. Block 11a: Classified Contract Performance is restricted to: (1) Naval Surface Warfare Center Dahlgren Division Dam Neck Annex (NSWCDD DNA), (2) Central Shipping and Receiving 2089 Tarter Avenue. Classified information will be safeguarded in accordance with the security classification guidance identified in the source material. Classified data shall not be generated under this Contract.

5. Block 11e: Contractor personnel possessing the appropriate personnel security clearance and need-to-know are authorized access to Secret classified material/hardware at designated Government facilities in performance of this contract for inventory management duties only. Contractor personnel may receive, escort, and transport classified shipments between authorized locations in accordance with applicable security regulations. No classified information or material shall be stored, retained, processed, maintained, or generated at contractor-controlled facilities.

6. Block 11j: The Contractor shall utilize the Critical Information and Indicators List, of October 2, 2025 or most recent, as published by NSWCDD, to assist in the identification of critical information associated with this contract.

7. Block 11j: Continued: During the period of this contract, the Contractor may be exposed to, use, or produce, NSWCDD Critical Information (CI) and/or observables and indicators which may lead to discovery of CI. NSWCDD’s CI will not be distributed to unauthorized third parties, including foreign governments, or companies under Foreign Ownership, Control, or Influence (FOCI).

8. Block 11j: Continued: Assembled large components/systems being transported to and from testing areas, other production or government facilities (whether or not on public roadways) shall be in an enclosed van trailer or covered flatbed trailer. Component/System outside storage, staging, and test areas shall be shielded/obscured from public view wherever physically possible.

9. Block 11j: Continued: NSWCDD’s CI shall not be publicized in corporate wide newsletters, trade magazines, displays, intranet pages or public facing websites. Media requests related to this project shall be directed to NSWCDD Public Release Authority listed in Item 12 of this DD Form 254.

10. Block 11j: Continued: Any attempt by unauthorized third parties to solicit, obtain, photograph, or record, or; incidents of loss/ compromise of government Classified or CI, Business Sensitive and Company Proprietary information related to this contract or other programs must be immediately reported to the Facility Security Officer, DCSA and/or the Naval Criminal Investigative Service, and the NSWCDD Security Office. Questions concerning these requirements shall be directed to the NSWCDD Security Office.

11. Block 11j: Continued: Performance under this contract requires the contractor to adhere to OPSEC requirements. OPSEC requirements are additional to the requirements of NISPOM, 32 CFR Part 117, therefore, the Contractor may not impose OPSEC requirements on its subcontractors unless NSWCDD approves the OPSEC requirements.

12. Block 11l: Controlled Unclassified Information (CUI), formerly For Official Use Only (FOUO), and Personally Identifiable Information (PII) generated and/or provided under this contract shall be safeguarded and marked as specified in DODI 5200.48.

-Contractor performance shall be in accordance with the NISPOM, 32 CFR Part 117 and DFARS 252.204-7012 - Safeguarding Covered Defense Information and Cyber Incident Reporting, FAR 52.204-2 - Security Requirements and NIST Special Publication 800-171. The contractor shall limit requests for Personnel (Security) Clearances (PCL) to the minimal number of personnel for operational efficiency, consistent with contractual obligations and other requirements of the NISPOM.

-This DD254 and the 32 CFR Part 117, National Security Program Operating Manual (NISPOM) are part of the contract. The contractor agrees to provide and maintain a system of security controls within its own organization according to the NISPOM. All contractor personnel will obtain and maintain the appropriate level of security clearance eligibility or access as required to perform on the level of tasking assigned. Access to classified information will be limited by the access level showing in Defense Information Security System (DISS) or subsequent system of record and need to know. All classified information shall be handled in accordance with approved security practices and procedures. Contractor personnel in contact with classified documentation, information and/or equipment shall have the proper level of access showing in DISS or the subsequent system of record and have a need to know.

-Per the DFARS clause 252.204-7000:

a) 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, unless—

(1) The Contracting Officer has given prior written approval;

(2) The information is otherwise in the public domain before the date of release; or

(3) The information results from or arises during the performance of a project that involves no covered defense information (as defined in the clause at DFARS 252.204-7012) and has been scoped and negotiated by the contracting activity with the contractor and research performer and determined in writing by the contracting officer to be fundamental research (which by definition cannot involve any covered defense information), in accordance with National Security Decision Directive 189, National Policy on the Transfer of Scientific, Technical and Engineering Information, in effect on the date of contract award and the Under Secretary of Defense (Acquisition, Technology, and Logistics) memoranda on Fundamental Research, dated May 24, 2010, and on Contracted Fundamental Research, dated June 26, 2008 (available at DFARS PGI 204.4 (DFARS/PGI view)).

(b) Requests for approval under paragraph (a)(1) shall identify the specific information to be released, the medium to be used, and the purpose for the release. The Contractor shall submit its request to the Contracting Officer at least 10 business days before the proposed date for release.

(c) The Contractor agrees to include a similar requirement, including this paragraph (c), in each subcontract under this contract.

Subcontractors shall submit requests for authorization to release through the prime contractor to the Contracting Officer.

This clause shall also be made available to Subcontractors.

-All classified information received is the property of the US Government, as such; all questions and concerns about downgrading or the

PREVIOUS EDITION IS OBSOLETE. Page 4 of 5DD FORM 254, APR 2018 declassification of classified information shall be forwarded to the NSWC Dahlgren Division Government Contracting Activity (GCA) for review and consideration. Contracting companies are not permitted to make downgrading or declassification decisions for classified information at any time. Any classified information generated in the performance of this contract shall be classified according to the markings shown on the source material as well as the applicable security classification guide (SCG). In the event of a discrepancy between source material and the SCG, the SCG shall prevail. Classified information shall be processed for appropriate disposition per 32 CFR Part 117 (NISPOM), 117.15 (i).

-FAR CLAUSE - 52.204-2 -- Security Requirements

(a) This clause applies to the extent that this contract involves access to information classified “Confidential,” “Secret,” or “Top Secret.”

(b) The Contractor shall comply with --

(1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (32 CFR Part 117);

and

(2) Any revisions to that manual, notice of which has been furnished to the Contractor.

(c) If, subsequent to the date of this contract, the security classification or security requirements under this contract are changed by the Government and if the changes cause an increase or decrease in security costs or otherwise affect any other term or condition of this contract, the contract shall be subject to an equitable adjustment as if the changes were directed under the Changes clause of this contract.

(d) The Contractor agrees to insert terms that conform substantially to the language of this clause, including this paragraph.

-The Security Classification Guide listed in Block 13 or subsequent revisions apply to this contract. Subsequent revisions shall be provided by the Government Contracting Activity as Government Furnished Information and shall be executed by the Contractor at no additional cost to the government.

-Contractor employees occupying positions requiring access to classified information, whether embedded within the command or working from another location, require, at a minimum, a favorably adjudicated T3 background investigation providing national security eligibility or an interim (temporary) national security eligibility, commensurate with contract requirements, prior to being afforded access to classified information.

-Onsite support Contractors are required to complete a security indoctrination and all required security trainings.

-Shipment of classified material must be in accordance with 32 CFR Part 117 and the NSWCDD Command Security Manual. Otherwise, a Transportation Plan will be prepared and submitted by the Contractor to the GCA for approval.

-Any non-NISP Contractor information systems (those that do not meet NIST-800-171 requirements for the protection of government-owned information that is stored, transmitted, or processed on those systems), must be reviewed, and approved or denied by the Command Information Systems Security Manager (ISSM).

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

Operations Security (OPSEC) requirements for this contract are reflected in Item 13 of this DD Form 254 under section 11(j).

NAME & TITLE OF REVIEWING OFFICIAL

Cynthia Ridgell, Code 1053 OPSEC Program Manager

SIGNATURE

14. ADDITIONAL SECURITY REQUIREMENTS

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

No Yes 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.)

OPSEC requirements are imposed on this task. Refer to Item: 13 of this DD Form 254 for applicable guidance. These OPSEC requirements cannot be imposed on subcontractors without written consent from the NSWCDD OPSEC Program Manager. These requirements shall not be imposed at an additional cost to the government.

15. INSPECTIONS

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

No Yes 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)

a. GCA NAME

NSWCDD DNA

b. ACTIVITY ADDRESS CODE (AAC) OF THE CONTRACTING OFFICE (See Instructions)

N63273

c. ADDRESS (Include ZIP Code) 1922 Regulus Avenue Virginia Beach VA 23461-2097

d. POC NAME Matt Lewisson

e. POC TELEPHONE (Include Area Code)

+1 (540) 618-4437

f. EMAIL ADDRESS (See Instructions) matthew.s.lewisson.civ@us.navy.mil

PREVIOUS EDITION IS OBSOLETE. Page 5 of 5DD FORM 254, APR 2018

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.

a. TYPED NAME OF CERTIFYING OFFICIAL (Last, First, Middle Initial) (See Instructions)

Burns, Rheannon M.

b. TITLE

Security Contracting Officer

c. ADDRESS (Include ZIP Code) Naval Surface Warfare Center Dahlgren Division 6146 Tisdale Road, Suite 237, Bldg. 492 Dahlgren VA 22448-5158

d. AAC OF THE CONTRACTING OFFICE (See Instructions)

N00178

e. CAGE CODE OF THE PRIME CONTRACTOR

(See Instructions.)

N/A

f. TELEPHONE (Include Area Code)

+1 (540) 284-1233

g. EMAIL ADDRESS (See Instructions) rheannon.m.burns.civ@us.navy.mil

h. SIGNATURE

i. DATE SIGNED (See Instructions)

18. REQUIRED DISTRIBUTION BY THE CERTIFYING OFFICIAL

a. CONTRACTOR

b. SUBCONTRACTOR

c. COGNIZANT SECURITY OFFICE FOR PRIME AND

SUBCONTRACTOR

d. U.S. ACTIVITY RESPONSIBLE FOR OVERSEAS SECURITY

ADMINISTRATION

e. ADMINISTRATIVE CONTRACTING OFFICER

f. OTHER AS NECESSARY (If more room is needed, continue in Item 13 or on additional page if necessary.)

NSWCDD DNA Contracting Officer Representative

UNCLASSIFIED

CONTINUATION – DD FORM 254 BLOCK 13

BIDDING 046-20

BLOCK 13 CONTINUATION STATEMENTS:

1. CLASSIFIED OR UNCLASSIFIED TECHNICAL PAPERS TO BE PRESENTED AT A

CLASSIFIED SYMPOSIUM MUST BE APPROVED BY THE NSWCDN CONTRACTING

OFFICER'S REPRESENTATIVE PRIOR TO THE PRESENTATION.

2. SECURITY CLASSIFICATION GUIDES (SCG’s) AND UNCLASSIFIED LIMITED DOCUMENTS

(E.G., FOUO, DISTRIBUTION STATEMENT CONTROLLED) ARE NOT AUTHORIZED

FOR PUBLIC RELEASE; THEREFORE, THEY CAN NOT BE POSTED ON A PUBLICLY

ACCESSIBLE WEB SERVER OR TRANSMITTED OVER THE INTERNET UNLESS

APPROPRIATELY ENCRYPTED. REQUEST FOR PUBLIC RELEASE CAN NOT BE

TRANSMITTED VIA THE INTERNET UNTIL THE CONTRACTOR RECEIVES FINAL

APPROVAL FROM THE COR.

3. ALL CONTRACTOR REQUESTS FOR SHARING OF CLASSIFIED AND OTHER

SENSITIVE INFORMATION BETWEEN PRIME CONTRACTS MUST BE FORWARDED IN

WRITING TO THE NSWCDL SECURITY OFFICE POC IDENTIFIED IN BLOCK 17 OF THIS

FORM FOR APPROVAL. SUBCONTRACTORS MUST SUBMIT REQUESTS FOR PUBLIC

RELEASE THROUGH THE PRIME CONTRACTOR. THE PRIME CONTRACTOR IS

REPSONSIBLE FOR SUBMITTING THE SUBCONTRACTOR’S REQUEST FOR PUBLIC

RELEASE TO THE GCA PUBLIC RELEASE AUTHORITY IDENTIFIED IN BLOCK 12.

4. PERSONNEL DESIGNATED AS DERIVATIVE CLASSIFIERS SHALL RECEIVE DERIVATIVE

CLASSIFICATION TRAINING PRIOR TO ACCESS FROM THE CONTRACTOR'S FACILITY

SECURITY OFFICER (FSO). THE FSO SHALL ENSURE PERSONNEL RECEIVE INITIAL AND

BIENNIAL TRAINING DURING THE LIFE OF THIS CONTRACT. EVIDENCE OF COMPLETION,

TRAINING CERTIFICATES OR EQUIVALENT, SHALL BE PROVIDED TO THE INFORMATION

ASSURANCE MANAGER NO LATER THAN THE INDIVIDUAL'S DUE DATE.

5. ALL CLASSIFIED DOCUMENTS MUST BE DESTROYED USING A NATIONAL SECURITY

AGENCY (NSA) APPROVED HIGH SECURITY CROSSCUT SHREDDER LISTED ON THE

NSA/CSS EVALUATED PRODUCTS LIST(EPL) FOR HIGH SECURITY CROSSCUT PAPER

SHREDDERS, OR OTHER APPROVED METHOD FOR DESTROYING CLASSIFIED

INFORMATION.

6. ALL CLASSIFIED INFORMATION INVOLVED IN SECURITY INCIDENTS SHALL BE RETAINED

AND PROVIDED TO THE CERTIFYING OFFICIAL IN ITEM 17 OF THIS DD 254 FOR

CLASSIFICATION REVIEW.

7. ALL SECURITY RELATED ISSUES, INCIDENTS, OR REQUESTS PERTAINING TO THIS

CONTRACT SHALL BE PRESENTED IN WRITING BY THE CONTRACTOR'S FACILITY

SECURITY OFFICER (FSO) TO THE INDIVIDUAL IDENTIFIED IN BLOCK 16(A) OF THIS

DD254. THE CONTRACTOR SHALL ABIDE BY OTHER REPORTING REQUIREMENTS

OUTLINED IN THE 32 CFR PART 117.

8. FORWARD A COPY OF SUBCONTRACTOR DD 254S ISSUED UNDER THIS CONTRACT TO

THE OFFICIAL SHOWN IN ITEM 16 OF THIS DD254.

CONTINUATION – DD FORM 254 BLOCK 13

BIDDING 046-20

N00178-19-9-0005/N001782390001 REV 1

CONTINUATION – DD FORM 254 ITEM 13

DODI 5200.48

SEPT 2021

CONTROLLED UNCLASSIFIED INFORMATION (CUI)

1. DEFINITION. CUI is defined as information that Government creates or possesses, or that an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Government-wide policy requires or permits an agency to handle using safeguarding or dissemination controls. CUI does not include classified information.

2. ORGANIZATIONAL INDEX GROUPINGS (OIG) and CUI CATEGORIES: CUI consists of OIGs and their categories with marking guidance. Categories have definitions and legal authorities to help determine if information meets the criteria to be marked as CUI. A complete list of OIGs and categories are located at the National Archives and Records Administration (NARA) website https://www.archives.gov/cui/registry/category-list.

3. GENERAL GUIDANCE: Security Classification Guides (SCG) and documents marked as Controlled Unclassified Information (CUI), legacy For Official Use Only (FOUO), or Distribution Statements B thru F are not authorized for public release and cannot be placed on a publicly accessible web site or web server.

a. All contractors supporting an NSWCDD DNA contract will comply with the DoD phased CUI implementation as determined by DUSN (I&S). NSWCDD DNA is currently in phase one of CUI implementation. Phase one consists of the following marking requirements:

▪ Mark emails containing CUI with CUI banner at the TOP and BOTTOM of the email

▪ Use Designation Indicator Block along with signature block or in place of signature block.

CUI contains Non-technical Information

▪ CUI attachments in emails must have _CUI at the end of the filename: Filename_CUI.

▪ All emails containing CUI must be digitally signed and encrypted.

▪ FOR OFFICIAL USE ONLY (FOUO) is no longer an authorized marking for new documents and materials in the DOD.

▪ During phase one, portion markings are not required.

Controlled by: Department of the Navy

Controlled by: NSWCDD DNA, Code, Branch, Dept

CUI Category: OPSEC (example category)

Limited Dissemination Control: FEDCON

POC: Name & office phone of CONTRACTOR who authored

CUI contains Technical Information

Controlled by: Department of the Navy

Controlled by: NSWCDD DNA, Code, Branch, Dept

CUI Category: CTI

Distribution Statement::D

POC: Name & office phone of CONTRACTOR who authored https://www.archives.gov/cui/registry/category-list

N00178-19-9-0005/N001782390001 REV 1

CONTINUATION – DD FORM 254 ITEM 13

b. Controlled Technical Information (CTI): Dissemination of CTI will be controlled with Distribution Statement (B-F) in the Distribution/Dissemination Control line with CTI as the CUI Category.

i. All controlled technical data provided to the contractor by the government will be protected from public disclosure in accordance with the markings contained therein.

ii. Follow guidance for marking CTI in accordance with DODI 5230.24, Distribution Statements for Technical Documents.

c. Marking guidance for deliverables shall be provided by the owning government office in the form of:

iii. Security Classification Guidance

iv. Properly marked source document in the form of a:

i. Memorandum,

ii. Plan,

iii. Message document (Any physical medium in or on which information is recorded or stored, to include written or printed matter, audiovisual materials, and electromagnetic storage material.)

iv. Letter, or

v. Publication.

4. TRANSMITTAL. All emails containing such information or attachments must be appropriately marked, and digitally signed and encrypted if being transmitted within Navy networks, or outside a Navy network to an approved contractor email address. All transmissions to personal email accounts (AOL, Yahoo, Hotmail, Comcast, etc.) are prohibited.

5. OFFSITE HANDLING. The contractor shall provide adequate physical protection to such information as to preclude access by any person or entity not authorized such access by the government.

6. DISCLOSURE POLICY: All other information relating to the items to be delivered or services to be performed under this contract may not be disclosed by any means without prior approval of the authorized representative of the contracting officer. Dissemination or public disclosure includes, but is not limited to, permitting access to such information by foreign nationals or by any other person or entity; publication of technical or scientific papers; advertising; or any other proposed public release. Due to the sensitivity of this program, no classified or CUI material received or generated under this contract will be transferred to any other contractor or agency without the approval of the Contracting Officer or Contracting Officer’s Representative (COR).

Additional guidance can be found at DODI 5200.48.

UNCLASSIFIED NSWCDD-M 3070.3

OPERATIONS SECURITY (OPSEC) MANUAL

Naval Surface Warfare Center Dahlgren Division Prepared by NSWCDD OPSEC Program Manager, Code 1051

Activity Security Manager (ASM)

July 2025

Table of Contents Table of Contents

1. Purpose

2. Background

3. Roles and Responsibilities

3.1 Commanding Officer (CO)

3.2 Command Security Director (CSD)

3.3 OPSEC Program Manager

3.4 Department OPSEC Representative

3.5 Public Affairs

3.6 Contracting Officers

3.7 Assigned NSWCDD Personnel

4. What is OPSEC?

5. Why do we need OPSEC?

6. OPSEC Program

7. Data Aggregation

8. Indicators

8.1 Examples of Indicators:

9. The OPSEC Process

9.1 Identify Critical Information

9.2 Analyze the Threat(s)

9.2.1 Intelligence Collection Methods

9.3 Analyze the Vulnerabilities

9.4 Asses the Risk

9.5 Apply Countermeasures

10. Program Protection Plan (PPP) process

11. OPSEC Areas of Concern

12. OPSEC Working Group

13. OPSEC Assessments

14. OPSEC and Public Release

15. OPSEC and Contracts

16. OPSEC and Social Media

18. Training

19. Continuing Awareness

20. Review Responsibility Appendix A. NSWCDD Documents OPSEC Review Process Appendix B. NSWCDD OPSEC INTERNET SEARCH FORM Appendix C. NSWCDD OPSEC FOR YOU AND YOUR FAMILY TRI-FOLD

Record of Changes

Change Number

Date of Change

YYYYMMDD

Summary of Change including Page number

Chapter #, Page, Paragraph, and any Subparagraphs

1 1 March 2021 Removed all reference to Open Skies Treaty (Chapter 12)

2 1 June 2023 Page 3. Reference (e). Removed cancelled policy NAVSEAINST 3432.1A. Replaced with current policy NAVSEAINST 3070.2. Added Reference (h) 32 CFR National Industrial Security Program Operating Manual

3 1 June 2023 Page 14, para 15. OPSEC statement for Statement of Work (SOW) updated

4 15 December 2023 Page 3, Updated Reference (f). Replaced NTTP 3-54M/MCWP 3-40.9, Operations Security of March 2009 with current policy NTTP 3-13.3M/MCTP 3-32-B, Operations Security Sep 2017

5 15 December 2023 Page 6, Updated Section 3.3 Security Coordinators – Description and bullet points b, d, and g.

6 15 December 2023 Page 7, Added bullet point a).

7 15 December 2023 Pages 13 – 14, Section 12 OPSEC Working Group. Updated mandatory OPSEC Working Group Members and added other attendees.

8 28 March 2024 Page 4. Subparagraph 3.1 Commanding Officer (CO). Added OPSEC Program Level for NSWCDD (Level II)

9 9 April 2024 General; administrative edits and formatting

10 15 July 2025 Removed reference (g) NSWCDD OPSEC Manual

11 15 July 2025 Page 6, section 3.4 changed from Security Coordinator to Department OPSEC Representative

12 15 July 2025 Page 6, section 3.4, para g. Removed “outdoor.”

13 15 July 2025 Page 8, section 9. Renamed from “Five Step OPSEC Process” to “The OPSEC Process.”

14 15 July 2025 Page 8 - 12, Sections 9.1- 9.5. Removed “Step One, Step Two, Step Three, Step Four, and Step Five.”

15 15 July 2025 Page 14, para 15. OPSEC statement for Statement of Work (SOW) updated

16 15 July 2025 Page 18. Inserted updated Appendix B

17 15 July 2025 General; administrative edits and formatting

18 15 July 2025 Updated Table of Contents

19 5 Aug 2025 Added section 17 – Personal Email

Annual Review Date of Review

YYYYMMDD

Name of Reviewer

20221013 Cyndi Howard, OPSEC Program Manager

20231215 Cyndi Howard, OPSEC Program Manager

20250715 Cyndi Howard, OPSEC Program Manager

References

(a) DoD Manual 5202.02-M, DoD Operations Security (OPSEC) Program Manual, 3 Nov 08;

Incorporating Change 2, Effective Oct 29, 2020

(b) SECNAVINST 3070.2A, Operations Security, 3 May 2019

(c) OPNAVINST 3432.1A, Operations Security, 4 Aug 2011

(d) DoD Directive 5205.02E DoD Operations Security (OPSEC) Program, 20 June 2012;

Incorporating Change 2, Aug 20, 2020

(e) NAVSEAINST 3070.2, Naval Sea Systems Command Operations Security, 31 Dec 2021

(f) NTTP 3-13.3M/MCTP 3-32-B, Operations Security Sep 2017

(g) 32 CFR National Industrial Security Program Operating Manual, 21 Dec 2020

(h) National Security Decision Directive (NSDD) 298, 22 Jan 1988

1. Purpose Per National Security Decision Directive (NSDD) 298, each federal agency or organization supporting national security missions with classified or sensitive activities is required to establish an OPSEC program. OPSEC is a formal program that identifies and protects sensitive but unclassified information that ensures mission success.

2. Background OPSEC is an operations function. Security, intelligence, and counterintelligence support its implementation. OPSEC focuses on unclassified activities, information and vulnerabilities, whereas security functions (physical security, information security systems, etc.) are primarily directed towards the protection of classified material. OPSEC is not intended to be a replacement for traditional security programs.

OPSEC is intended to deny adversaries publicly available indicators of sensitive or unclassified activities, capabilities, or intentions. Information Operations (IO) are actions taken to affect adversary information and information systems while protecting one’s own information and information systems. OPSEC supports and is integrated with the other elements of IO to deny an adversary the information needed for effective decision making and to focus and prioritize IO countermeasures to protect critical information (CI).

The potential for exploitation of open source material, including internet, media, and other generally unclassified but sensitive information significantly challenges the ability to provide adequate force protection of sensitive or classified activities. As a result, OPSEC is vital in mitigating risks associated with all operations.

3. Roles and Responsibilities

3.1 Commanding Officer (CO)

The NSWCDD CO is solely responsible for the Level III OPSEC program and must:

a) Appoint in writing a NSWCDD OPSEC Program Manager;

b) Establish and resource an effective OPSEC program;

c) Maintain an effective OPSEC program;

d) Oversee, guide, and supervise subordinate elements

3.2 Command Security Director (CSD)

The NSWCDD CSD has been delegated responsibility for the oversight of the NSWCDD OPSEC program by the NSWCDD CO. The CSD will advise the CO on all OPSEC matters.

3.3 OPSEC Program Manager

The OPSEC Program Manager is defined as an appointee who is assigned to develop and manage the OPSEC program. The OPSEC Program Manager must be appointed in writing and at a minimum a GS-12 or higher with sufficient authority and staff to manage the program for the Command. They must be a U.S. citizen and have, at a minimum, a Secret clearance.

NSWCDD OPSEC Program Manager must (when situation requires):

a) Administer the OPSEC program per references (a) through (h);

b) Develop and maintain NSWCDD’s OPSEC program to include writing policy documents;

i. Develop CIIL

ii. Review OPSEC plans associated with project testing for the departments

iii. Conduct web search by entering key words

iv. Conduct employee interviews

c) Conduct OPSEC education and training;

d) Coordinate OPSEC surveys;

e) Conduct NSWCDD’s annual OPSEC assessment;

f) Maintain an OPSEC Continuity binder;

g) Coordinate intelligence and counterintelligence support, as necessary;

h) Lead OPSEC internal working group meetings to coordinate department action and support;

i) Advise external inspectors on NSWCDD’s OPSEC program;

j) Integrate the OPSEC process into the planning and execution of applicable command operations (including routine operations, command web sites, and all outgoing message traffic);

k) Ensure command personnel are informed of CI and OPSEC measures are implemented to protect CI;

l) Ensure an initial OPSEC briefing is provided to all new personnel and annually thereafter;

m) Provide guidance to Public Affairs personnel for maintaining Operations security;

n) Participate in Naval Sea Systems Command (NAVSEA) OPSEC Community of Practice

(COP) group;

o) Ensure all public release documents for their department are reviewed for CI prior to release;

p) Attend all relevant Interagency OPSEC Support Staff courses:

i. OPSEC-1301 Fundamentals Course- completed within 30 days of assignment;

ii. OPSEC-2490 Program Manager Course- completed within 90 days of assignment; and

iii. OPSEC-1500: OPSEC and Public Release.

3.4 Department OPSEC Representative

A Department OPSEC Representative is defined as an individual who is trained in OPSEC and who works in coordination with the OPSEC Program Manager. Department OPSEC Representatives are typically the departmental Security Coordinator. Department OPSEC Representatives must:

a) Attend relevant courses to assist in executing OPSEC duties, which includes:

I. OPSEC-1301: OPSEC Fundamentals Course (within 30 days of assignment)

b) Attend OPSEC Working Group meetings and other meetings scheduled by the OPSEC Program Manager;

c) Provide guidance on developing program-specific OPSEC plans for department heads and program managers, as needed;

d) Conduct monthly web searches specific to technical department’s programs and CI;

e) Perform OPSEC assessments, surveys, awareness campaigns and other OPSEC related tasks, as assigned;

f) Inform the OPSEC Program Manager of any new programs or projects under NSWCDD jurisdiction;

g) Assist in development of an OPSEC Plan prior to any testing;

3.5 Public Affairs

Public Affairs professionals must:

a) Be properly trained per reference (a) and (b)

b) Understand NSWCDD’s Command CIIL and what level of detail its contents can be discussed as per reference (e).

c) Be responsible for the oversight and management of all content on official DON publicly-accessible websites.

d) Maintain on-going collaboration with the OPSEC Program Manager to ensure

OPSEC is maintained on command social media profiles.

e) Attend relevant courses to assist in executing OPSEC duties, which includes:

i. OPSEC 1301: Fundamentals Course (within 30 days of assignment)

ii. OPSEC-1500: OPSEC and Public Release

3.6 Contracting Officers

Contracting Officers must include OPSEC training as a stipulation in all contracts regardless of the classification of the contract.

3.7 Assigned NSWCDD Personnel

All NSWCDD personnel must:

a) Be aware of the contents in the command’s Critical Information and Indicators List.

b) Protect information useful to adversaries and potential adversaries to plan, prepare, and conduct military and other operations against the United States.

c) Properly safeguarding and handling CI by treating CI as Controlled Unclassified

Information (CUI) and applying the appropriate safeguarding controls.

d) Destroy CI when no longer needed by using NSWCDD gray shred bins or an approved shredder.

e) Understand that failure to follow OPSEC guidance can result in a security incident and/or disciplinary action.

f) Complete OPSEC training prior to accessing any DON system and then annually thereafter.

4. What is OPSEC?

OPSEC is a systematic, analytical, proven process that identifies, controls, and protects generally sensitive but unclassified information about a mission, operation, or activity. When effectively employed, it denies or mitigates an adversary’s ability to compromise or interrupt a mission, operation, or activity. A good OPSEC program forces our adversary to make decisions with insufficient information.

5. Why do we need OPSEC?

The NSWCDD mission is complex and possesses vast amounts of information our adversaries want to obtain. Protecting these national security-related missions, technologies and functions is vital to mission success and is accomplished through OPSEC planning.

Security programs and procedures already exist to protect classified information. Sensitive unclassified (critical) information and certain detectable activities (indicators) sometimes reveal friendly intentions and capabilities and must also be protected in accordance with references

(a) through (h). Such information or indicators assist those seeking to neutralize our weapon systems and technology or exploit friendly operations, activities, plans, exercises, and capabilities.

6. OPSEC Program A formal OPSEC program must be maintained with the goal of ensuring OPSEC practices are used to deny CI to potential adversaries.

An OPSEC program consists of policies, manning, training, and equipping functions necessary for OPSEC planning and execution, and to ensure all personnel understand their responsibilities to protect information reference (e).

All NSWCDD personnel are required to familiarize themselves with, and participate in, the command’s OPSEC program. The OPSEC Program Manager will conduct annual reviews to determine the status of the OPSEC program and take actions necessary to improve the program as required by references (a) through (h).

7. Data Aggregation Adversaries often collect what appears to be insignificant unclassified data. However, when this data is aggregated with other pieces of information, it can provide a comprehensive view of our capabilities and intentions the adversary can use to act against friendly forces. OPSEC is critical for mitigating these vulnerabilities to sensitive, critical or classified information. The most effective OPSEC measure is to simply refrain from saying anything without a valid need-to-know.

8. Indicators OPSEC indicators are friendly actions and open-source information that an adversary can interpret and piece together to reach conclusions or estimates of critical or classified information concerning friendly intentions, capabilities, or activities.

8.1 Examples of Indicators:

a) Predictable operating procedures as well as sudden changes

b) Product deliveries such as electronic components or machine shop orders

c) Pre-positioned equipment

d) Arrival of certain technical representatives or experts

9. The OPSEC Process The OPSEC process is continuous and interactive. The protection of essential elements of friendly information (EEFI) and subsequently, CI, is essential to the success of the OPSEC process. Failure to recognize EEFI/CI renders the OPSEC program ineffective against revealing vulnerabilities and the subsequent risk assessment process as well as enacting appropriate countermeasures against a real or potential threat. The OPSEC process consists of:

1. Identify CI

2. Analyze the Threat

3. Analyze the Vulnerabilities

4. Assess the Risk

5. Apply Countermeasures

9.1 Identify Critical Information

CI is information about Department of Defense (DoD) activities, intentions, capabilities, or limitations an adversary seeks to gain for a military, political, diplomatic, economic, or technological advantage. Such information, if revealed to an adversary, can prevent or degrade our mission accomplishment, cause loss of life, or damage friendly resources.

NSWCDD CI will vary based on Research and Development (R&D) and is best identified by the individuals responsible for planning and executing the mission. CI in operational organizations is often easy to recognize, however, in support or administratively focused organizations, CI might be more difficult to identify. When going through the process of identifying CI, be sure to consider all functional areas. NSWCDD command or program administrative staff might have valuable information that should also be assessed for its criticality.

NSWCDD CI is primarily identified through the program areas within each of the departments.

Managers and directors, administrative staff, operational personnel, even personnel not directly assigned to NSWCDD might handle portions of NSWCDD’s CI. Therefore, it is important to have personnel from each functional area involved in the process of identifying CI.

Using an adversarial approach and asking what information an adversary would want to know about the NSWCDD mission is a helpful method when trying to identify what information is critical. The CI is considered to be CUI.

9.1.1 Examples of CI

(a) Military operations: The adversary learns of the time and location of a planned attack involving one or more weapons systems from NSWCDD. As a result, losing the element of surprise could lead to significant casualties.

(b) Outdoor testing operations: The adversary learns of the time and location of a planned NSWCDD sensitive outdoor test. As a result, the adversary can be more effective in collecting information about a critical military technology or weapon system.

(c) Acquisition: The adversary learns of a new missile in the development phase that cannot be detected by adversary capabilities. As a result, the adversary begins development of countermeasures to defeat the new technology.

(d) Administration: The adversary obtains information about force protection equipment being sent to a unit operating in theater. As a result, the adversary changes its tactics, techniques, and procedures to defeat the equipment.

9.1.2 Command Critical Information and Indicators List (CIIL) Once the CI has been identified, it should be compiled into a CIIL approved by the NSWCDD CO and disseminated so personnel know what information is critical and requires protection. The Command CIIL will be transmitted in a manner that reduces the risk of aggregation and compromise as per reference (e). The Command CIIL will be reviewed and updated annually by the OPSEC Program Manager.

9.2 Analyze the Threat(s)

Threat information is necessary to develop appropriate countermeasures. The threat analysis includes identifying potential adversaries and their associated capabilities and intentions to collect, analyze, and exploit CI and indicators.

An adversary must have the intent (desire, doctrine) and capability (resources, expertise) in order to be considered a threat.

When conducting a threat analysis, NSWCDD organizations should seek support from their security, intelligence counterintelligence experts, and requisite documentation to include:

(a) NSWCDD 104 (Information systems security)

(b) NSWCDD 105 (traditional security disciplines)

(c) Threat documents or briefings from the Naval Criminal Investigative Service (NCIS).

(d) Scientific And Technical Intelligence Liaison Officer (STILO) Program

(e) Program Protection Plans (PPPs)

A thorough threat analysis will answer the following questions:

(a) Who is the adversary? What is the adversary’s intent and capability?

(b) What are the adversary’s goals?

(c) What tactics does the adversary use?

(d) What does the adversary already know about the unit’s mission? What CI has already been exposed and is known by the adversary?

(e) What are the adversary’s intelligence collection capabilities?

(f) Are Program Protection Plans (PPP’s) in place?

9.2.1 Intelligence Collection Methods

The threat to NSWCDD activities is ongoing and though there might not be any eminent threat identified, NSWCDD is still subject to collection efforts by adversaries who employ both overt and covert methods. Intelligence collection methods include:

1. Open Source Intelligence

2. Human Intelligence

3. Signals Intelligence

4. Imagery Intelligence

9.2.2 Open Source Intelligence (OSINT)

Most foreign intelligence collection comes from the systematic analysis of open source documents that may be obtained through news media, official and unofficial organization publications, professional publications, the internet, social media, meetings, seminars, and advertisements. It is estimated that 90% of foreign intelligence is derived from OSINT.

9.2.3 Human Intelligence (HUMINT)

HUMINT is the collection of information through the use of human sources. It is gathered either covertly by espionage agents with placement and access, or overtly through information available in the public domain. Information gathering is usually conducted through personal contact and social engineering. Foreign intelligence agents are tasked to target DoD personnel, particularly those with RDT&E knowledge. HUMINT relies heavily upon OSINT.

9.2.4 Signals Intelligence (SIGINT)

The SIGINT threat targets telephones (including cell phones, pagers, and residential phones), radio transmissions, tablets, smart watches, baby monitors, google glasses, wireless connections, and facsimile transmissions. Exploitation is easier for intelligence collectors when a deviation from standard security practices occurs. The most common error is discussing information over a non-secure telephone or through an unencrypted email.

9.2.5 Imagery Intelligence (IMINT)

IMINT is collected through the use of satellites, cameras, and imaging devices mounted on airplanes, ships, space vehicles, or carried by an individual on land. IMINT can provide the adversary with extremely valuable information especially during the testing and evaluation stages of a systems development.