W9128A-18-B-0002_Am-0013.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

FY16 MCAF KNMD043004 F-22 Fighter Alert Facility, Joint Base Pearl Harbor Hickam (JBPHH), Oahu, Haw aii

See Continuation Page.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 2

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W9128A18B0002

X 9B. DATED (SEE ITEM 11)

01-Feb-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended,X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

Am-0013

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

07-Aug-2018

CODE

CECT - CONTRACTING DIVISION

USACE, HONOLULU DISTRICT

BLDG 252 (CECT-POH)

FT. SHAFTER HI 96858-5440

W9128A 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W9128A18B0002 Am-0013

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

1. CHANGES TO SPECIFICATIONS. Attached hereto are revised pages/paragraphs to the specifications. The revision mark “(Am-0013)” is shown on each revised page.

a. REVISED SECTIONS. The following are revised pages/paragraphs to the solicitation. Changes are marked in

“*” asterisks or indicated in bold.

Standard Form 1442 – Page 1 Section 00 21 13 – Pages 6, 7 Section 00 72 00 – Pages 21 through 25 Section 05 12 00 – Paragraph: 1.3 Section 31 63 33 – Paragraph: 3.3.4 Section 32 13 11 – Paragraph: 1.4.6.1 Section 33 05 23.13 – Paragraph: 2.1.2

b. NEW PAGES. The following are new pages to the solicitation.

