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

GEODSS DD Form 254

Attachment 1

EMSEC/TEMPEST Requirements

Addendum to DD Form 254, Block 11i

Certification and Accreditation (C&A) Process For All Classified Systems

The Emission Security (EMSEC) Process. An important part of IA is the certification and accreditation (C&A) process. The C&A process addresses vulnerabilities and threats with the goal of reducing the risk to an acceptable level. EMSEC is part of the C&A process.

Below are the major steps and where they fit into the C&A process.

- The user contacts the wing IA office whenever they intend to process classified information.

The user must do this before selecting the operational facility or room, beginning architectural engineering and facility design, procuring information systems, beginning engineering and installation, or processing classified information.

- The wing IA office determines required IA countermeasures and makes the EMSEC assessments to determine the need for EMSEC countermeasures. When needed, the wing IA office makes the EMSEC Countermeasures reviews to determine specific EMSEC Countermeasures based on the threat for that location. This is the EMSEC portion of determining the security policy for the C&A of the information system.

- The selection of EMSEC countermeasures is validated by the Air Force CTTA.

- The required countermeasures are given to the user for application or implementation.

- The wing IA office inspects the application of countermeasures for correctness and effectiveness. The inspection is made during the security test and evaluation task of the C&A.

- The wing IA office certifies the information system meets EMSEC requirements as part of the certification phase of the C&A.

Processing classified information without complying with the requirements of AFSSI 7700 is a reportable security incident under AFI 16-1404, Air Force Information Security Program, except as allowed for by waiver in AFSSI 7700.

*Wing IA Office: 21 SW Cybersecurity, 21sw.ia@us.af.mil, Peterson AFB, CO, DSN 834-4253

Attachment 1

GEODSS DD Form 254

Attachment 2

OPERATIONS SECURITY (OPSEC)

Addendum to DD Form 254, Item 11.j.

1. PURPOSE: This section outlines the requirements and procedures necessary to protect Critical Information for Operations Security (OPSEC).

2. MISSION:

· To maintain a continuing awareness of adversary interest in center actions and adversary intelligence collection capabilities.

· To understand the need to identify and protect classified and unclassified indicators, which occur, reveal sensitive information.

· To evaluate the effectiveness of OPSEC measures taken to preclude or reduce adversary acquisition and exploitation of sensitive information.

3. DEFINITION:

OPSEC is the process of analyzing friendly actions attendant to military operations and other activities to:

· Identify those actions that can be observed by adversary intelligence systems.

· Determine indicators hostile intelligence systems might obtain that could be interpreted or pieced together to derive critical information in time to be useful to adversaries.

· Select and execute measures that eliminate or reduce to an acceptable level the vulnerabilities of friendly actions to adversary exploitation.

4. OBJECTIVES:

· To protect planned operational center activities by preventing the inadvertent disclosure of unclassified information relating to or revealing a possible classified operation.

· To preserve secrecy concerning specific scenario events and a NORAD response to these events.

· To identify OPSEC vulnerabilities and recommend protective measures which will serve to enhance the security of future operations.

5. TASKS:

Task requirements are outlined in the Performance Work Statement for this effort and at a minimum must include:

· Release of the organizations Critical Information List to the contractor.

· Threat information available (Threat Working Group Minutes).

· Contractor receiving OPSEC training from the sponsoring organization.

· Specific OPSEC countermeasures as needed.

Attachment 2

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 [2] (All Files Must be Attached Prior to Signing, i.e., for any digital signature on the form) GEODSS EMSEC_TEMPEST Attachment 1.docx GEODSS OPSEC Attachment 2.docx

21 SW/IP, Peterson AFB, CO 80914-1560 20 SPCS Det 1, PO Box W, Socorro, NM 87801 20 SPCS Det 2, PSC 466 Box 51 FPO, Diego Garcia 96595 20 SPCS Det 3, 535 E. Lipoa Pkwy Ste 200, Kihei, HI 96753

377 MSG/SCXF (CA624520), CRO

Det 2, 22 SOPS, CRO Det 15, AFRL, CRO

Ref Item 10a: If the contractor is authorized to receive Government furnished cryptographic equipment, the guidance will state that fact. Access to classified COMSEC information requires a final U.S. Government clearance at the appropriate level. Further disclosure of COMSEC information by a contractor, to include subcontracting, requires approval of the GCA. Non-accountable COMSEC information, though not tracked in the COMSEC material control system, may still require a level of control within a document control system. Refer to NSA/CSS Manual 3-16, “Control of Communications Security Material,” and the Committee on National Security Systems Instruction (CNSSI) 4001, “Controlled Cryptographic Items,” for guidance. If access to COMSEC information is required at Government facilities, or the material is under Government control, contractor personnel will follow the security requirements of the host government activity.

