ATT (8) DD254.pdf

Please wait...

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

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

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

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

DD-254

OPSEC Attachment

CUI

NAVAIR OPERATIONS SECURITY (OPSEC) REQUIREMENTS

1. All work is to be performed in accordance with Department of Defense (DoD) and Department of

Navy (DON) Operations Security (OPSEC) requirements, per the following:

a) National Security Decision Directive 298

b) DoDD 5205.02, DoD Operations Security (OPSEC) Program

c) DoD 5205.02-M, DoD Operations Security (OPSEC) Program Manual

d) OPNAVINST 3432.1A, DON Operations Security

2. The contractor shall accomplish the following minimum requirements in support of the Naval Air

Systems Command (NAVAIR) OPSEC Program:

a) Determine Critical Information (CI) in accordance with DoD 5205.02-M (Appendix 1 through

Encl 3). CI includes those facts, which individually, or in the aggregate, reveal sensitive details about NAVAIR or the contractor’s security or operations related to the support or performance of this Statement of Work (SOW), and thus require a level of protection from adversarial collection or exploitation not normally afforded to unclassified information.

b) Practice OPSEC and implement countermeasures to protect CI and other sensitive unclassified information and activities, especially those activities or information which could compromise classified information or operations, or degrade the planning and execution of military operations performed or supported by the contractor in support of the mission. Protection of

CI will include the adherence to and execution of countermeasures which the contractor initiates or provided by NAVAIR, for CI on or related to the SOW.

c) Sensitive unclassified information is that information marked Controlled Unclassified

Information (CUI), Privacy Act of 1974, COMPANY PROPRIETARY, and also information as identified by NAVAIR or NAVAIR Contracting Officer Security Representative (COSR).

d) NAVAIR has identified the following baseline CI:

DAILY ACTIVITIES

1) Details regarding military operations, missions and exercises

2) Details of U.S. systems supporting combat operations (numbers, timelines, locations effectiveness, unique capabilities, etc.)

3) Operational characteristics for new or modified weapon systems (Probability of Kill

(PK), Countermeasures, Survivability, etc.)

4) Required performance characteristics of U.S. systems using leading edge or greater technology (new, modified or existing)

5) Test or evaluation information pertaining to schedules of events during which CI may be captured

6) Details of NAVAIR unique Test or Evaluation capabilities (disclosure of unique capabilities)

7) Any material designated at Controlled Unclassified Information (CUI) such as

NOFORN, and other distribution statement-controlled documents as well as

Proprietary, or Business Sensitive Information (to include Source Selection

Information or other sensitive competitive information)

8) Known or probable vulnerabilities to any U.S. system and their direct support systems

SECURITY RESPONSIBILITIES

9) Government personnel information that would reveal force structure and readiness

10) Detailed facility maps or installation overhead photography (photo with annotation of

Command areas or greater resolution than commercially available)

11) Force Protection specific capabilities or response protocols

12) Vulnerabilities in Command processes, disclosure of which could allow circumvention of security, financial, personnel safety, or operations procedures

13) Details of COOP, NAVAIR emergency evacuation or emergency recall procedures

14) Network User ID’s and Passwords and access codes to restricted/controlled spaces

15) Existence and/or details of intrusions into or attacks against DoD Networks or

Information Systems, including, but not limited to, tactics, techniques and procedures used, network vulnerabilities exploited, and data targeted for exploitation

16) Compilations of information that directly disclose Command CI

17) Command leadership and VIP agendas, reservations, plans/routes, etc.

3. All CI developed by the contractor and/or NAVAIR, in electronic or hardcopy form, shall be protected by a minimum of the following countermeasures:

a) All emails containing CI must be DoD Public Key Infrastructure (PKI) signed and PKI encrypted

b) CI may not be sent via unclassified fax when practical

c) CI may not be discussed via non-secure phones when practical

d) CI may not be provided to individuals that do not have a need to know it in order to complete their assigned duties

e) CI may not be disposed of in recycle bins or trash containers unless made unusable (i.e.

shredded)

f) CI may not be left unattended in uncontrolled areas

g) CI in general should be treated with the same care as CUI or Proprietary information

h) CI must be destroyed in the same manner as CUI

i) CI must be destroyed at contract termination or returned to the government at the government’s discretion

4. The contractor shall document items of CI that are applicable to contractor operations involving information on or related to the SOW. Such determinations of CI will be completed using the DoD

OPSEC Five-Step process as described in National Security Decision Directive (NSDD) 298 and

DoDMAN 5205.02 (App 1 to Encl 3).

5. Per DoDM 5205.02M (Encl 6), OPSEC training must be included as part of the contractors ongoing security awareness program. Basic OPSEC training, produced by the Interagency OPSEC

Support Staff (IOSS), can be found here - OPSE1301 OPSEC Fundamentals If this link does not work, please request a CD copy via NAVAIR Operations Officer.

