Att3 DD254 FY25 JINTACCS.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.

ATTACHMENT A

CONTROLLED UNCLASSIFIED INFORMATION (CUI) INFORMATION

1. The Controlled Unclassified Information (CUI) marking is applied to the information in a document upon creation. The CUI marking is not a substitute for a security classification marking, but is used on official government information that may be withheld from the public under exemptions 2 through 9 of the Freedom of Information Act (FOIA).

2. The use of CUI markings means that the information must be reviewed by MCTSSA prior to release to the public to determine whether a significant and legitimate government purpose is served by withholding the information or portions of the information.

3. An unclassified document containing CUI information will be marked “CONTROLLED UNCLASSIFIED INFORMATION” on the bottom face and interior pages.

4. Any CUI information released to you by MCTSSA is required to be marked with the following statement prior to transfer:

THIS DOCUMENT CONTAINS INFORMATION EXEMPT FROM MANDATORY

DISCLOSURE UNDER THE FOIA. EXCEPTION(S) _APPLY.

5. CUI markings may only be removed by the originator or other authority. DO NOT REMOVE ANY CUI MARKING WITHOUT WRITTEN AUTHORIZATION FROM MCTSSA OR THE AUTHOR. You will be notified when the CUI status is terminated.

6. CUI information may be disseminated to employees and subcontractors who have a need for the information, in respect to this contract.

7. During working hours, CUI information shall be placed out-of-sight if the work area is accessible to persons who do not have a need for the information. During off hours, the information shall be stored to prevent unauthorized access. Filing CUI material in unlocked files or desks with other unclassified records is adequate when internal building security is provided during off hours. When internal security is not available, locked buildings or rooms provide adequate off hours protection.

Additionally, the material may be stored in locked receptacles, such as file cabinets, desks, or bookcases.

8. CUI information may be sent via first-class mail or parcel post.

Bulky shipments may be sent via fourth-class mail.

9. CUI information created at Government site will be disposed of when no longer needed ONLY by using a government provided cross cut shredder or shred disposable bin provided in each Government facility.

10. The releasing agency should be informed of any unauthorized disclosure of CUI information. The unauthorized disclosure of CUI is not a security violation, but the release of information protected by the Privacy Act may result in criminal sanctions.

ATTACHMENT B

OPERATIONS SECURITY REQUIREMENTS

All work will be performed in accordance with DoD and Navy Operations Security (OPSEC) requirements, per the following applicable documents:

National Security Decision Directive 298, National Operations Security Program, 28 July 1992.

DoDD 5205.02E, DoD Operations Security (OPSEC) Program, 20 June 2012.

OPNAVINST 3432.1A, Operations Security, 4 August 2011.

SECNAVINST 5239.2

MCTSSA Operations Security Policy

The Contractor will accomplish the following minimum requirements in support of Marine Corps Tactical Systems Support Activity (MCTSSA) OPSEC Program:

The Contractor will practice OPSEC and implement OPSEC countermeasures to protect DoD Critical Information. Critical Information includes facts (individually or in aggregate) that reveal sensitive details about MCTSSA, contractor security, or operations related to the support or performance of this Performance Work Statement (PWS), and require a level of protection from adversarial collection or exploitation not normally afforded to unclassified information.

The Contractor must protect Critical Information and other sensitive unclassified information and activities, especially those which could compromise classified information, operations, or degrade the planning and execution of military operations performed or supported by the contractor. Protection of Critical Information includes adherence to and execution of countermeasures provided by MCTSSA for Critical Information related to the PWS.

Sensitive unclassified information is that information marked CONTROLLED UNCLASSIFIED INFORMATION (or CUI), Privacy Act of 1974, COMPANY PROPRIETARY, and also information as identified by MCTSSA or the MCTSSA Contracting Officer Representative (COR).

MCTSSA has identified the following Critical Information items that may be related to this PWS:

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

Details of capabilities or limitations of any U.S. system and direct support systems.

