Attachment 3 - DD254 Contract Security Classification Specification.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.

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

Enterprise Protection (SSC/CIO) 483 N. Aviation Blvd.

El Segundo, CA 90245 CSO: Space Systems Command Enterprise Protection (SSC/CIO) 483 N. Aviation Blvd.

El Segundo, CA 90245 CSO: Space Systems Command Enterprise Protection (SSC/CIO) 483 N. Aviation Blvd.

El Segundo, CA 90245 CSO: Space Systems Command Enterprise Protection (SSC/CIO) 483 N. Aviation Blvd.

El Segundo, CA 90245 CSO: Space Systems Command Enterprise Protection (SSC/CIO) 483 N. Aviation Blvd.

El Segundo, CA 90245

SAF/AAZ (via OSI/PJ)

483 N. AVIATION BLVD, EL SEGUNDO, CA 90245

PublicAuthority: SSC/PA, SSC.PA@spaceforce.mil, 310-652-1131

483 N. AVIATION BLVD, EL SEGUNDO, CA 90245

By signing this form, the requesting Government program office and the servicing Contractor (or Subcontractor) verify that the stated access requests on this form are based on legitimate and bona fide need(s)/requirement(s) of the Government.

General Security - Space Systems Command, Assured Access To Space (SSC/AATS) has determined that performance of this contract requires that the contractor, subcontractor(s), vendor(s), etc. (herein known as contractor), requires access to classified National Security Information (herein known as classified information). Classified information is Government information which requires protection in accordance with Executive Order 13526, Classified National Security Information, and supplementing directives.

The Contractor shall abide by the requirements set forth in the DD Form 254, Contract Security Classification Specification, Included in the contract, and the 32 Code of Federal Regulation (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM) for the protection of classified information at its cleared facility if applicable, as directed by the Defense Counterintelligence and Security Agency (DCSA).

Any firm or business under contract with the Air Force (AF), which requires access to classified information, will require a facility security clearance commensurate with the level of access required. Firms that do not possess a facility clearance, or the requisite level of facility clearance, will be sponsored for a Department of Defense facility clearance.

For access to classified information contractor will ensure all required actions IAW 32 Code of Federal Regulation (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM) are completed for personnel working on this contract. Interim clearances are authorized except when the contractor will require NATO and COMSEC access, where a finalized security clearance is required. Security clearances are in accordance with the 32 Code of Federal Regulation (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM). Access to SCI will be in accordance with the current SCI addendum and DOD Manual 5105.21 Volumes 1-3 for SCI management.

This is also applicable to Contractor and Subcontractor personnel who are visiting or on a temporary duty assignment at the NSSL launch sites. This requirement is for personnel who have or may need access to launch site restricted or controlled areas containing (NSSL) National Security Space Launch and/or Information Systems, which directly affect a launch system. Alternate Personnel Security determinations (when applicable) must be appropriately authorized in the DAFI31-101_SSCSUP_DAFGM2021-1 supplement and validated/approved.

Security Management -The contractor shall appoint a senior official to act as the Facility Security Officer. The individual will interface with SSC/AA security on all security matters, to include physical, personnel, industrial, information, program protection and cybersecurity and will protect all Government information and data accessed by the Contractor.

Contractor employees who become eligible for access to classified National Security Information shall receive annual refresher training in accordance with the 32 Code of Federal Regulation (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM). In the event classified information is inadvertently received by a contractor who does not hold an active security clearance at the appropriate level, a Government employee or Contractor with the appropriate security clearance equal to or higher than the classified information received, will take possession of the material and shall safeguard and store the information in accordance with standards set forth in the 32 Code of Federal Regulation (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM). The inadvertent disclosure will be immediately reported to their supervisor and then to SSC/AA's Security Manager for action as appropriate.

Period of Performance: 14 Nov 2024 - 13 Nov 2025, Four (4) 1 year options 14 Nov 2024 - 13 Nov 2029