6. If contractor cannot resolve an issue concerning OPSEC they will contact the COR (who will consult with the appropriate OPSEC Manager).

8. All above requirements shall be passed to all Sub-contractors.

https://www.iad.gov/ioss/department/opsec-fundamentals-course-opse1300-opse1301-opse1300e-10045.cfm

DRAFT

SAMPLE

PREVIOUS EDITION IS OBSOLETE.

Page of

DD FORM 254, MAY 2019

NEEDS DD67

DEPARTMENT OF DEFENSE

CONTRACT SECURITY CLASSIFICATION SPECIFICATION

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

OMB No. 0704-0567 OMB approval expires:

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

RETURN COMPLETED FORM AS DIRECTED IN THE INSTRUCTIONS.

1. CLEARANCE AND SAFEGUARDING

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

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

a. ORIGINAL (Complete date in all cases.)

b. REVISED (Supersedes all previous specifications.)

4. IS THIS A FOLLOW-ON CONTRACT?

If yes, complete the following:

Classified material received or generated under

5. IS THIS A FINAL DD FORM 254?

If yes, complete the following:

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

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

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

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

e. NATIONAL INTELLIGENCE INFORMATION:

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

12. PUBLIC RELEASE

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

13. SECURITY GUIDANCE

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

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

14. ADDITIONAL SECURITY REQUIREMENTS

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

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

15. INSPECTIONS

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

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

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

17. CERTIFICATION AND SIGNATURES

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

18. REQUIRED DISTRIBUTION BY THE CERTIFYING OFFICIAL

9.0.0.2.20120627.2.874785 DD 254, DoD Contract Security Classification Specification whs.mc-alex.esd.mbx.formswebmaster@mail.mil

WHS

List of Attachments [1] (All Files Must be Attached Prior to Signing, i.e., for any digital signature on the form) 2013OPSECANNEX.pdf

Marine Corps Air Station (MCAS) Miramar, CA Joint Reserve Base McGuire-Dix-Lakehurst, NJ

Determination of need-to-know in connection with a classified visit is the responsibility of the individual/host who will disclose the classified information.

All contracts with non-Sensitive Compartmented Information and Non-Compartmented work that may reveal mission-related information of a sensitive activity or sensitive operation should be routed to the NAVAIR STILO for approval.

The COR, TPOC, and Government Security Office, concerning instances of possible loss, compromise, and electronic spillage of classified or controlled unclassified information shall be notified immediately upon discovery and/or no later than 72 hours of discovery.

Block 10.j/11.l – Controlled Unclassified Information including Legacy FOUO and Covered Defense Information (meeting the definition of 48 CFR 252.204–7012(a)) generated and/or provided under this contract shall be marked and safeguarded as specified in DoD Instruction 5200.48 (Controlled Unclassified Information) (CUI)) available at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/520048p.PDF. Any product containing Covered Defense Information shall be assigned the appropriate distribution statement using the criteria set forth in DoDI 5230.24 (Distribution Statements on Technical Documents); and have this statement displayed per DoDI 5230.24, Enclosure 3-4.

All Covered Defense Information (CDI), Legacy FOUO, and program Controlled Unclassified Information (CUI) data transmitted and safeguarded via electronic means shall use approved encryption. The Contractor shall ensure that when transmitting CUI/Legacy FOUO/CDI over non-secure e-mail (e.g. not connected to the Navy Marine Corps Intranet through Broadband Unclassified Remote Access System / Virtual Private network), those transmissions are encrypted using Department of Defense Public Key Infrastructure (PKI), or an approved DoD External Certificate Authority, in accordance with Public Key Infrastructure & Public Key Enabling, DoDI 8520.02, 24 May 2011.

Block 11.a – All classified information/material shall be provided by the contractor facility or Government Contracting Activity (GCA) and safeguarded at the approved actual performance site.

Block 11.j – PMA205, has made a determination that BASIC Operations Security (OPSEC) measures are sufficient to protect the contracted related Critical Information associated with this Contract. The NAVAIR DD254 OPSEC Annex, dated Jan 2013, shall be included as an attachment to this DD254. When basic OPSEC measures are prescribed, there shall be no required OPSEC CDRLs associated with this contract. However, the contractor will adhere to all OPSEC requirements specified in the NAVAIR DD254 OPSEC Annex. The Contractor shall be responsible for subcontractor implementation of the OPSEC Program requirements for this contract.

Specific Security Classification Guidance (SCGs), to include subsequent upgrades/revision(s), applying to classified performance on this contract, shall be provided by the Contracting Officer Representative or Technical Point of Contact, identified in Blk 16, as Government Furnished Information (GFI); and shall be executed by the Contractor without obligation to modify this DD Form 254. If additional security classification is required, contact the COR identified in Blk 16d.

************************************************** Nothing Further ************************************************

OPSEC in contract

Orlando, FL 32826 Address: 47123 Buse Road Patuxent River MD