Ref Item 10j: DoD Components; refer to DoDM 5200.01, Volume 4, “DoD Information Security Program: Controlled Unclassified Information (CUI),” available at http://www.esd.whs.mil/DD/DoD-Issuances/, when considering protection for CUI. Non-DoD Components must consult with their Component specific information security policy office to determine if they have any existing authority by law, government-wide policy or government-wide regulation to impose this requirement.

Ref Item 11a: Contractor performance is restricted to 20 SPCS, Det 1 at Stallion Range Center, White Sands Missile Range (WSMR), New Mexico (NM); 20 SPCS, Det 2 at the Naval Support Facility (NSF), Diego Garcia, British Indian Ocean Territory (BIOT); and 20 SPCS, Det 3 at the Maui Space Surveillance Complex, Hawaii (HI). Contractor will reference the appropriate security classification guidance when generating or deriving classified material or hardware. All classified information received or generated will be properly stored and handled according to the markings on the material. All classified information received or generated is the property of the U.S. government. At the termination or expiration of this contract, the U.S. government will be contacted for proper disposition instructions. Contractor will abide by the following security classification guidance (subsequent revisions/changes apply to this contract):

a. Dedicated Space Surveillance Network Security Classification Guide, 31 Dec 05 (or current edition), OPR: HQ AFSPC/XOC, Peterson AFB, CO 80914-5000

b. Security Classification Guide for Space Surveillance Operations (SSOps), 28 Jul 17 (or current edition), OPR: HQ USSTRATCOM/J33, Offutt AFB, NE 68113-6300

Ref Item 11e: Contract provides support for maintenance services on equipment which processes classified information. Actual knowledge of, generation, or production of classified information is not required for performance of the contract. Cleared personnel are required to perform this service because access to classified information cannot be precluded by escorting personnel.

Any classification guidance will be provided by the using activity.

Ref Item 11f: Diego Garcia, British Indian Ocean Territory (BIOT)

Ref Item 11j: See DD Form 254 Attachment 2, Operations Security (OPSEC) requirements.

Ref Item 11l: CUI - DoDM 5200.01 Vol 4, Enclosure 3 para 1(e); DFARS 252.204-7000, Disclosure of Information; DoDD 5230.20, Visits and Assignments of Foreign Nationals.

Ref Item 11m. Provide the information required by contract clauses 52.204-2, 52.204-9000/52.204-9001 to the Info Sec Prog Mgr (ISPM). Contractor requires access to SIPRNET and JWICS for contract performance.

Ref Item 12: Public Release: No public release of SCI is authorized. For OPSEC, the Contractor is to submit requests through the Contracting Officer for OPSEC Program Manager review and public release authorization. The Contracting Officer will provide contractor with written approval/disapproval. (T-1) Information requiring AF or DoD–level review will be reviewed by the unit’s OPSEC Program Manager or Coordinator who will in-turn forward to the entry-level public affairs office through the AFIMSC Public Affairs Office to the Secretary of the Air Force, Office of Public Affairs, Security and Review Division (SAF/PAX), 1690 Air Force Pentagon, Washington DC 20330-1690. MAJCOM/DRUs will send information requiring AF or DoD-level review directly to SAF/PAX.

Ref Item 13b: The SCIF at 20 SPCS, Det 1, WSMR, NM will be used to perform SCI contractual requirements. SCI material released to the contractor under this contract will be separately stored and maintained only in such properly accredited facilities. SCIFs owned by an organization other than AFSPC will be used only when covered by a co-utilization Memorandum of Agreement (MOA) between AFSPC and the sponsor of the facility. The supporting SSO is SSO AFSPC.

Ref Item 13c: The following documents with subsequent revisions or changes will be used for specific SCI security classification guidance on this contract:

DCID 1/20 - Security Policy Concerning Travel and Assignment of Personnel with Access to SCI (29 DEC 91) DCID 6/1 - Security Policy for Sensitive Compartmented Information and Security Policy Manual [formerly DCID 1/19] (1 MAR 95) ICD 301 - National Open Source Enterprise [formerly DCID 1/7] (11 JUL 06) ICD 704 - Personnel Security Standards and Procedures Governing Eligibility for Access to Sensitive Compartmented Information and Other Controlled Access Program Information [formerly DCID 6/4] (1 OCT 08) ICD 705 - Sensitive Compartmented Information Facilities [formerly DCID 6/9] (5 MAY 11) DoDM 5105.21, Vol 1 - Sensitive Compartmented Information (SCI) Administrative Security Manual: Administration of Information and Information Systems Security (OCT 12) DoDM 5105.21, Vol 2 - Sensitive Compartmented Information (SCI) Administrative Security Manual: Administration of Physical Security, Visitor Control, and Technical Security (OCT 12) DoDM 5105.21, Vol 3 - Sensitive Compartmented Information (SCI) Administrative Security Manual: Administration of Personnel Security, Industrial Security, and Special Activities (OCT 12) AFI 14-302 - Control, Protection, and Dissemination of Sensitive Compartmented Information (18 JAN 94) AFI 14-303 - Release of Intelligence to U.S. Contractors (1 APR 99) AFMAN 14-304 - The Security Use, and Dissemination of Sensitive Compartmented Security Information (23 Dec 16) EO 12333 - United States Intelligence Activities (AMENDED by EO 13470, 2008) EO 13526 - Classified National Security Information (29 DEC 09) {replaced EO12958} AFI 16-1404 - Air Force Informational Security Program (29 MAY 15) AFI 16-1406 - Air Force Industrial Security Program (25 AUG 15) AFI 31-501 - Personnel Security Program Management (27 JAN 05) DoDM 5200.01 Vol 1-4 - Information Security Program (24 FEB 12) DoDM 5220.22 - National Industrial Security Program (18 MAR 11) DoD 5200.2-R - Personnel Security Program (JAN 87) DoD 5220.22-R - Industrial Security Regulation (4 DEC 85)