Ref 7a. (Subcontractor): GCA’s relationship is only with the Prime contractor. Prime Contract Facility Security Officer (FSO) is responsible in the preparation of all subcontractor DD Form 254s. Coordination for subcontract DD 254s will be with the GCA and Prime contractor. If applicable, subcontract DD 254s with Sensitive Compartmented Information (SCI) requirements will be flowed through the SSC/S2S (SSO) office. If applicable, subcontract DD 254s with special access program information requirements will be flowed through the Government Special Access Program Security Officer (GSSO) office. Management of the subcontractor (to include preparation and approval of a subcontractor’s DD Form 254) is the responsibility of the Prime contractor. The subcontractor shall never have access above what is authorized to the Prime. This includes higher Facility Clearance (FCL) levels or Safeguarding levels. Subcontractors are not authorized access to classified information, COMSEC or NATO information/task on this contract until written approved by GCA.

Ref 10a. COMSEC -Classified COMSEC material is not releasable to contractor employees who have not received a FINAL clearance at the appropriate security level. All personnel granted access to COMSEC are required to be familiar with applicable Air Force and specialized COMSEC publications, and Air Force Methods and Procedures Technical Orders (MPTOs), etc. When access is required at Government facilities, contractor personnel will adhere to COMSEC rules and regulations as mandated by Command policy and procedures. Written concurrence of the GCA is required prior to subcontracting. The Prime Contractor should also notify the National Security Agency (NSA) Central Office of Record (COR) before negotiating or awarding subcontracts.

(U) (For Visitor Groups) Contractor will require access to COMSEC information at the on-base locations listed in item 8a. On-base contractors will not require their own COMSEC account. Access will be controlled by 61st Air Base Group (ABG) or host installation. On-base contractors will protect COMSEC material IAW directives identified by the installation COMSEC Custodian to include Air Force Manual 17-1302-0, Communications Security (COMSEC) Operations. Access to COMSEC material by personnel is restricted to U.S. citizens holding final U.S. Government clearances.

Ref 10e1: National Intelligence Information: SCI. No public release of information authorized, public disclosure or confirmation of any subject related to the support contract is not authorized without first obtaining written approval from the SSC/S2S SSO Security Office. Written concurrence of SSC/S2S SSO's Security Office is required prior to subcontracting. The SSC/S2S SSO Security Office shall have security cognizance for SCI. All activities involving SCI (including discussions) will be conducted in Sensitive Compartmented Information Facilities (SCIFs). Physical security standards for SCIFs are contained in ICD 705, applicable IC specifications, or standards and implementing DoD Component policies. See current SCI Addendum.

The contractor shall nominate a Contractor Special Security Officer (CSSO) and Alternate(s) to SSC/S2S through the government program office Special Security Representative (SSR) or Contracting Officers Representative (COR). CSSO and alternates must be SCI eligible and briefed into SCI.

Ref 10e2. Non-SCI: The contractor shall handle non-SCI or "collateral" intelligence information IAW 32 Code of Federal Regulation (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM), DoDM 5200.01-V1-V3, Information Security Program and AFI 16-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 of SSC/S2S offices.

Ref 10f: Special Access Program Information (SAP): See SAP Addendum for guidance.

Ref 10g – NATO Information. Access to North Atlantic Treaty Organization (NATO) classified information may be required by selected employees for performance on this contract. Access to classified NATO information requires a final U.S. Government clearance at the appropriate level. Contractor will protect NATO information in accordance with (IAW) 32 Code of Federal Regulation (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM). GCA written approval is required prior to issuing a subcontract for access to NATO information IAW 32 Code of Federal Regulation (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM).

