Attachment 8 - DD Form 254 DRAFT.pdf

CLASSIFICATION (When filled in): Unclassified

PREVIOUS EDITION IS OBSOLETE. Page 1 of 4

AEM LiveCycle Designer DD FORM 254, APR 2018 PREVIOUS EDITION IS OBSOLETE. Page 1 of 4

AEM LiveCycle Designer

DD 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:

October 31, 2020

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

a. LEVEL OF FACILITY SECURITY CLEARANCE (FCL) REQUIRED

(See Instructions)

Secret

b. LEVEL OF SAFEGUARDING FOR CLASSIFIED INFORMATION/

MATERIAL REQUIRED AT CONTRACTOR FACILITY

Secret

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

a. PRIME CONTRACT NUMBER (See instructions.)

b. SUBCONTRACT NUMBER

c. SOLICITATION OR OTHER NUMBER

FA568224Q8014

DUE DATE (YYYYMMDD)

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

a. ORIGINAL (Complete date in all cases.)

DATE (YYYYMMDD)

20240711

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 ----Contractor goes here----

b. CAGE CODE c. COGNIZANT SECURITY OFFICE(S) (CSO) (Name, Address, ZIP Code, Telephone required; Email Address optional) Defense Counterintelligence and Security Agency 13873 Park Center Road, Suite 225 Herndon, VA 20171-3223 571-373-5205

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

NONE

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

57 Rescue Squadron Aviano AB, Italy

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

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

31 FW/IP

Unit 6140

APO AE 09603

DSN: 314-632-4113

31fw.informationprotection@us.af.mil

9. GENERAL UNCLASSIFIED DESCRIPTION OF THIS PROCUREMENT

Due to nature of the work being performed at the Mission Partner's premises, the member will be physically involved in mission operations that have probability of being classified at increased levels up to Secret. During work, the member will closely work with pararescueman and various support personnel at the 57RQS and in other facilities within Aviano, AB that requires security clearance levels of authorization. The Contractor shall provide a qualified and certified acquisition program manager to the 57 RQS in accordance with (IAW) the terms and conditions of the Performance Work Statement (PWS).

PREVIOUS EDITION IS OBSOLETE. Page 2 of 4

AEM LiveCycle Designer DD FORM 254, APR 2018 PREVIOUS EDITION IS OBSOLETE. Page 2 of 4

AEM LiveCycle Designer

DD FORM 254, APR 2018

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

NIPRNET

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 DoDM 5200.01, Volume 4 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)

Refer to the AFI or ask Security Manager for further information to be provided (See instructions above).

Public Release Authority:

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

Block 10e(2). NON-SCI. The contractor shall handle non-SCI or “collateral” intelligence information IAW 32 CFR Part 117 National Industrial Security Program Operating Manual, (NISPOM), DoDM 5200.01-V1-V3, Information Security Program and AFMAN16-1404, Air Force Information Security Program. Particular emphasis is placed on the contractor(s) correctly understanding and heeding intelligence portion markings. As classified material, the contractor shall afford collateral intelligence information the same protections, safeguards, and precautions required by any classified material required by DoDM 5200.01 V1-V3, unless special intelligence related handling instructions are specifically imposed. The contractor shall neither disclose, nor release intelligence derived information, whether its status is collateral or SCI, without the prior consent.

Block 10k: Access to SIPRNET is not required to perform duties, access to NIPRNET will be utilized.

Block 10j/11j/11l: Access to Controlled Unclassified Information is required. Contractors will comply with DoDI 5200.48 and Sections 252.204-7008 and 252.204-7012 of the DFARS with emphasis on identification, sharing, marking, safeguarding, storage, dissemination, destruction, and records management of CUI. In accordance with Part 2002 of Title 32, CFR, CUI requires safeguarding or dissemination

PREVIOUS EDITION IS OBSOLETE. Page 3 of 4

AEM LiveCycle Designer DD FORM 254, APR 2018 PREVIOUS EDITION IS OBSOLETE. Page 3 of 4

AEM LiveCycle Designer

DD FORM 254, APR 2018

controls identified in a law, regulation, or government-wide policy for information that does not meet the requirements for classification in accordance with E.O. 13526.

DoDI 5200.48 contains specific CUI requirements that the contractor must review and assess in entirety. The contractor will notify the government Contracting Officer if unable to meet or comply with any applicable CUI requirements.

CUI initial and annual refresher training will be required for all contractors. The contractor shall not access, download or further disseminate any CUI outside the execution of the defined contract requirements without the guidance and written permission of the government Contracting Officer. CUI must be controlled until authorized for public release in accordance with DoD Instructions (DoDIs).

In accordance with DoDIs 8500.01 and 8510.01, security controls for systems and networks are set to the level required by the safeguarding requirements for the data or information being processed, as identified in Federal Information Processing Standards 199 and