Details about military operations (e.g., numbers of systems deployed, deployment timelines, locations, effectiveness, unique capabilities).

Operational characteristics for new or modified weapon systems (e.g., Probability of Kill (Pk), countermeasures, survivability).

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

Telemeter or data-linked data or information from which operational characteristics may be inferred or derived.

Test or evaluation information pertaining to schedules of events during which Critical Information might be captured.

Details of MCTSSA’s unique Test and Evaluation (T&E) capabilities (disclosure of unique capabilities).

Existence or details of intrusions into or attacks against the DoD networks or information systems, including tactics, techniques and procedures used, network vulnerabilities exploited, and data targeted for exploitation.

Network user identification (ID) and passwords.

Counter- Improvised Explosive Device (IED) capabilities and characteristics, including success or failure rates, damage assessments, and advancements to existing or new capabilities.

Vulnerabilities in Command processes, the disclosure of which could allow someone to circumvent security, financial, personnel safety, or operational procedures.

Force Protection specific capabilities or response protocols (e.g., timelines, equipment, numbers of personnel, training received).

Command leadership and VIP agendas, reservations, plans and routes.

Detailed facility maps or installation overhead photography (photos with annotations of Command areas or greater resolution than commercially available).

Details of MCTSSA emergency evacuation procedures, or emergency recall procedures.

Government personnel information that reveals force structure and readiness (e.g., recall rosters, deployments lists).

Compilations of information that directly disclose Command Critical Information.

The above Critical Information and any developed by the contractor, regardless if electronic or hardcopy must be protected by the following countermeasures at minimum:

All emails containing Critical Information must be DoD Public Key Infrastructure (PKI) signed and PKI encrypted when sent.

Critical Information may not be sent via unclassified fax.

Critical Information may not be discussed via non-secure phones.

Critical Information may not be provided to individuals that do not have a need to know to complete their assigned duties.

Critical Information may not be disposed of in recycle bins or trash containers.

Critical Information may not be left unattended in uncontrolled areas.

Critical Information should be treated with the same care as CUI or proprietary information.

Critical Information must be destroyed in the same manner as CUI.

Critical Information must be destroyed at upon termination of the contract or returned to the government at the government’s discretion.

The contractor shall document Critical Information items applicable to operations involving information on or related to the PWS.

Determinations of Critical Information will be completed using the DoD OPSEC 5-step process described in the National Security Decision Directive (NSDD) 298, National Operations Security Program.

OPSEC training must be included as part of the contractor’s ongoing security awareness program conducted in accordance with Chapter 3, Section 1, of the NISPOM. NSDD 298, DoD 5205.02E, DoD Operations Security (OPSEC) Program, and OPNAVINST 3432.1A, Operations Security should be used to assist in the creation or management of training curriculum.

If the contractor cannot resolve an OPSEC issue, they will contact the MCTSSA COR, who will consult with the MCTSSA OPSEC Manager.

All above requirements must be passed on to all subcontractors.

ATTACHMENT C

SPECIFIC ON-SITE SECURITY REQUIREMENTS

1. GENERAL

a. Contractor Performance

In performance of this contract, the following security services and procedures are incorporated as an attachment to the DD-254. The Contractor will conform to the requirements of DoD 5220.22-M, Department of Defense (DoD) National Industrial Security Program, Operating Manual (NISPOM). When visiting MCTSSA, the contractor will comply with the security directives used regarding the protection of classified and sensitive unclassified information, SECNAVINST 5510.36 (series) and SECNAVINST 5510.30 (series).

b. Security Supervision

MCTSSA will exercise security supervision over all contractors onboard MCTSSA and provide security support to the contractor, as noted below. The contractor will identify, to the MCTSSA COR or Technical Support Officer (TSO), an on-site point of contact (POC) to interface with the MCTSSA COR or TSO.

2. HANDLING CLASSIFIED MATERIAL OR INFORMATION