Ref 10j. Controlled Unclassified Information (CUI), Controlled Unclassified Information (CUI) is the term which collectively refers to For Official Use Only (FOUO), Unclassified Controlled Technical Information (UCTI), Unclassified Controlled Nuclear Information (UCNI) and many other designations. CUI information generated and/or provided under this contract shall be managed and safeguarded IAW DoDI 5200.48, Controlled Unclassified Information, which supersedes DoDM 5200.01, Volume 4, DoD Information Security Program: DoDI 5200.48 DAFI 16-1403 Controlled Unclassified Information Implementation Guidance applies to arrangements, agreements, contract, and other transaction authority actions requiring access to Controlled Unclassified Information according to terms and conditions of such documents, as defined in Clause 2.101 of the Federal Acquisition Regulation and Section 2002.4 of Title 32, CFR, including but not limited to, grants, licenses, certificates, memoranda of agreement’/arrangement or understanding, and information-sharing agreements or arrangements.

AFGM2021-16-01 supersedes sections of Air Force Instruction (AFI) 16-1404, Air Force Information Security Program, where the designation For Official Use Only (FOUO) is referenced. See Block 11l for Information Systems protection guidance.

All CUI must be controlled until authorized for public release in accordance with DoDIs 5230.09, Clearance of DoD Information for Public Release, 5230.29, Security and Policy Review of DoD Information for Public Release, DoDM 5400.07, DoD Freedom of Information Act (FOIA) Program, and DoDM 5205.07-V1, DoD SAP Security Manual: General Procedures.

Support to Controlled Unclassified Information (CUI) portions of work on a lawful government contract may be accomplished by individuals without a security clearance needing to access CUI. No individual may have access to CUI unless it is determined that the individual has an authorized, lawful government purpose. The individual with authorized possession, knowledge, or control of CUI will determine whether an individual has an authorized, lawful government purpose to access designated CUI. CUI does not include information lawfully and publically available without restrictions. CUI requires safeguarding measures identified by the necessary law, regulation, or government wide policy with which it is associated.

Reference security requirements of NIST SP 800-171, they must use the NIST SP 800-171A procedures to evaluate the effectiveness of the tested controls. NIST SP 800-171A is the primary and authoritative guidance on assessing compliance with NIST SP 800-171.

Ref 10k & 11m. In order to perform assigned duties the contractor will need access to various government systems as identified by the GCA. The contractor shall follow overarching, and local requirements for access to these systems. Contractors shall be held accountable for actions they initiate on the network and shall conduct business IAW USSF, USAF, SSC, and host installation instructions and policies. The contractor shall not access, download or further disseminate any information/data (i.e. intelligence, NATO, COMSEC, etc.) outside the execution of the defined contract requirements and without the guidance and written permission of the GCA. In the event that any additional access is required, the GCA must modify the contract requirements, and revise the DD Form 254. Note: Once the GCA has modified the requirements for the generation of a revised DD Form 254, the Contractor must complete the Access Request Form(s), along with the modified DD Form 254, and forward to the GCA prior to receiving access. A NATO awareness brief will also be required for all Contractors prior to access to the NATO accredited terminals. Written concurrence of the GCA is required prior to subcontracting.

Secret Internet Protocol Router Network (SIPRNET) Access - Access to SIPRNET by contractor at government locations will be IAW applicable guidance and policies. Access to SIPRNET will be IAW DODI 8500.01, and Cybersecurity and Risk Management Framework (RFM) for DOD Information Technology.

Joint Wide Intelligence Communications Systems (JWICS) Access - Access by contractors at government locations will be IAW DoDM 5105.21 V1-3, SCI Administrative Security Manual(s), ICD 503-Information Systems, Cybersecurity and Risk Management Framework (RFM) for DOD Information Technology, and other applicable guidance. Reference SCI guidance and SCI Addendum. Written concurrence of the GCA is required prior to subcontracting.

The terms Cybersecurity, Information Systems, and Information Technology are defined in Committee on National Security Systems Instruction 4009, and Cybersecurity DODI 8500.01.

Unauthorized Disclosure: Government and contractor personnel must act to protect Technical Program design, development, or manufacturing data under their control from unauthorized disclosure to any foreign person or a U.S. person residing in a foreign country. Government and contractor organizations must inform the U.S. State Department under the provision of the ITAR regarding any unauthorized disclosure.