200. For DoD CUI, the minimum security level will be moderate confidentiality in accordance with Part 2002 of Title 32, CFR and NIST SP 800-171. Contractors will not use unofficial or personal (e.g., .net; .com) e-mail accounts, messaging systems, or other non-DoD information systems, except approved or authorized government contractor systems, to conduct official business involving CUI.

Contractors must monitor CUI for aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information. DoD contracts shall require contractors to report the potential classification of aggregated or compiled CUI to Contracting Officer or designated government security representative.

Block 11j. OPSEC REQUIREMENTS. The contractor will comply with installation OPSEC programs. Contractor personnel will know who their organization's OPSEC coordinator is and contact them for questions, concerns, or recommendations for OPSEC or Signature Management (SM) related topics. AFI 10-701 OPSEC requirements apply to include being familiar with the organization's critical information and protecting critical and/or sensitive information from disclosure. Contractor personnel will NOT publicly post or publish work-related information that potentially contains critical or sensitive information without explicit approval of their immediate supervisor, security office and/or OPSEC PM/SM/OPSEC coordinator, this includes NOT publicly disseminating, or publishing photographs displaying critical and/or sensitive information, nor publicly referencing, disseminating, or publishing critical and/or sensitive information already compromised. When directed or as part of established Standard Operating

Procedures, contractor personnel will destroy (burn, shred, etc.) critical and/or sensitive unclassified information no longer needed to prevent the inadvertent disclosure and/or reconstruction of this material and implement additional protection measures as ordered by the commander, director, or an individual in an equivalent position. Contractor personnel will report attempts by unauthorized personnel to solicit critical and/or sensitive information and treat such attempts as human intelligence (HUMINT) gathering and consider it a HUMINT incident. All contractor personnel who have been involved in or have knowledge of a possible HUMINT incident will report all facts immediately to the nearest supporting AFOSI office.

Block 11j. HAVE OPERATIONS SECURITY (OPSEC) REQUIREMENTS. The contractor shall accomplish the following minimum requirements in support of the user agency’s Operations Security (OPSEC) Program. Compliance with security requirements imposed by documents generated in response to DoDI 5200.39, Critical Program Information (CPI) Identification and Protection within Research, Development, Test and Evaluation (RDT&E), 28 May 2015, is required. Compliance with OPSEC measures if imposed by programs supported or by documents generated by user agency programs may be necessary. OPSEC program shall be IAW DoDM 5205.2, dated 3 November 2008 and AFI 10-701, dated 9 June 2020. Program OPSEC plans shall be coordinated with and approved by the user agency and shall be imposed on subcontractors as appropriate. Program protection measures shall be approved by the user agency and shall be applied at ALL locations where Critical Information is developed, produced, analyzed, maintained, transported, stored, tested, or used in training.”

The contractor shall develop an OPSEC Plan in accordance with DoDM 5205.2. Include OPSEC as a part of their ongoing security awareness program conducted in accordance the National Industrial Security Operating Manual. Be responsive to the user agency OPSEC Manager on a non-interference basis. Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of military operations performed by the contractor in support of the mission.

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

Add Attachment View Selected Attachment Remove Selected Attachment

NAME & TITLE OF REVIEWING OFFICIAL

Revin S. Habba, Chief, Information Protection/31st Fighter Wing

SIGNATURE

14. ADDITIONAL SECURITY REQUIREMENTS

PREVIOUS EDITION IS OBSOLETE. Page 4 of 4

AEM LiveCycle Designer

DD FORM 254, APR 2018

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

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

CSO is relieved of responsibility to inspect. Host 31st FW/IP will conduct security reviews for sensitive and classified information. 31 FW/ IP will provide security oversight and conduct required inspections IAW DD FORM 254, applicable DoD and AFI guidance, and applicable Visitor Group Security Agreement.

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

a. GCA NAME

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

c. ADDRESS (Include ZIP Code) d. POC NAME

e. POC TELEPHONE (Include Area Code)

f. EMAIL ADDRESS (See Instructions)

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)

b. TITLE

c. ADDRESS (Include ZIP Code)

d. AAC OF THE CONTRACTING OFFICE (See Instructions)

e. CAGE CODE OF THE PRIME CONTRACTOR (See Instructions.)

f. TELEPHONE (Include Area Code)

g. EMAIL ADDRESS (See Instructions)

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

DRAFT

SAMPLE

PREVIOUS EDITION IS OBSOLETE.

Page of AEM LiveCycle Designer

DD FORM 254, APR 2018

NEEDS DD67

DEPARTMENT OF DEFENSE

CONTRACT SECURITY CLASSIFICATION SPECIFICATION

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