a. Control and Safeguarding

Contractor personnel at MCTSSA are responsible for controlling and safeguarding classified material in their possession.

Contractor personnel will be briefed by the Facility Security Officer (FSO) on the responsibility to safeguard classified material. In addition, all contractor personnel are invited to attend MCTSSA security briefings. In the event of a possible or actual loss or compromise of classified material, the on-site contractor at MCTSSA will immediately report the incident to the MCTSSA Security Manager and the Contractor’s FSO. A MCTSSA representative will investigate the circumstances, determine culpability when possible, and report results to the FSO and the Cognizant Field Office of the Defense Security Service (DSS). On-site contractor personnel will promptly correct any deficient security conditions identified by the MCTSSA representative.

b. Storage

Classified material may be stored in containers authorized by the MCTSSA Security Manager. The MCTSSA Commanding Officer must pre-approve in writing, the use of open areas for storage or for the processing of classified material. The MCTSSA Security Manager will provide specific supplemental security controls for open storage areas, when required.

c. Transmission of Classified Material

i. All classified material transmitted by mail for use by long term visitors will be addressed to COMMANDING OFFICER, MCTSSA, ATTN: CMCC, Box 555171, CAMP PENDLETON, CA 92055- 5171. The inner envelope will be addressed to the attention of the COR/TSO for this contract.

ii. All SECRET/CONFIDENTIAL material hand carried to MCTSSA by contractor personnel must be delivered to the MCTSSA Classified Material Control Center (CMCC).

iii. All MCTSSA classified material transmitted by contractor personnel from MCTSSA will be sent via the MCTSSA CMCC.

d. Information Systems (IS) Security

Contractors using IS networks, or computer resources to process classified, sensitive unclassified and/or unclassified information will comply with the provisions of the NISPOM and SECNAVINST 5239.2 and local policies and procedures.

Contractor personnel must contact the Information System Security Officer (ISSO) to ensure the systems used at MCTSSA have been granted a formal letter of approval to operate.

3. VISITOR CONTROL PROCEDURES

a. Contractor personnel assigned to MCTSSA will be considered long term visitors for the purpose of this contract.

b. Per DoD Memorandum dated April 1, 2005 Subject: Facilitating Classified Visits within the Department of Defense and the National Industrial Security Program Operating Manual (NISPOM), as amended by Industrial Security Letter (ISL) 02-X, mandates industry use of Joint Personnel Adjudication System (JPAS). JPAS Industry Sub Committee Doc 004 Rev 000; all contractors under DoD security cognizance will use JPAS for all personnel security actions. You must request a JPAS account within 90 days after the contract has been awarded.

Prior to the setup of a JPAS account, visit requests to activities shall have Need to Know certified by the MCTSSA TSO. All requests shall contain the information required by NISPOM and shall not exceed a 12 month period. Visit Notifications may be sent via JPAS to the MCTSSA Security Management Office (SMO) number 304256.

c. Visit requests for long term visitors must be received prior to the expected arrival of the visitor to ensure necessary processing of the request.

d. MCTSSA security personnel will issue temporary identification badges to contractor personnel following receipt of a valid JPAS Visit Notification from the contractor’s Security Office.

The COR/TSO may request that picture badges be issued for the length of the basic contract or option period. Identification badges are the property of the U.S. Government and will be worn and used for official business only. Unauthorized use of a MCTSSA badge will be reported to DSS. Identification badges will be worn above the waist in plain sight at all times on board MCTSSA.

e. Prior to departing MCTSSA (after official business has concluded) contractor personnel will check-out with MCTSSA security personnel. The check-out process will ensure security related items issued to contractor personnel are retrieved.

f. Foreign Nationals may only visit MCTSSA by complying with authorized methods set forth within:

i. SECNAVINST 5510.34

ii. Foreign Clearance Guide @ https://www.fcg.pentagon.mil

g. Prior to the termination of a Contractor employee with a MCTSSA badge or active Visit Notification on file, the FSO must:

i. Notify, in writing to the MCTSSA Security Manager and COR/TSO, the Contractor employee is being terminated. In emergency situations, a facsimile may be sent or a telephone notification may be used. The telephone notification, however, must be followed up in writing within five working days.

ii. Confiscate any MCTSSA identification/access badges and return them to the MCTSSA Security Officer, no later than five working days after the effective date of the termination.

4. PHOTOGRAPHY/RECORDING CONTROL

No photography, video, or audio recordings are authorized aboard or around the MCTSSA compound without the written permission of the Commanding Officer or his representative. If there is an official requirement for any photography, video, or audio recordings, the MCTSSA COR/TSO will submit the MCTSSA PHOTOGRAPHY

/ RECORDING REQUEST form to the MCTSSA Security Manager via the CMCC, building 31337.

5. INSPECTIONS

MCTSSA security personnel will conduct periodic inspections of the security practices of the on-site contractor. All contractor personnel will cooperate with MCTSSA security representatives during these inspections. The contractor will be responsive to the MCTSSA security representative’s findings.

6. REPORTS

As documented by the NISPOM, Chapter 1, Section 3, contractors are required to report events that have an impact on the status of the facility clearance (FCL), the status of an employee’s personnel clearance (PCL), the proper safeguarding of classified information, or an indication that classified information has been lost or compromised. The contractor will ensure that information pertaining to assigned contractor personnel or operations is reported to the MCTSSA Security Manager and

COR/TSO.

This reporting will include the following:

a. The denial, suspension, or revocation of security clearance of any assigned personnel

b. Any adverse information, which would cast doubt on an assigned employee’s suitability for continued access to classified materials

c. Any instance of loss or compromise, or suspected loss or compromise, of classified information

d. Actual, probable or possible espionage, sabotage, or subversive information

e. Any other circumstances relating to security that would affect contractor operations on board MCTSSA.

7. PHYSICAL SECURITY

a. The Contractor will comply with all emergency rules and procedures established for MCTSSA.

b. All personnel onboard MCTSSA and Marine Corps Base Camp Pendleton are subject to random inspections of their vehicles, personal items and of themselves. Consent to these inspections is considered to have been given when personnel enter Camp Pendleton.

8. ITEMS PROHIBITED ON BOARD MCTSSA

a. Dangerous weapons, instruments, or devices including, but not limited to, the following:

i. Rifles, automatic rifles, machine guns, sub-machine guns, pistols, machine pistols, flare pistols, starter pistols, shotguns, compressed gas, air or spring fired pellet or BB guns, sling shots, blow guns, or any other device which uses gun powder, compressed gas or air, or spring tension to forcefully eject a projective or other device which may injure someone.

ii. Daggers, switch blades, bow and arrows, spear guns, Hawaiian slings, power heads, fishing knives, scuba knives, or any unofficial knife with a blade longer than 2.5 inches.

iii. Martial arts devices (throwing stars, nunchakus), stun guns, tasers, brass knuckles, billy clubs, night sticks, pipes, bars, mallets, or other similar devices capable of being used as a weapon.

iv. Poison, acids or caustic chemicals; or any other item that may be used to inflict serious injury or death to another person or temporarily blind or disable or cause individual injury not specifically authorized by proper authority.

b. Explosive articles or compounds including, but is not limited to, ammunition for any of the small arms weapons mentioned as a dangerous weapons, including blank ammunition, gun powder, Molotov cocktails, pipe bombs, grenades, pyrotechnics, fireworks, or any other compound or article which might violently react and cause injury not specifically authorized by proper authority.

9. ESCORTING POLICY

All personnel within the MCTSSA fenced perimeter, with the exception of emergency personnel such as fire, ambulance, or hazardous materials responding to an actual emergency, must wear a MCTSSA issued badge. Personnel without the required security clearance require a MCTSSA escort at all times