Ref 11a. Have access to classified information only at another contractor's facility or a Government activity. Classified material will be handled in accordance with DoD M 5200.01-V1-V3, and the 32 Code of Federal Regulation (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM).

11e. Perform Services Only - The contractor will be required to perform services consisting of acquisition, financial and administrative services in support of the SSC/AATS mission, which is to be the Guardian of Assured Access: Launching when & where the Nation needs. This contract provides expert services needed by SSC/AATS to enable the Government to adequately fulfill its acquisition role, efficiently in a research and development space-centric environment. This contract will provide support in the areas of strategic cells, digital transformation, CAG support, DAG support, administrative support and process improvement.

Ref 11g. Authorized to Use the Services of Defense Technical Information Center (DTIC) Access to DTIC can be requested through the DD Form 1540, Registration for Scientific and Technical Information Services or online at: http://www.dtic.mil/dtic/registration/registration.html The contractor may access information provided by DTIC by complying with all established safeguards and following the registration procedures as set forth in the 32 Code of Federal Regulation (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM).

Ref 11j. Have OPSEC Requirements - The contractor shall accomplish the following minimum requirements in support of the SSC/AATS Operations Security (OPSEC) Program.

a. The contractor shall protect activities that warrant OPSEC to include but are not limited to research, development, analysis, test and evaluation; acquisitions; treaty verification; nonproliferation protocols; international agreements; force protection operations; special access programs; and activities that prepare, sustain, or employ Military Services over the range of military operations.

b. The contractor shall 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. Sensitive unclassified information is that information marked For Official Use Only (FOUO), Controlled Unclassified Information (CUI), Privacy Act (PA) Of 1974, Company Proprietary, and as identified by the government program office and program manager, and SSC/AATS OPSEC Program Manager. OPSEC is essential to defense activities that may be compromised whenever open sources and detectable activities provide information that when compiled or analyzed is a detriment to U.S. interests.

c. Compliance with security requirements imposed by documents generated in response to DoDI 5200.39, Critical Program Information (f) Identification and Protection within Research, Development, Test and Evaluation (RDT&E).

d. The contractor shall comply with the NSSL OPSEC Plan, and apply protective measures therein. Research and Development contractors (off-base) shall develop an OPSEC Plan in accordance with NSSL OPSEC Plan, AFI 10-701, and DoDM 5205.2 as identified by the government program office, Program Manager, and the SSC/AA OPSEC Program Manager. OPSEC shall be a part of ongoing security awareness program conducted in accordance with the National Industrial Security Program Operating Manual.

e. The contractor shall participate in the host installation scheduled annual OPSEC program reviews.

f. The contractor shall protect all 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. Contractor shall protect Controlled Unclassified Information (CUI), IAW 32 CFR Part 2002 and information identified in the SSC and SSC program office Critical Information List (CIL), IAW AFI 10-701, OPSEC and DoD Operations Security (OPSEC) Program, DoDM 5205.02.

Email transmission of Sensitive Information, Critical Information, and Legacy Information (FOUO), and CUI obtained or produced pursuant to this contract will be encrypted or password protected. If the CUI is in the attachment(s), it must be identified and encrypted. CUI marking must be included at the top and bottom of each email. Email must also have the CUI Designation Indicator after the sender’s signature block.

g. Destruction of Sensitive Information, Critical Information, Legacy Information (FOUO), and CUI obtained or produced pursuant to this contract shall be in a manner that makes it unreadable, indecipherable, and irrecoverable. Contractor must use any destruction method specifically required by law, regulation, or Government-wide policy for that CUI. If the authority does not specify a destruction method, Contractor must use one of the following methods: Guidance for destruction in NIST SP 800–53: Security and Privacy Controls for Federal Information Systems and Organizations, and NIST SP 800–88, Revision 1: Guidelines for Media Sanitization (incorporated by reference, 32 CFR 2002.2); or any method of destruction approved for Classified National Security Information, as delineated in 32 CFR 2001.47, unless the CUI category's authority mandates other destruction methods (CUI Specified categories). Also, ISOO CUI Notice 2019-03 – “Destroying Controlled Unclassified Information (CUI) in Paper Form, this notice clarifies certain aspects of the requirements for destroying paper CUI. NIST SP 800-88, Revision 1, describes authorized methods for destroying other media types that contain CUI.