OMB No. 0704-0567 OMB approval expires:

October 31, 2020 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 List of Attachments (All Files Must be Attached Prior to Signing, i.e., for any digital signature on the form)

13873 Park Center Road, Suite 225 Herndon, VA 20171-3223 571-373-5205

CSO: 31 FW/IP

Unit 6140

APO AE 09603

DSN: 314-632-4113

31fw.informationprotection@us.af.mil

Aviano AB, Italy

Block 10k: Access to SIPRNET is not required to perform duties, access to NIPRNET will be utilized.

Block 10j/11j/11l: Access to Controlled Unclassified Information is required. Contractors will comply with DoDI 5200.48 and Sections 252.204-7008 and 252.204-7012 of the DFARS with emphasis on identification, sharing, marking, safeguarding, storage, dissemination, destruction, and records management of CUI. In accordance with Part 2002 of Title 32, CFR, CUI requires safeguarding or dissemination controls identified in a law, regulation, or government-wide policy for information that does not meet the requirements for classification in accordance with E.O. 13526.

DoDI 5200.48 contains specific CUI requirements that the contractor must review and assess in entirety. The contractor will notify the government Contracting Officer if unable to meet or comply with any applicable CUI requirements.

CUI initial and annual refresher training will be required for all contractors. The contractor shall not access, download or further disseminate any CUI outside the execution of the defined contract requirements without the guidance and written permission of the government Contracting Officer. CUI must be controlled until authorized for public release in accordance with DoD Instructions (DoDIs). In accordance with DoDIs 8500.01 and 8510.01, security controls for systems and networks are set to the level required by the safeguarding requirements for the data or information being processed, as identified in Federal Information Processing Standards 199 and 200. For DoD CUI, the minimum security level will be moderate confidentiality in accordance with Part 2002 of Title 32, CFR and NIST SP 800-171. Contractors will not use unofficial or personal (e.g., .net; .com) e-mail accounts, messaging systems, or other non-DoD information systems, except approved or authorized government contractor systems, to conduct official business involving CUI. Contractors must monitor CUI for aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information. DoD contracts shall require contractors to report the potential classification of aggregated or compiled CUI to Contracting Officer or designated government security representative.

Block 11j. OPSEC REQUIREMENTS. The contractor will comply with installation OPSEC programs. Contractor personnel will know who their organization's OPSEC coordinator is and contact them for questions, concerns, or recommendations for OPSEC or Signature Management (SM) related topics. AFI 10-701 OPSEC requirements apply to include being familiar with the organization's critical information and protecting critical and/or sensitive information from disclosure. Contractor personnel will NOT publicly post or publish work-related information that potentially contains critical or sensitive information without explicit approval of their immediate supervisor, security office and/or OPSEC PM/SM/OPSEC coordinator, this includes NOT publicly disseminating, or publishing photographs displaying critical and/or sensitive information, nor publicly referencing, disseminating, or publishing critical and/or sensitive information already compromised. When directed or as part of established Standard Operating

Procedures, contractor personnel will destroy (burn, shred, etc.) critical and/or sensitive unclassified information no longer needed to prevent the inadvertent disclosure and/or reconstruction of this material and implement additional protection measures as ordered by the commander, director, or an individual in an equivalent position. Contractor personnel will report attempts by unauthorized personnel to solicit critical and/or sensitive information and treat such attempts as human intelligence (HUMINT) gathering and consider it a HUMINT incident. All contractor personnel who have been involved in or have knowledge of a possible HUMINT incident will report all facts immediately to the nearest supporting AFOSI office.

Block 11j. HAVE OPERATIONS SECURITY (OPSEC) REQUIREMENTS. The contractor shall accomplish the following minimum requirements in support of the user agency’s Operations Security (OPSEC) Program. Compliance with security requirements imposed by documents generated in response to DoDI 5200.39, Critical Program Information (CPI) Identification and Protection within Research, Development, Test and Evaluation (RDT&E), 28 May 2015, is required. Compliance with OPSEC measures if imposed by programs supported or by documents generated by user agency programs may be necessary. OPSEC program shall be IAW DoDM 5205.2, dated 3 November 2008 and AFI 10-701, dated 9 June 2020. Program OPSEC plans shall be coordinated with and approved by the user agency and shall be imposed on subcontractors as appropriate. Program protection measures shall be approved by the user agency and shall be applied at ALL locations where Critical Information is developed, produced, analyzed, maintained, transported, stored, tested, or used in training.” The contractor shall develop an OPSEC Plan in accordance with DoDM 5205.2. Include OPSEC as a part of their ongoing security awareness program conducted in accordance the National Industrial Security Operating Manual. Be responsive to the user agency OPSEC Manager on a non-interference basis. Protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of military operations performed by the contractor in support of the mission.