Attachment 03_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.

SSPARS DD Form 254 FA2518-22-C-0001

Attachment 1

EMSEC Requirements (Addendum to DD Form 254, item 11.i.)

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: P-S Garrison Cybersecurity, P_SGAR.IA@us.af.mil, Peterson SFB, CO, DSN 834-

SSPARS DD Form 254 FA2518-22-C-0001

Attachment 2

OPERATIONS SECURITY (OPSEC)

(Addendum to DD Form 254, item 11.j.)

GENERAL:

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:

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

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

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

4. OBJECTIVES:

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

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

c. 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 Statement of Work for this effort and at a minimum must include:

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

b. Threat information available (Threat Working Group Minutes).

c. Contractor receiving OPSEC training from the sponsoring organization.

d. Specific OPSEC countermeasures as needed.

DRAFT

SAMPLE

PREVIOUS EDITION IS OBSOLETE.

Page of

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:

May 31, 2022 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.)

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

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" Hide Attachment Bar

(NAESOC)

Defense Counterintelligence & Security Agency (DCSA) P.O. Box 644 Hanover, MD 21076

Force Station (SFS), MA; 7 SWS at Beale Air Force Base (AFB), CA; 12 SWS at Pituffik Space Base (SB), GL; 13 SWS at Clear SFS, AK; Royal Air Force (RAF) Fylingdales, UK; and Cheyenne Mountain SFS, CO Enter general unclassified description of this procurement.: Contract is for operations and maintenance on a continuous basis 24-hours-a-day, 7-days-a-week (24/7) in support of Missile Warning, Missile Defense, and Space Domain Awareness (SDA) missions under SpOC Space Delta 4 at six (6) installations/sites: Cape Cod SFS, MA (6 SWS); Beale AFB, CA (7 SWS); Pituffik SB, GL (12 SWS); Clear SFS, AK (13 SWS); and Secure Communications at RAF Fylingdales, UK. Contract also includes operations and maintenance on a continuous basis 24-7 hours-a-day, 7-days-a-week in support of the Long Range Discriminator Radar (LRDR) at Clear SFS, AK (13 SWS), with operations at Beale AFB, CA (7 SWS) and Cheyenne Mountain SFS, CO.

21 SW/IP, Peterson SFB, CO 80914-1560;

6 SWS/SF, Cape Cod SFS, MA 02561-0428;

7 SWS/SF, Beale AFB, CA 95903;

12 SWS/DOO, Pituffik SB, Greenland, APO AE 09704;

13 SWS/SM Clear SFS, AK 99704;

RAF Fylingdales, UK, 100 ARW/IP, RAF Mildenhall, UK APO AE09459; Cheyenne Mountain SFS, CO

Ref. 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. 10g: Specific briefings are required for access to NATO IAW DoDM 5200.01 V1_AFMAN16-1404 V1. Prior approval of the contracting activity is required for subcontracting. Access to classified NATO information requires a final U.S. Government clearance at the appropriate level.

Ref. l0h: Access requires a final U.S. Government clearance at the appropriate level.

Ref. 10j: The contractor shall comply with DoDI 5200.48_DAFI 16-403, Controlled Unclassified Information (CUI), DoDM 5200.01 V1_AFMAN 16404 V1, Air Force Security Program, and DoDM 5400.07_AFMAN 33-302, DoD Freedom of Information Act (FOIA) Program. The contractor shall monitor CUI aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information.

Ref 11.a.: The managing government activity will furnish complete classification guidance performance on this contract. If any classified information is generated in the performance of this contract at the identified location, the contractor shall apply derivative classification and markings consistent with the source material.

Ref 11.c.: 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. Ground-Based Radar Missile Warning Systems, 1 Sep 03, OPR: HQ SpOC/XOSM, Peterson SFB, CO 80914-4250

b. Dedicated Space Surveillance Sensors Security Classification Guide, 30 Sep 05, OPR: HQ SpOC/XO, Peterson AFB, CO 80914-5000

c. Milstar/Advanced Extremely High Frequency (AEHF) Security Classification/Declassification Guide, Revision A, 14 Aug 09, OPR: HQ SpOC, Peterson SFB, CO 80914-4630

d. Security Classification Guide for Space Surveillance Operations (SSOps), 28 Jul 17, OPR: HQ USSTRATCOM/J3I, Offutt AFB, NE 68113-6300

Ref. 11e: Equipment Maintenance Services: 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 this 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 th e using activity.

Ref. 11f: RAF Fylingdales, UK and Pituffik SB, Greenland

Ref. 11i.: TEMPEST - If movement or removal of SIPR or JWICS equipment occurs, the user will update the Room diagram and Equipment list, and send these to the TEMPEST manager. C&A process provided at Attachment 1.

Ref 11.j.: The contractor is not responsible to develop an OPSEC plan.

Ref. 11l: CUI - DoDM 5200.01 V 4, Enclosure 3 para l(e); DFARS 252.204-7000 ref i; DoDD 5230.20 (Visits and Assignments of Foreign Nationals)

Ref. 13a.: Contract Expiration Date: 31 Jan 36

Ref. 13b: The SCIFs at Cape Cod SFS, MA (6 SWS), Beale AFB, CA (7 SWS), Clear SFS, AK (13 SWS) and Pituffik SB, GL (12 SWS) 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 Space Operations Command (SpOC) will be used only when covered by a co-utilization Memorandum of Agreement (MOA) between SpOC and the sponsor of the facility. The supporting SSO is SpOC/SSO, Peterson SFB CO 80914-4313

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

ICD 301 - National Open Source Enterprise [formerly DCID 1/7] (11 JUL 06) ICD 703 - Protection of Classified National Intelligence, Including Sensitive Compartmented Information (21 Jun 2013) 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 V1.5 - 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} AFMAN 16-1406V2 - Air Force Industrial Security Program (8 MAY 2020) AFI 31-501 - Personnel Security Program Management (27 JAN 05) DoDM 5200.01 Vol 1-4 - Information Security Program (24 FEB 12) DoDM 5220.23V1 - National Industrial Security Program (19 APR 2022) DoD 5200.2 - Personnel Security Program (3 APR 2017) 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM) (24 FEB 21) {replaced DoD 5220.22M}

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

Ref 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 SpOC 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 SpOC contractor-occupied SCIF does not constitute approval to release SpOC contractual material to these other personnel; Contract Monitor approval is required. Contract Monitor approval of an SpOC 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 SpOC SSO 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. 131: 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 13c. The CSSO will appoint an Information Systems Security Officer (ISSO) and advise SpOC SSO of this appointment.

Ref. 13n: Contractor Special Security Officers (CSSOs) must coordinate with the SCI Contract Monitor and obtain the concurrence of SpOC SSO 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 Space Operations Command must be certified to SpOC SSO for use on the contract.

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

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 UserAgency SSO for SCI requirements IAW DIA Manual 50-5: SpOC/SSO, Peterson SFB CO 80914-4313.

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

SSPARS Program Manager rep: Willard Viar, GS-12 Delta 4 Security Manager rep: David Callahan, GS-12 COMSEC Manager rep: Ronnie Enciso, GS-11 TEMPEST Manager rep: Mark Evanger, GS-14 Chief, Special Security Office (SSO) rep: Frank Pablo Industrial Security Program Mgr (ISPM)

Peterson SFB, CO 80914-1285 Enter address (include zip code).: 135 Dover Street, Suite 2041 Peterson SFB, CO 80914-1285