Ref 11l. Receive, Store, or Generate Controlled Unclassified Information (CUI) -

Contractor shall apply security controls contained in NIST SP 800-171 for the protection of CUI on non-DoD information systems. CUI information will not be placed on publicly accessible web sites.

Definitions:

Adequate Security - Security commensurate with the risk and the magnitude of harm resulting from the loss, misuse, or unauthorized access to or modification of information (see 0MB Circular A-130). Current means of achieving adequate security for Information Technology is to use DoD, CNSS and NIST guidance (see CNSSI No. 4009).

Non-Sensitive Information - Information available in the public domain or DoD information that has been approved for public release.

Sensitive Information - Information, the loss, misuse, or unauthorized access to or modification of, could adversely affect the national interest or the conduct of Federal programs, or the privacy to which individuals are entitled under Section 552a of title 5, United States Code, "The Privacy Act" but which has not been specifically authorized under criteria established by Executive order or an Act of Congress to be kept secret in the interest of national defense or foreign policy.

Ref 13: Security Guidance

Program Protection Plans (PPP) and Security Classification Guides (SCG): The contractors shall protect critical program information (CPI) and critical components (CC), technologies and systems in compliance with the applicable LSP Annex to the NSSL Program Protection Plan (PPP) and the contractor developed Program Protection Implementation Plan (PPIP). Program Security Classification Guides (SCGs) will be provided by the Government program office. Classified national security information, and unclassified controlled information (CUI) shall be protected as outlined in the SCG, 32 Code of Federal Regulation (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM), DODM 5200.01 V1-3 and DoDI 5200.48.

Research and developmental contractors shall develop a Program Protection Implementation Plan (PPIP) to be approved by the program office. The PPIP shall describe the protection measures being implemented by the contractor and sub-contractors for CPI and CC. The prime contractor shall flow-down to any subcontractor protection requirements for implementation as described in the PPIP in compliance with PPP. The government program office shall conduct Program Protection Surveys at contractor locations to assess the effectiveness of the established PPIP.

Personnel Security - For access to classified information contractor will ensure all required actions IAW DoDM 5200.02, AFM 16-1405, AFGM2022-03, and 32 CFR Part 117, are completed for personnel working on this contract. An interim SECRET or CONFIDENTIAL Personnel Security Clearance (PCL) is valid for access to classified information at the level of the eligibility granted. Interim SECRET or CONFIDENTIAL PCLs are authorized except when the contractor will require access COMSEC information, RD, or NATO information, where a finalized security clearance is required. Note, an interim TOP SECRET PCL is the equivalent of a final SECRET PCL. Security clearances are in accordance with the 32 Code of Federal Regulation (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM). Access to SCI will be in accordance with the current SCI addendum and DOD Manual 5105.21 Volumes 1-3 for SCI management. Contractor(s) will not be afforded access to classified information at any level (i.e. Confidential, Secret, or Top Secret) until the Defense Counterintelligence and Security Agency (DCSA) Consolidated Adjudication Services (CAS) grants a final PCL at the appropriate level. Interim PCLs are authorized only when granted by the adjudicative authority and have been entered into Defense Information System for Security (DISS). Contractor(s) must be employed in a position that requires a clearance in order to be submitted for the appropriate PCL. Contractor(s) Facility Security Officer (FSO) will submit all investigation requests through National Background Investigation Services (NBIS) and ensure individuals complete a clearance application in the Electronic Application (e-App). Contractor(s) FSO reviews, approves, and forwards the completed e-App to DCSA Vetting Risk Operations (VRO) for approval, issuance of an interim clearance, and release to Office of Personnel Management (OPM) for investigation. Alternate methods of clearance submission are acceptable as long as the contractor security personnel ensures clearance levels are available in Defense Information System for Security (DISS) for review.