10. COMMON ACCESS CARD (CAC) REQUIREMENT

The COR will identify and approve contractor employees for this contract that require Common Access Cards (CACs) to perform their job. In accordance with Headquarters, United States Marine Corps issued guidance relative to Homeland Security Presidential Directive – 12 (HSPD-12), all personnel must meet eligibility criteria to be issued a CAC. To meet the eligibility criteria, contractor employees requiring a CAC, must obtain and maintain a favorably adjudicated Personnel Security Investigation (PSI).

Prior to authorizing a CAC, the employee’s JPAS record must indicate a completed and favorably adjudicated PSI or (at a minimum) that a PSI has been submitted and accepted (opened).

The minimum acceptable investigation is a National Agency Check with Written Inquiries (NACI). If a contractor employee’s open investigation closes and is not favorably adjudicated, the CAC must be immediately retrieved and revoked.

FSOs are responsible for notifying the Marine Corps Systems Command (MCSC) Security Director if any contractor on this contract receives an unfavorable adjudication after being issued a CAC. The FSO must also notify the MCSC Security Director of any adverse/derogatory information associated with the 13 Adjudicative Guidelines/Factors concerning any contractor issued a CAC, regardless of whether a JPAS Incident Report is submitted.

Each CAC is issued with a “ctr.usmc.mil” e-mail account the individual contractor must keep active, by logging in on a regular basis (at least twice a month), sending an e-mail, and clearing any unnecessary e-mails. Contractors are prohibited from auto-forwarding “.mil” e-mail to a personal “.com” account.

If the “ctr.usmc.mil” e-mail account is not kept active, the G-6 will deactivate the account and CAC will lose functionality.

CACs will only be issued to contractors that have been authorized by the COR. If a contractor loses their eligibility for a CAC due to an adverse adjudicative decision, they also lose eligibility to work on MCSC contracts. CACs are not issued for convenience.

The CAC and MCTSSA access badge must be turned into the COR or MCTSSA Security representative prior to leaving the compound on the last business day of the contract, upon the expiration of the CAC, or in the event of a contractor employee resigning or being fired.

CLASSIFIED ACCESS LOCATIONS

DD-254 Contract Number: M68909-20-R-7600

ATTACHMENT D

CLASSIFIED ACCESS LOCATIONS

Classified access (to the level indicated in Block 1a of this DD‐254) may occur at the locations identified below. These facilities are under the exclusive responsibility of the designated Government Security Managers/Officers or the Contractor Facility Security Officers.

LOCATION CAGE

CODE

SMO

CODE

GENSER SIPRNet (where available)

Receive, Generate, & Store Classified

SCIF - NV-02-015

I Marine Expeditionary Force 11th and C Street Camp Pendleton, CA 92055

X X

MCTSSA

Camp Pendleton, CA 92055-5171

Additional Locations as Determined by the GCA, COR, or Project Officer in order to prevent work stoppage. These locations will be provided in subsequent DD‐254 along with the Task Orders for the Multi‐Award Task Order Contract.

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

San Diego, CA 92128 858-207-0170

Camp Pendleton, CA 92055-5171

10e (2). Contractor requires access to the SIPRNet (at government activity). Although Intelligence information is available on SIPRNet, and could be inadvertently accessed, there is no valid requirement for Intelligence information at this time, therefore prior approval by the Government Contracting Activity (GCA) for subcontracting is not required. The contractor shall not intentionally access/download Intelligence information from the SIPRNet. In the event, Intelligence information is required, MARCORSYSCOM’s GCA and the Industrial Security Office will modify this contract/DD-254. In addition, there is no valid requirement for NATO access, however inadvertent access may occur because NATO information is available on the SIPRNet. NATO Awareness Briefs will be reviewed, acknowledged, signed, and retained on file by the MARCORSYSCOM Security Office. Access to NATO information requires a final U.S. Government clearance and special briefings at the appropriate level.