Ref Item 13d: Inquiries pertaining to classification guidance on SCI will be directed to the Contract Monitor.

Ref Item 13i: Release of Information. SCI with restrictive caveats (e.g. ORCON, PROPIN, etc.) will be released to contractors only when originator approval has been obtained. The contractor will control SCI, which has been originated or obtained under this contract as follows: The contractor may release such material to any contractor employee working against a billet under this contract only when a need-to-know exists. The contractor will release such material to any Special Security Office personnel assigned to HQ AFSPC or DIA upon demand by such personnel. The contractor may release such material to any other personnel, including contractor and subcontractor employees, and employees of any Federal Government agency, only upon prior written approval from the SCI Contract Monitor. An access certification to an AFSPC contractor-occupied SCIF does not constitute approval to release AFSPC contractual material to these other personnel; Contract Monitor approval is required. Contract Monitor approval of an AFSPC contractor visit certification or permanent certification to another facility will constitute approval to discuss contractual material at facility to be visited.

Ref 13j.: Any SCI released to the contractor in support of this contract remains the property of the DoD department, agency, or command that releases it. The contractor will maintain active accountability of all SCI released to his/her custody, regardless of whether the release is within a contractor or US Government SCIF. Upon completion/cancellation of the contract, the contractor must return all such material to SSO AFSPC unless a follow-on contract specifies that the material will be transferred to a subsequent contract. SCI inventories will be conducted IAW DIA Manual 50-5 and AFMAN 14-304.

Ref 13l: This contract requires use of the Defense Courier system. The SSO will validate Defense Courier Service requirements.

Ref 13m: Electronic processing of classified information is permitted only when formal AIS accreditation is obtained and maintained IAW JDCSISSS and DCID 6/3, AND the requirements of AFMAN 14-304 have been met as determined by an accredited TEMPEST authority. This contract requires electronic process of SCI. TEMPEST accreditation of ADPS must be obtained IAW the above reference. Operational accreditation of ADPS using software must be obtained IAW DIA 50-5, Vol II. Security provisions of DIA Manuals 50-3, 50-4, 50-5 Vol I, and AFMAN 14-304 also apply and must be entered in item 13.c. The CSSO will appoint an Information Systems Security Officer (ISSO) and advise SSO AFSPC of this appointment.

Ref 13n: Contractor Special Security Officers (CSSOs) must coordinate with the SCI Contract Monitor and obtain the concurrence of SSO AFSPC prior to subcontracting any portion of SCI efforts involved in this contract.

Ref 13o: No contractor personnel will be granted access to SCI materials under this contract unless they are filling a DoD SCI billet. The contractor will coordinate with SCI Contract Monitor to ensure adequate billets are requested under this contract. Multiple contract employees sponsored by the organizations other than Air Force Space Command must be certified to SSO AFSPC for use on the contract.

Ref 13p: The contractor will designate a Special Security Point of Contact (POC) to SSO AFSPC. The POC will be responsible for all personnel and information security transactions between the contractor and SSO AFSPC.

Ref 13q: Contractor will not use references to SCI accesses, even by unclassified acronyms, in advertising, promotional efforts, or recruitment for employees.

Ref 13r: The following activity is designated as the User Agency SSO for SCI requirements IAW DIA Manual 50-5: HQ AFSPC/A2S, Peterson AFB CO 80914-4313.

Ref 13s: The complete name, address, organization, and duty phone of the Contract Monitor will be provided to the SSO.

21 OG Security Manager rep: Laura McDonough, DAFC GEODSS Program Manager rep: Julie Boyatt, DAFC Industrial Security Program Mgr (ISPM)

Peterson AFB CO 80914-1285 Address: 135 Dover Street, Suite 2225 Peterson AFB CO 80914-1285