Contract performance on a Government installation and/or 1) access to classified information and/or 2) IT Level I/II/III access and/or 3) when cleared personnel are required to perform unclassified services in a facility requiring a security clearance for unescorted access, shall undergo a Personnel Security Investigation (PSI), as appropriate. This is also applicable to contractor and subcontractor personnel who are visiting or on a temporary and/or escort duties for a period of 90 days or more. This requirement is for personnel who have or may need access to restricted or controlled areas. Contractor employees who require access to government IT systems/networks are determined to be trustworthy by the completion of a favorable PCL investigation appropriate with assigned duties and by a designated government official prior to IT access being granted. This is accomplished through the system authorization access request, DD Form 2875, process. Reference AFI 31-501, Personnel Security Program Management (or applicable revisions) for background investigation requirements.

Reference AFI 16-1406, Air Force Industrial Security Program and AFI 31-101, Integrated Defense, for administrative approaches to identify installation access for contractors as “Visitor Groups,” “Intermittent,” and “Cleared Facilities.” Both installation and network access as prescribed in AFI 16-1406 correlates to AFI 36-3026, Volume 2, Common Access Card (CAC), for contractor and volunteer populations, eligibility and enrollment to DEERS via the online TASS application.

Grant contractors (prime contractors and subcontractors) access to the installation IAW AFMAN 31-113, Installation Perimeter Access Control.

Any conflict and/or issue regarding classification level between this and any other application guide will be protected at the highest level until the conflict or issue is resolved by the Corps Security Manager, and Information Protection Office (IPO) and Special Security Office (SSO). Written resolution and/or direction will be provided by the Corps Security Manager, and IPO and SSO.

Security Incident Reporting: In addition to the reporting requirements directed by the NISPOM, the contractor shall provide a concurrent report of loss or compromise and/or unauthorized access of CUI, FOUO, and any classified information, materials, hardware, and/or systems to the cognizant Government Contracting Activity (GCA), Government Information System Security Manager (ISSM), Corps Security Manager (CSM), and SSC Information Protection Office (SSC/S2S), and supporting CSO (DCSA, etc.). Contractor shall report loss or compromise and/or unauthorized access of CUI, FOUO, and any classified information, materials, hardware, and/or systems to the contractor's cognizant security office identified in Block(s) 6c and 8c, within 24-hrs. The Contractor shall notify the PSO (OSI PJ) within 24 hours of any incident involving the actual or suspected compromise/loss of SAP classified information.

Upon expiration of this contract, the contractor shall request disposition instruction for all classified and unclassified project material. The contractor may be directed to properly destroy or return material. If the contractor desires to retain classified or unclassified program information, the contractor must provide a request six (6) months in advance of contract completion to transfer project information to follow-on contractor or similar effort, contractor must have written approval from the Government: Program Manager, Contracting Officer and Security Officer. The contractor shall return to the GCA all CACs, security badges, entry passes/vehicle decals issued to contractor personnel. This applies to termination, cancellation and/or expiration contract, and/or of employment and/or suspension of clearance.

Transfer of document to other Independent Research and Development (IRAD) is not permitted.

The undersigned has reviewed the Security Specification, understands the provisions and will ensure that it is complied with within the limits of his/her responsibility, and that any violations are brought to the attention of the GCA.

text:

SSC/AA

text:

SSC/BZS-AATS

Program Manager/COR rep: Nicolas Alvarez Security Representative rep: Reginald G. King Chief, Information Protection Office rep: Sharon M. Jones SSC SSO Office rep: Abraham Calderon Government Special Access Program Security Office rep: Malcolm L. Jones PSO, OSI/PJ Det 7 OL-A

EL SEGUNDO, CA 90245

Address: SSC/AATS

483 N. AVIATION BLVD.

EL SEGUNDO, CA 90245