Section 00 60 00, Appendix A – Requests for Information (#316 through 323)

2. CHANGES TO DRAWINGS.

a. REVISED DRAWINGS. The following revised drawings replace like-numbered drawings and are issued herewith.

Sheet ID Sheet Number Mark Revision Date GI002a

TS501

TS503

T-506

3a of 410

8/6/18 8/6/18 8/6/18 8/6/18

3. The bid opening date and time is EXTENDED (see SF1442, Page 1, Block 13A).

FY16 MCAF KNMD043004, F-22 Fighter Alert Facility, Joint Base Pearl Harbor-Hickam (JBPHH), Oahu, Hawaii

X

COLIN K WAKI 808-835-4393

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

10. THE GOVERNMENT REQUIRES PERFORMANCE OF THE WORK DESCRIBED IN THESE DOCUMENTS

NEGOTIATED

01-Feb-2018

(RFP)

(IFB)

CALL:

B. TELEPHONE NO. (Include area code) (NO COLLECT CALLS)

See Item 7

2. TYPE OF SOLICITATION

SEALED BID

3. DATE ISSUED

9. FOR INFORMATION A. NAME

SOLICITATION

NSN 7540-01-155-3212 1442-101 STANDARD FORM 1442 (REV. 4-85)

Prescribed by GSA

FAR (48 CFR) 53.236-1(e)

11. The Contractor shall begin performance within _______7 calendar days and complete it within ________721 calendar days after receiving award, X notice to proceed. This performance period is X mandatory, negotiable. (See _________________________52.211-10

12 A. THE CONTRACTOR MUST FURNISH ANY REQUIRED PERFORMANCE AND PAYMENT BONDS?

(If "YES," indicate within how many calendar days after award in Item 12B.)

X YES NO

13. ADDITIONAL SOLICITATION REQUIREMENTS:

A. Sealed offers in original and __________1 copies to perform the work required are due at the place specified in Item 8 by ___________ local time ______________ 16 Aug 2018 (date). If this is a sealed bid solicitation, offers must be publicly opened at that time.

shall be marked to show the offeror's name and address, the solicitation number, and the date and time offers are due.

B. An offer guarantee X is, is not required.

C. All offers are subject to the (1) work requirements, and (2) other provisions and clauses incorporated in the solicitation in full text or by reference.

D. Offers providing less than _______ 180 calendar days for Government acceptance after the date offers are due will not be considered and will be rejected.

SOLICITATION, OFFER,

AND AWARD

(Construction, Alteration, or Repair)

1. SOLICITATION NO.

IMPORTANT - The "offer" section on the reverse must be fully completed by offeror.

4. CONTRACT NO.

7. ISSUED BY CODE

CECT - CONTRACTING DIVISION

USACE, HONOLULU DISTRICT

BLDG 252 (CECT-POH)

FT. SHAFTER HI 96858-5440

W9128A

PAGE OF PAGES

1 OF

CODE

(Title, identifying no., date):

12B. CALENDAR DAYS

02:00 PM (hour)

Sealed envelopes containing offers

5. REQUISITION/PURCHASE REQUEST NO. 6. PROJECT NO.

8. ADDRESS OFFER TO (If Other Than Item 7)

FAX: TEL: TEL: FAX:

W9128A18B0002 90

(Am-0013)

W9128A-18-B-0002

Section 00 21 13 – Page 6

(2) The offeror should be prepared to provide the following information:

(i) Company legal business name.

(ii) Tradestyle, doing business, or other name by which your entity is commonly recognized.

(iii) Company physical street address, city, state and Zip Code.

(iv) Company mailing address, city, state and Zip Code (if separate from physical).

(v) Company telephone number.

(vi) Date the company was started.

(vii) Number of employees at your location.

(viii) Chief executive officer/key manager.

(ix) Line of business (industry).

(x) Company Headquarters name and address (reporting relationship within your entity).

(d) If the Offeror does not become registered in the SAM database in the time prescribed by the Contracting Officer, the Contracting Officer will proceed to award to the next otherwise successful registered Offeror.

(e) Processing time, which normally takes 48 hours, should be taken into consideration when registering. Offerors who are not registered should consider applying for registration immediately upon receipt of this solicitation.

(f) Offerors may obtain information on registration at https://www.acquisition.gov.

(End of Provision)

252.204-7008 COMPLIANCE WITH SAFEGUARDING COVERED DEFENSE INFORMATION CONTROLS

(OCT 2016)

(a) Definitions. As used in this provision--

Controlled technical information, covered contractor information system, covered defense information, cyber incident, information system, and technical information are defined in clause 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting.

(b) The security requirements required by contract clause 252.204-7012 shall be implemented for all covered defense information on all covered contractor information systems that support the performance of this contract.

(c) For covered contractor information systems that are not part of an information technology service or system operated on behalf of the Government (see 252.204-7012(b)(2))--

(1) By submission of this offer, the Offeror represents that it will implement the security requirements specified by National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, ``Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations'' (see http://dx.doi.org/10.6028/NIST.SP.800-171) that are in effect at the time the solicitation is issued or as authorized by the contracting officer not later than December 31, 2017.

Section 00 21 13 – Page 7

(2)(i) If the Offeror proposes to vary from any of the security requirements specified by NIST SP 800-171 that are in effect at the time the solicitation is issued or as authorized by the Contracting Officer, the Offeror shall submit to the Contracting Officer, for consideration by the DoD Chief Information Officer (CIO), a written explanation of—

(A) Why a particular security requirement is not applicable; or

(B) How an alternative but equally effective, security measure is used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection.

(ii) An authorized representative of the DoD CIO will adjudicate offeror requests to vary from NIST SP 800-171 requirements in writing prior to contract award. Any accepted variance from NIST SP 800-171 shall be incorporated into the resulting contract.

(End of provision)

252.222-7007 REPRESENTATION REGARDING COMBATING TRAFFICKING IN PERSONS (JAN 2015)

By submission of its offer, the Offeror represents that it--

(a) Will not engage in any trafficking in persons or related activities, including but not limited to the use of forced labor, in the performance of this contract;

(b) Has hiring and subcontracting policies to protect the rights of its employees and the rights of subcontractor employees and will comply with those policies in the performance of this contract; and

(c) Has notified its employees and subcontractors of--

(1) The responsibility to report trafficking in persons violations by the Contractor, Contractor employees, or subcontractor employees, at any tier; and

(2) Employee protection under 10 U.S.C. 2409, as implemented in DFARS subpart 203.9, from reprisal for whistleblowing on trafficking in persons violations.

(End of provision)

FY16 MCAF RNMD043004, F‐22 Fighter Alert Facility Joint Base Pearl Harbor Hickam (JBPHH), Oahu, Hawaii

RFI # References Question Government Response 316 Drawings TS-105 and

TS-501

The project drawings show the electrical conduits under the taxiway to be installed using Horizontal Directional Drilling (HDD) with the installation to be at least two feet below ground surface. Our experience with taxiways has found the subbase materials often extend deeper than that. Is there a maximum allowable depth for the conduits?

Please see revised Drawing TS501, Detail C1, Note 10, per Am- 0013.

317 Drawings TS-105 and

TS-501

The length of the bores under the taxiway will vary depending on the HDD method used. One method would best be implemented close to the taxiway where another works best at some distance from the taxiway. What is the minimum and maximum standoff distance from the taxiway?

Please see new Section 01 35 13.05 20, Paragraph 3.1.1, per Am-0008.

318 Drawing TS-501 On Detail C1, a (24) inch diameter drill casing is shown. Please confirm and verify that the intended specified casing material is steel, or HDPE pipe. Please verify and confirm a specified wall thickness and/or schedule of the casing outlined.

Please see revised Drawing TS-501, per Am-0007, and revised Section 33 05 23.13, Paragraph 2.1.2, per Am-0013

319 Under Spec Section 32 13 11, Concrete Pavement for Airfields Pavement, Paragraph 1.4.6 – Test Section; it says to construct a test section, but not as part of the production concrete area.

The test section is to be at least 400’ long. Under 1.4.6.1 is says to construct the test lane the same width as required for use in the project. There are numerous widths required.

Please clarify width required.

At 10’ wide, this is approximately 170 cy of concrete to waste.

Also, can you reconsider and have the test lane be part of the project concrete if it passes testing? If not, where will this test lane be allowed to be poured?

Please see revised Section 32 13 11, Paragraph 1.4.6.1, per Am-0013.

320 • Specification §316333-3.3.4 stipulates "Install hex nut at bearing plate to lock off central bar after load testing is complete."

1. Could you clarify/confirm that it is intended that a "lock off load" be applied to the central bar of the micro-piles.

2. If the micro-piles are to be "pre-loaded" could you provide the required loading? (Note that this is not a typical arrangement.)

1. Please see revised Section 31 63 33, Paragraph 3.3.4, per Am-0010.

2. Please see revised Section 31 63 33, Paragraph 3.3.4, per Am-0010. Preloading is not required.

Section 00 60 00, Appendix A (Am‐0013)

321 Plan Sheet G-001, T-

504, TY001, TY420,

TY440, TY501, TY601,

TY602

-Plan Sheet G-001, Option #3 states “IDS Equipment is a Complete Install & Ready for Use. Items in Option: Security Cameras, Detection, Monitors, Detection Equipment, Transmitter Units, Ancillary Wires, Connectors, Utilities, Disposal & Clean up.”

-Plan Sheet T-504, Am0005 adds note 3 “Security IDS, ACS, Cabling is GFGI” -Plan Sheet TY001, note 26 states “All Wiring & Security Devices Shall be Bid Option #3” -Plan Sheets TY420 & TY440, note 3 indicates that all CCTV, ACS, & IDS Cabinets are GFGI.

-Plan Sheet TY501, note 3 states “Security IDS, ACS, Cabling is

GFGI”

-Plan Sheet TY601 CCTV System Notes, note #1 States “Furnish & Install Empty Raceway & Outlet System (Devices, Backboxes, Conduit with Pull String) for Interior & Exterior CCTV System by Government” -Plan Sheet TY602 States “Provide Wiring in Accordance with the Equipment Supplier Shop Drawings. Provide Wiring for Tamper Alarm Contacts for all Junction Boxes” Sheet Note directly below states “System is Conduit/Junction Box Pull String Only. System Devices & Wiring are by Owner.”

-These notes are contradictory to the Option #3 description on Sheet G-001. Please clarify GFGI equipment and cabling.

Please see revised Drawings TY001, TY420, TY440, TY501, TY601, and TY602 per Am-0011; and revised Drawing T-506, per Am-0013. Drawing T-504 has been deleted per Am-0007.

322 Specification section 051200 indicates that the steel erectors are to be AISC certified, Category CSE. There is only one subcontractor that has this certification in Hawaii and they have expressed they are undecided on bidding on this project. In an effort to receive multiple competitive bids from qualified subcontractors, please reconsider the AISC certification requirement on this project.

Please see revised Section 05 12 00, Paragraph 1.3, per Am- 0013.

323 Drawings TS503 General Note 1

Drawings TS503 General Note 1 States that precast manholes are to be designed in Accordance with AASHTO H-20 LRFD Traffic Bridge Loading using 5,500 PSI Compressive strength concrete and a 60,000 PSI Yield Strength and references an Aircraft rating with the outside dimensions. Can the designer confirm that this can truly be achieved with an 8" wall thickness of the Telecommunications Manhole. Can the designer confirm that a heavy duty aircraft rating can be achieved for the Security Manhole detail shown on TY702 with a 6" wall thickness?

Please see revised Drawing TS-503, per Am-0013.

Section 00 72 00 – Page 21 date of contract award and the Under Secretary of Defense (Acquisition, Technology, and Logistics) memoranda on Fundamental Research, dated May 24, 2010, and on Contracted Fundamental Research, dated June 26, 2008 (available at DFARS PGI 204.4).

(b) Requests for approval under paragraph (a)(1) shall identify the specific information to be released, the medium to be used, and the purpose for the release. The Contractor shall submit its request to the Contracting Officer at least 10 business days before the proposed date for release.

(c) The Contractor agrees to include a similar requirement, including this paragraph (c), in each subcontract under this contract. Subcontractors shall submit requests for authorization to release through the prime contractor to the Contracting Officer.

(End of clause)

252.204-7003 CONTROL OF GOVERNMENT PERSONNEL WORK PRODUCT (APR 1992)

The Contractor's procedures for protecting against unauthorized disclosure of information shall not require Department of Defense employees or members of the Armed Forces to relinquish control of their work products, whether classified or not, to the contractor.

(End of clause)

252.204-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT

REPORTING (OCT 2016)

(a) Definitions. As used in this clause--

Adequate security means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.

Compromise means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.

Contractor attributional/proprietary information means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.

Controlled technical information means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination.

Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.

Covered contractor information system means an unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.

Covered defense information means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.archives.gov/cui/registry/category-list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is--

Section 00 72 00 – Page 22

(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or

(2) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract.

Cyber incident means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.

Forensic analysis means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data.

Information system means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.

Malicious software means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.

Media means physical devices or writing surfaces including, but is not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which covered defense information is recorded, stored, or printed within a covered contractor information system.

Operationally critical support means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.

Rapidly report means within 72 hours of discovery of any cyber incident.

Technical information means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data--Noncommercial Items, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.

(b) Adequate security. The Contractor shall provide adequate security on all covered contractor information systems.

To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections:

(1) For covered contractor information systems that are part of an information technology (IT) service or system operated on behalf of the Government, the following security requirements apply:

(i) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract.

(ii) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract.

(2) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1) of this clause, the following security requirements apply:

(i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to the security requirements in National Institute of Standards and Technology (NIST)

Section 00 72 00 – Page 23

Special Publication (SP) 800-171, ``Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations'' (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800-171) in effect at the time the solicitation is issued or as authorized by the Contracting Officer.

(ii)(A) The Contractor shall implement NIST SP 800-171, as soon aspractical, but not later than December 31, 2017.

For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award.

(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative, but equally effective, security measure that may be implemented in its place.

(C) If the DoD CIO has previously adjudicated the contractor's requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract.

(D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline (https://www.fedramp.gov/resources/documents/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.

(3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraphs (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan.

(c) Cyber incident reporting requirement.

(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor's ability to perform the requirements of the contract that are designated as operationally critical support and identified in the contract, the Contractor shall--

(i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor's network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor's ability to provide operationally critical support; and

(ii) Rapidly report cyber incidents to DoD at http://dibnet.dod.mil.

(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at http://dibnet.dod.mil.

(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see http://iase.disa.mil/pki/eca/Pages/index.aspx.

Section 00 72 00 – Page 24

(d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC3) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to the Contracting Officer.

(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.

(f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis.

(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.

(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.

(i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD--

(1) To entities with missions that may be affected by such information;

(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;

(3) To Government entities that conduct counterintelligence or law enforcement investigations;

(4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or

(5) To a support services contractor (``recipient'') that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information.

(j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purpose or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government's use and release of such information.

(k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data.

(l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor's responsibility for other safeguarding or cyber incident reporting

Section 00 72 00 – Page 25 pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements.

(m) Subcontracts. The Contractor shall--

(1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial items, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and, if necessary, consult with the Contracting Officer; and

(2) Require subcontractors to--

(i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and

(ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause.

(End of clause)

252.205-7000 PROVISION OF INFORMATION TO COOPERATIVE AGREEMENT HOLDERS (DEC 1991)

(a) Definition.

"Cooperative agreement holder" means a State or local government; a private, nonprofit organization; a tribal organization (as defined in section 4(c) of the Indian Self-Determination and Education Assistance Act (Pub. L. 93- 268; 25 U.S.C. 450 (c))); or an economic enterprise (as defined in section 3(e) of the Indian Financing Act of 1974 (Pub. L. 93-362; 25 U.S.C. 1452(e))) whether such economic enterprise is organized for profit or nonprofit purposes; which has an agreement with the Defense Logistics Agency to furnish procurement technical assistance to business entities.

(b) The Contractor shall provide cooperative agreement holders, upon their request, with a list of those appropriate employees or offices responsible for entering into subcontracts under defense contracts. The list shall include the business address, telephone number, and area of responsibility of each employee or office.

(c) The Contractor need not provide the listing to a particular cooperative agreement holder more frequently than once a year.

(End of clause)

252.209-7004 SUBCONTRACTING WITH FIRMS THAT ARE OWNED OR CONTROLLED BY THE

GOVERNMENT OF A COUNTRY THAT IS A STATE SPONSOR OF TERRORISM (OCT 2015)

(a) Unless the Government determines that there is a compelling reason to do so, the Contractor shall not enter into any subcontract in excess of $35,000 with a firm, or a subsidiary of a firm, that is identified in the Exclusions section of the System for Award Management System (SAM Exclusions) as being ineligible for the award of Defense contracts or subcontracts because it is owned or controlled by the government of a country that is a state sponsor of terrorism.