10e (2). Contractor requires access to the SIPRNet (at government activity). Although Intelligence information is available on SIPRNet, and could be inadvertently accessed, there is no valid requirement for Intelligence information at this time, therefore prior approval by the Government Contracting Activity (GCA) for subcontracting is not required. The contractor shall not intentionally access/download Intelligence information from the SIPRNet. In the event, Intelligence information is required, MARCORSYSCOM’s GCA and the Industrial Security Office will modify this contract/DD-254. In addition, there is no valid requirement for NATO access, however inadvertent access may occur because NATO information is available on the SIPRNet. NATO Awareness Briefs will be reviewed, acknowledged, signed, and retained on file by the MARCORSYSCOM Security Office. Access to NATO information requires a final U.S. Government clearance and special briefings at the appropriate level.

10g. If access to NATO information is required, it will be handled, marked, and controlled per the requirements of the National Industrial Security Program Operating Manual (NISPOM), (DoD-5220.22M). Access to NATO information requires a final U.S. Government Secret clearance and NATO brief. MCTSSA will provide the NATO brief, and record briefing date in JPAS. The Contractor will sign the NATO brief acknowledgment form. Access to classified information/documents belonging to NATO, or containing NATO classified information is required. NATO information will be handled and controlled in compliance with the DoD 5220.22-M.

10j. The contractor shall comply with the requirements of the SECNAVINST 5510.36B and DoDM 5200.01, Volume 4 for guidance when access to Controlled Unclassified Information (CUI) is required in performance of this contract.

See attachment A - For Official Use Only (FOUO) Information.

10k. Secret Internet Protocol Router Network (SIPRNet) access is required.

11a. The TPOC will provide security classification guidance necessary for performance of this contract. The contractor requires access to classified source data up to and including the classification levels identified in item 1.a. of this DD-254 in support of this work effort. Contractors will be co-located in MCTSSA government spaces and will comply with and be held accountable for the requirements of SECNAVINST 5510.30C, SECNAVINST 5510.36B and any additional security requirements provided by the MCTSSA’s Government Contracting Activity (GCA), the Industrial Security Office, and the CMCC Custodian. The contractor shall comply with the requirements of the Information Systems Security Programs as described in OPNAVINST 5239.2 and local command information systems security instructions. All classified systems, regardless of the level of data processed, will be accredited in accordance with the above instructions. The contractor will ensure all articles (including graphics) intended for public release or posting on Internet/World Wide Web sites will be processed through the Public Affairs Office as listed in Item 12.

11j. See [14.] Additional Security Requirements for OPSEC Requirements while performing aboard NAVY/USMC sites.

11l. Receive, Store, or Generate Controlled Unclassified Information (CUI). In addition to classified information, certain types of unclassified information also require distribution controls and protective measures for a variety of reasons. Refer to DoDM 5200.01 Vol 4 for guidance with identification and protection of CUI.

Camp Pendleton uses Defense Biometric Identification System (DBIDS) for base access. The vendor will need to call 760-763-7604 for information or go to the Las Pulgas gate to enroll. Failure to participate in the program will restrict access to the base and may not be used as a reason for late or non-performance of services. All vendors and their employees are required by MCB Camp Pendleton regulations to meet the requirement for installation access, pass a background check, and have their identity verified to receive unescorted access. No foreign nationals shall be permitted on MCB Camp Pendleton under this contract.

See attachment C – Specific On-Site Security Requirements.

Contracting Officer's Representative

DoDM 5105.21

SECNAV M5510.30B

NAVSUP to DoD Dir 5105.21-M-1

SECNAV M5510.36A

Title 32 CFR 117.15 NISPOM Explain and identify specific areas and government activity responsible for inspections.: SCI Security Cognizant: SSO Navy Collateral Security Cognizant: DCSA

BOX 555171

CAMP PENDLETON, CA 92055-5171

Enter address (include zip code).: MCTSSA

BOX 555171

CAMP PENDLETON, CA 92055-5171