F35 SQ OPS AMU-SIM RTA Specifications Volume III of III.pdf

CONTRACT NO. N69450-19-D-0123

TASK ORDER NO. N6945020F0106 / N6945020F0102

EPROJECT NO. 1651220 / 1651221

SPECIFICATIONS

P415 F-35A SQUADRON OPERATIONS / AMU FACILITY AND

P396 F-35A FLIGHT SIMULATOR FACILITY

NAVY AIR STATION JOINT RESERVE BASE

FORT WORTH, TEXAS

RTA SUBMITTAL

VOLUME III OF III

DIVISION 25 THRU DIVISION 33

PREPARED BY:

January 22, 2021

P415 F-35A SQUADRON OPERATIONS/AMU FACILITY AND EPROJECT NO: 1651220

P396 F-35A FLIGHT SIMULATOR FACILITY EPROJECT NO: 1651221

PROJECT TABLE OF CONTENTS

DI VI SI ON 00 - PROCUREMENT AND CONTRACTI NG REQUI REMENTS

00 01 15 LIST OF DRAWINGS

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 11 00.00 25 SUMMARY OF WORK

01 14 00.00 25 WORK RESTRICTIONS

01 20 00.00 25 PRICE AND PAYMENT PROCEDURES

01 30 00.00 25 ADMINISTRATIVE REQUIREMENTS

01 30 01.00 20 PROCURMENT AND INSTALLATION OF FURNITURE, FIXTURES AND

EQUIPMENT

01 31 23.13 25 ELECTRONIC CONSTRUCTION AND FACILITY SUPPORT CONTRACT

MANAGEMENT SYSTEM

01 32 17.00 25 COST-LOADED NETWORK ANALYSIS SCHEDULES (NAS)

01 33 00 SUBMITTAL PROCEDURES

01 33 29.00 25 SUSTAINABILITY REPORTING

01 35 26.00 25 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 25 QUALITY CONTROL

01 45 35.00 25 SPECIAL INSPECTIONS

01 50 00.00 25 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19.00 25 TEMPORARY ENVIRONMENTAL CONTROLS

01 58 00.00 25 PROJECT IDENTIFICATION

01 74 19.00 25 CONSTRUCTION WASTE MANAGEMENT AND DISPOSAL

01 78 00.00 25 CLOSEOUT SUBMITTALS

01 78 23.00 25 OPERATION AND MAINTENANCE DATA

01 78 24.00 25 FACILITY ELECTRONIC OPERATION AND MAINTENANCE SUPPORT

INFORMATION (eOMSI)

01 91 00.15 25 TOTAL BUILDING COMMISSIONING

DI VI SI ON 02 - EXI STI NG CONDI TI ONS

02 41 00 DEMOLITION AND DECONSTRUCTION

02 82 00 ASBESTOS REMEDIATION

DI VI SI ON 03 - CONCRETE

03 11 31 VOID FORMS

03 30 00 CAST-IN-PLACE CONCRETE

DI VI SI ON 04 - MASONRY

04 20 00 UNIT MASONRY

DI VI SI ON 05 - METALS

05 05 23.16 STRUCTURAL WELDING

05 21 00 STEEL JOIST FRAMING

05 30 00 STEEL DECKS

05 40 00 COLD-FORMED METAL FRAMING

05 50 13 MISCELLANEOUS METAL FABRICATIONS

05 51 00 METAL STAIRS

05 51 33 METAL LADDERS

05 52 00 METAL RAILINGS

DI VI SI ON 06 - WOOD, PLASTI CS, AND COMPOSI TES

PROJECT TABLE OF CONTENTS Page 1

06 10 00 ROUGH CARPENTRY

06 41 16.00 10 PLASTIC-LAMINATE-CLAD ARCHITECTURAL CABINETS

06 61 16 SOLID SURFACING FABRICATIONS

DI VI SI ON 07 - THERMAL AND MOI STURE PROTECTI ON

07 05 23 PRESSURE TESTING AN AIR BARRIER SYSTEM FOR AIR TIGHTNESS

07 11 13 BITUMINOUS DAMPPROOFING

07 21 16 MINERAL FIBER BLANKET INSULATION

07 22 00 ROOF AND DECK INSULATION

07 24 00 SOFFIT STUCCO COATING SYSTEM

07 27 10.00 10 BUILDING AIR BARRIER SYSTEM

07 27 36 SPRAY FOAM AIR BARRIERS

07 60 00 FLASHING AND SHEET METAL

07 61 14.00 20 STEEL STANDING SEAM ROOFING

07 84 00 FIRESTOPPING

07 92 00 JOINT SEALANTS

DI VI SI ON 08 - OPENI NGS

08 11 13 STEEL DOORS AND FRAMES

08 11 16 ALUMINUM DOORS AND FRAMES

08 14 00 WOOD DOORS

08 31 00 ACCESS DOORS AND PANELS

08 34 19.10 20 ROLLING SERVICE DOORS

08 34 73 SOUND CONTROL DOOR ASSEMBLIES

08 41 13 ALUMINUM-FRAMED ENTRANCES AND STOREFRONTS

08 71 00 DOOR HARDWARE

08 81 00 GLAZING

08 91 00 METAL WALL LOUVERS

DI VI SI ON 09 - FI NI SHES

09 06 00 SCHEDULES FOR FINISHES

09 22 00 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 29 00 GYPSUM BOARD

09 30 10 CERAMIC, QUARRY, AND GLASS TILING

09 51 00 ACOUSTICAL CEILINGS

09 62 38 STATIC-CONTROL FLOORING

09 65 00 RESILIENT FLOORING

09 65 66 RESILIENT ATHLETIC FLOORING

09 67 23 RESINOUS FLOORING

09 68 00 CARPETING

09 69 13 RIGID GRID ACCESS FLOORING

09 84 20 ACOUSTICAL WALL PANELS

09 90 00 PAINTS AND COATINGS

DI VI SI ON 10 - SPECI ALTI ES

10 11 00 VISUAL DISPLAY UNITS

10 14 00.10 EXTERIOR SIGNAGE

10 14 00.20 INTERIOR SIGNAGE

10 21 13 TOILET COMPARTMENTS

10 22 39 FOLDING PANEL PARTITIONS

10 26 00 WALL AND DOOR PROTECTION

10 28 13 TOILET ACCESSORIES

10 44 16 FIRE EXTINGUISHERS

10 51 13 METAL LOCKERS

PROJECT TABLE OF CONTENTS Page 2

10 53 13.00 25 OVERHEAD SUPPORTED CANOPIES

10 56 13 STEEL SHELVING

DI VI SI ON 12 - FURNI SHI NGS

12 24 13 ROLLER WINDOW SHADES

12 61 13 UPHOLSTERED AUDIENCE SEATING

DI VI SI ON 13 - SPECI AL CONSTRUCTI ON

13 34 19 METAL BUILDING SYSTEMS

DI VI SI ON 14 - CONVEYI NG EQUI PMENT

14 24 23 HYDRAULIC PASSENGER ELEVATORS

DI VI SI ON 21 - FI RE SUPPRESSI ON

21 13 13.00 20 WET PIPE SPRINKLER SYSTEM, FIRE PROTECTION

21 30 00 FIRE PUMPS

DI VI SI ON 22 - PLUMBI NG

22 00 00 PLUMBING, GENERAL PURPOSE

22 31 00 WATER SOFTENERS, CATION-EXCHANGE (SODIUM CYCLE)

22 67 19.16 REVERSE-OSMOSIS WATER EQUIPMENT

DI VI SI ON 23 - HEATI NG, VENTI LATI NG, AND AI R CONDI TI ONI NG ( HVAC)

23 03 00.00 20 BASIC MECHANICAL MATERIALS AND METHODS

23 05 48.00 40 VIBRATION AND SEISMIC CONTROLS FOR HVAC PIPING AND

EQUIPMENT

23 05 93.00 25 TESTING, ADJUSTING, AND BALANCING FOR HVAC

23 07 00 THERMAL INSULATION FOR MECHANICAL SYSTEMS

23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC

23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC

23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING

CONTROL SYSTEMS

23 11 20 FACILITY GAS PIPING

23 23 00 REFRIGERANT PIPING

23 30 00 HVAC AIR DISTRIBUTION

23 52 33.00 25 HOT WATER BOILERS, CONDENSING TYPE

23 64 10 WATER CHILLERS, VAPOR COMPRESSION TYPE

23 64 26 CHILLED, CHILLED-HOT, AND CONDENSER WATER PIPING SYSTEMS

23 81 00 DECENTRALIZED UNITARY HVAC EQUIPMENT

23 82 00.00 20 TERMINAL HEATING UNITS

DI VI SI ON 25 - I NTEGRATED AUTOMATI ON

25 05 11.01 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS ENERGY

MANAGEMENT CONTROL SYSTEM (EMCS) BUILDING LEVEL ONLY

25 05 11.02 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS FIRE

ALARM REPORTING SYSTEM/MASS NOTIFICATION SYSTEM BUILDING

LEVEL ONLY

25 08 10 UTILITY MONITORING AND CONTROL SYSTEM TESTING

25 08 11.00 20 RISK MANAGEMENT FRAMEWORK FOR FACILITY-RELATED CONTROL

SYSTEMS

25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END

AND INTEGRATION

PROJECT TABLE OF CONTENTS Page 3

DI VI SI ON 26 - ELECTRI CAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 05 75.00 25 POWER SYSTEM STUDY FOR EXISTING INSTALLATION AND NEW

CONSTRUCTION PROJECTS

26 08 00 APPARATUS INSPECTION AND TESTING

26 12 19.10 THREE-PHASE, LIQUID-FILLED PAD-MOUNTED TRANSFORMERS

26 13 01 PAD-MOUNTED DEAD-FRONT AIR INSULATED SWITCHGEAR

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 24 13 SWITCHBOARDS

26 27 14.00 20 ELECTRICITY METERING

26 29 23 ADJUSTABLE SPEED DRIVE (ASD) SYSTEMS UNDER 600 VOLTS

26 41 00 LIGHTNING PROTECTION SYSTEM

26 51 00 INTERIOR LIGHTING

26 56 00 EXTERIOR LIGHTING

DI VI SI ON 27 - COMMUNI CATI ONS

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

27 41 00 AUDIO VISUAL SYSTEMS

DI VI SI ON 28 - ELECTRONI C SAFETY AND SECURI TY

28 31 76 INTERIOR FIRE ALARM AND MASS NOTIFICATION SYSTEM

DI VI SI ON 31 - EARTHWORK

31 05 21 GEOGRID SOIL REINFORCEMENT

31 23 00.00 20 EXCAVATION AND FILL

31 31 16.13 CHEMICAL TERMITE CONTROL

31 63 29 DRILLED CONCRETE PIERS AND SHAFTS

DI VI SI ON 32 - EXTERI OR I MPROVEMENTS

32 11 20 BASE COURSE FOR RIGID AND SUBBASES FOR FLEXIBLE PAVING

32 12 13 BITUMINOUS TACK AND PRIME COATS

32 12 16 HOT-MIX ASPHALT (HMA) FOR ROADS

32 16 19 CONCRETE CURBS, GUTTERS AND SIDEWALKS

32 17 23 PAVEMENT MARKINGS

32 31 13 CHAIN LINK GATES

32 92 19 SEEDING

32 92 23 SODDING

DI VI SI ON 33 - UTI LI TI ES

33 11 00 WATER UTILITY DISTRIBUTION PIPING

33 12 33.00 30 WATER UTILITY METERING

33 30 00 SANITARY SEWERAGE

33 40 00 STORM DRAINAGE UTILITIES

33 51 13.00 30 NATURAL-GAS METERING

33 51 15 NATURAL-GAS DISTRIBUTION PIPELINES

33 71 01 OVERHEAD TRANSMISSION AND DISTRIBUTION

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

33 82 00 TELECOMMUNICATIONS OUTSIDE PLANT (OSP)

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 4

SECTION 25 05 11.01

CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS

ENERGY MANAGEMENT CONTROL SYSTEM (EMCS)

BUILDING LEVEL ONLY

11/17

PART 1 GENERAL

This Section includes requirements in support of the DOD Risk Management Framework (RMF) for implementing cybersecurity. Refer to UFC 04-010-06, Cybersecurity for Facility-Related Control Systems for requirements on incorporating cybersecurity into control system design and for general information on the RMF process as it applies to control systems.

Assistance for control system cybersecurity is available from the following Service organizations:

a. Navy: Naval Facilities Engineering Command, Command Information Office (CIO).

b. Air Force: Civil Engineer Maintenance, Inspection, and Repair Team (CEMIRT) ICS Branch, Tyndall AFB.

Many subparts in this Section contain text in curly braces ("{" and "}") indicating which cybersecurity control and control correlation identifier (CCI) the requirements of the subpart relate to. The text inside these curly braces is for Government reference only, and enables coordination of the requirements of this Section with the RMF process throughout the design and construction process. Text in curly braces are not Contractor requirements.

This Section refers to Security Requirements Guide (SRGs) and Security Technical Implementation Guide (STIGs). STIGs and SRGs are available online at the DoD Cyber Exchange website at https://public.cyber.mil/ .

Not all control system components have applicable STIGs or SRGs. Some STIGs or SRGs may require authentication by Common Access Card (CAC).

1.1 CONTROL SYSTEM APPLICABILITY

There are multiple versions of this Section associated with this project.

Different versions have requirements applicable to different control systems. This specific Section applies only to the following control systems: EMCS (Building Level Controls Only).

1.2 RELATED REQUIREMENTS

All Sections containing facility-related control systems or control system components are related to the requirements of this Section. Review all specification sections to determine related requirements.

This section must be used in conjunction with other technical control system specifications and UFGS 25 08 11.00 20 RISK MANAGEMENT FRAMEWORK

FOR FACILITY-RELATED CONTROL SYSTEMS.

1.3 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by

SECTION 25 05 11.01 Page 1 the basic designation only.

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE 135 (2016) BACnet—A Data Communication Protocol for Building Automation and Control Networks

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

IEEE 802.1x (2010) Local and Metropolitan Area Networks - Port Based Network Access Control

U.S. DEPARTMENT OF DEFENSE (DOD)

DODI 8551.01 (2014) Ports, Protocols, and Services Management (PPSM)

DTM 08-060 (2008) Policy on Use of Department of Defense (DoD) Information Systems - Standard Consent Banner and User Agreement

UFC 4-010-06 (2016; with Change 1, 2017) Cybersecurity of Facility-Related Control Systems

1.4 DEFINITIONS

1.4.1 Computer

As used in this Section, a computer is one of the following:

a. A device running a non-embedded desktop or server version of Microsoft Windows.

b. A device running a non-embedded version of MacOS.

c. A device running a non-embedded version of Linux.

d. A device running a version or derivative of the Android OS, where Android is considered separate from Linux.

e. A device running a version of Apple iOS.

1.4.2 Network Connected

A component is network connected (or "connected to a network") only when the device has a network transceiver which is directly connected to the network and implements the network protocol. A device lacking a network transceiver (and accompanying protocol implementation) can never be considered network connected. Note that a device connected to a non-IP network is still considered network connected (an IP connection or IP address is not required for a device to be network connected).

Any device that supports wireless communication is network connected, regardless of whether the device is communicating using wireless .

SECTION 25 05 11.01 Page 2

1.4.3 User Account Support Levels

The support for user accounts is categorized in this Section as one of three levels:

1.4.3.1 FULLY Supported

Device supports configurable individual accounts. Accounts can be created, deleted, modified, etc. Privileges can be assigned to accounts.

1.4.3.2 MINIMALLY Supported

Device supports a small, fixed number of accounts (perhaps only one).

Accounts cannot be modified. A device with only a "User" and an "Administrator" account would fit this category. Similarly, a device with two PINs for logon - one for restricted and one for unrestricted rights would fit here (in other words, the accounts do not have to be the traditional "user name and password" structure).

1.4.3.3 NOT Supported

Device does not support any Access Enforcement therefore the whole concept of "account" is meaningless.

1.4.4 User Interface

Generally, a user interface is hardware on a device allowing user interaction with that device via input (buttons, switches, sliders, keyboard, touch screen, etc.) and a screen. There are three types of user interfaces defined in this Section: Limited Local User Interface, Full Local User Interface and Remote User Interface. In this Section, when the term "User Interface" is used without specifying which type, it refers only to Full Local User Interface and Remote User Interface (NOT to Limited Local User Interface).

1.4.4.1 Limited Local User Interface

A Limited Local User Interface is a user interface where the interaction is limited, fixed at the factory, and cannot be modified in the field.

The user must be physically at the device to interact with it.

Examples of Limited Local User Interface include thermostats (Space Sensor Modules as defined in Section 23 09 13 INSTRUMENTATION AND CONTROL DEVICES

FOR HVAC).

1.4.4.2 Full Local User Interface

A Full Local User Interface is a user interface where the interaction and displays are field-configurable.

Examples of a Full Local User Interface include local applications on a computer and user interfaces to Variable Speed Drives .

1.4.4.3 Remote User Interface

A Remote User Interface is a user interface on a Client device allowing user interaction with a different Server device. The user need not be physically at the Server device to interact with it.

SECTION 25 05 11.01 Page 3

Examples of Remote User Interfaces include web browsers and Local Display Panels as defined in Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC .

1.5 ADMINISTRATIVE REQUIREMENTS

1.5.1 Coordination

Coordinate the execution of this Section with the execution of all other Sections related to control systems as indicated in the paragraph RELATED REQUIREMENTS. Items that must be considered when coordinating project efforts include but are not limited to:

a. If requesting permission for the use of a device with multiple IP connections, the Multiple IP Connection Device Request must be approved prior to control system device selection and integration.

b. If the Device Audit Record Upload Software is to be installed on a computer not being provided as part of the control system, coordination is required to identify the computer on which to install the software.

c. Cybersecurity testing support must be coordinated across control systems and with the Government cybersecurity testing schedule.

d. Passwords must be coordinated with the indicated contact for the project site.

e. If applicable, HTTP web server certificates must be obtained from the indicated contact for the project site.

f. Contractor Computer Cybersecurity Compliance Statements for each Contractor using Contractor owned computers.

1.5.2 Authorizing and Owning Authorities

Coordination also requires interfacing with the System Owner(s) (SOs) and the Authorizing Official(s) (AOs) for each control system to ensure that security control sets and required supporting documentation are in agreement with the system categorization(s) of each system and the particular requirements for each branch of the service.

The Authorizing Official for this control system accreditation is:

Name: TBD Title: CIO4 Organization: NAVFAC Southeast

The System Owner is:

Name: TBD Organization: 301st MSG, NAS JRB Forth Worth

The change management process for existing control systems that will be extended or modified as a result of this Project will also need to be understood and coordinated with the individuals listed above to support any existing accreditations or ongoing accreditation activities.

1.5.3 Categorization and Controls

The proposed security categorization (C-I-A levels) has not been approved

SECTION 25 05 11.01 Page 4 as of this submittal, but based on AFCEC guidance, this system will be categorized as Low-Low-Low (L-L-L). The list of security controls included as an Appendix to this Section are based on this security categorization.

1.6 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00

SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Device Account Lock Exception Request; G

Contractor Computer Cybersecurity Compliance Statements; G

Contractor Temporary Network Cybersecurity Compliance Statements; G

Qualifications; G

SD-02 Shop Drawings

User Interface Banner Schedule; G

Network Communication Report; G

Cybersecurity Riser Diagram; G

Control System Inventory Report; G

Proposed Security Technical Implementation Guides; G

SD-03 Product Data

Control System Cybersecurity Documentation; G

SD-07 Certificates

Software Licenses; G

SD-11 Closeout Submittals

Password Summary Report; G

Software Recovery And Reconstitution Images; G

Device Audit Record Upload Software; G

Completed Security Technical Implementation Guides Checklist; G

Completed NESSUS/ACAS Scans; G

1.7 QUALITY CONTROL

1.7.1 Qualifications

For the positions listed below, submit resumes to the Government within 14

SECTION 25 05 11.01 Page 5 days after notice to proceed. All certifications must be in effect prior to being hired. These positions may serve across the contract.

1.7.1.1 Cybersecurity Subject Matter Expert

The individual will oversee all work within this specification. This position requires that the individual currently meets Information Assurance Manager Level II Certification in accordance with DoDI 8570 Information Workforce Improvement Program. Individuals for this position should have experience securing DoD Systems and with Risk Management Framework. Control System Experience is highly desirable.

1.7.1.2 Computing Environment (System Administrator) and Network Personnel

The individual will complete all work at the computing level environment.

This position requires that the individual meet Information Assurance Technical Level II Certification in accordance with DoDI 8570 Information Workforce Improvement Program. Individuals for this position should have experience in securing DoD Systems, Security Technical Implementation Guides, and associated tools and practices. Control System experience is highly desirable.

1.8 CYBERSECURITY DOCUMENTATION

1.8.1 Network Communication Report

{For Reference Only: This subpart (and its subparts) relates to CA-9;

CCI-002102, CCI-002103, CCI-002104, CCI-002105 and also the submittal requirements associated with CM-6, CM-7 and SC-41 }

Provide a network communication report. For each networked controller, document the communication characteristics of the controller including communication protocols, services used, and a general description of what information is communicated over the network. For each controller using IP, document all TCP and UDP ports used. If other control system Sections used on this project include submittals documenting this information, provide copies of those submittals to meet this requirement.

In addition to the requirements of Section 01 33 00 SUBMITTAL PROCEDURES, provide the Network Communication Report as an editable Microsoft Excel file.

1.8.2 Control System Inventory Report

{For Reference Only: This subpart (and its subparts) relates to CM-8(a), CP-12, SI-17, IA-3; CCI-000389, CCI-000392, CCI-000398, CCI-002855, CCI-002856, CCI-002857, CCI-002773, CCI-002774, CCI-002775, CCI-000777, CCI-000778, CCI-001958}

Provide a Control System Inventory report using the Inventory Spreadsheet listed under this Section at http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ forms-graphics-tables documenting all devices, including networked devices, network infrastructure devices, non-networked devices, input devices (e.g., sensors) and output devices (e.g., actuators). For each device provide all applicable information for which there is a field on the spreadsheet in accordance with the instructions on the spreadsheet.

In addition to the requirements of Section 01 33 00 SUBMITTAL PROCEDURES, SECTION 25 05 11.01 Page 6 provide the Control System Inventory Report as an editable Microsoft Excel file.

1.8.3 Software Recovery and Reconstitution Images

{For Reference Only: This subpart (and its subparts) relates to CP-10;

CCI-000550, CCI-000551, CCI-000552}

For each computer on which software is installed under this project, provide a recovery image of the final as-built computer. This image must allow for bare-metal restore such that restoration of the image is sufficient to restore system operation to the imaged state without the need for re-installation of software.

If additional user permissions are required to meet this requirement, coordinate the creation of the image with the Government.

1.8.4 Cybersecurity Riser Diagram

{For Reference Only: This subpart (and its subparts) relates to PL-2(a);

CCI-003051, CCI-003053}

Provide a cybersecurity riser diagram of the complete control system including all network and controller hardware. If the control system specifications require a riser diagram submittal, provide a copy of that submittal as the cybersecurity riser diagram. Otherwise, provide a riser diagram in one-line format overlayed on a facility schematic.

1.8.5 Control System Cybersecurity Documentation

This subpart (and its subparts) relates to SA-5 (a),(b),(c); CCIs:

CCI-003124, CCI-003125, CCI-003126, CCI-003127, CCI-003128, CCI-003129,

CCI-003130, CCI-003131}

Provide a Control System Cybersecurity Documentation submittal containing the indicated information for each device and software application.

1.8.5.1 Software Applications

For all software applications running on computers provide:

a. Administrator documentation that describes secure configuration of the software {relates to CCI-003124}.

b. Administrator documentation that describes secure installation of the software {relates to CCI-003125}.

c. Administrator documentation that describes secure operation of the software {relates to CCI-003124}.

d. Administrator documentation that describes effective use and maintenance of security functions or mechanisms for the software {relates to CCI-003127}.

e. Administrator documentation that describes known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions for the software {relates to CCI-003128}.

f. User documentation that describes user-accessible security functions

SECTION 25 05 11.01 Page 7 or mechanisms in the software and how to effectively use those security functions or mechanisms {relates to CCI-003129}.

g. User documentation that describes methods for user interaction which enables individuals to use the software in a more secure manner {relates to CCI-003130}.

h. User documentation that describes user responsibilities in maintaining the security of the software {relates to CCI-003131}.

1.8.5.2 For EMCS Control System Devices

1.8.5.2.1 EMCS Control System Devices FULLY Supporting User Accounts

For all EMCS Control System Devices which FULLY support user accounts, provide:

a. Documentation that describes secure configuration of the device {for reference only: Relates to CCI-003124}.

b. Documentation that describes secure operation of the device {for reference only: Relates to CCI-003124}.

c. Documentation that describes effective use and maintenance of security functions or mechanisms for the device {for reference only: Relates to CCI-003127}.

d. Documentation that describes known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions for the device {for reference only: Relates to CCI-003128}.

e. Documentation that describes user-accessible security functions or mechanisms in the device and how to effectively use those security functions or mechanisms; or a specific indication that there are no user-accessible security functions or mechanisms in the device {for reference only: Relates to CCI-003129}.

f. Documentation that describes methods for user interaction which enables individuals to use the device in a more secure manner {for reference only: Relates to CCI-003130}.

1.8.5.2.2 All Other EMCS Control System Devices

For all EMCS Control System Devices which do not FULLY support user accounts, provide:

a. Documentation that describes secure configuration of the device; or a specific indication that there are no secure configuration steps that apply {for reference only: Relates to CCI-003124}.

b. Documentation that describes effective use and maintenance of security functions or mechanisms for the device; or a specific indication that there are no security functions or mechanisms in the device {for reference only: Relates to CCI-003127}.

c. For devices which include a user interface, documentation that describes methods for user interaction which enables individuals to use the device in a more secure manner {for reference only: Relates to CCI-003130}.

SECTION 25 05 11.01 Page 8

1.8.5.3 Default Requirements for Control System Devices

For control system devices where Control System Cybersecurity Documentation requirements are not otherwise indicated in this Section, provide:

a. Documentation that describes secure configuration of the device {for reference only: Relates to CCI-003124}.

b. Documentation that describes secure installation of the device {for reference only: Relates to CCI-003125}.

c. Documentation that describes secure operation of the device {for reference only: Relates to CCI-003124}.

d. Documentation that describes effective use and maintenance of security functions or mechanisms for the device {for reference only: Relates to CCI-003127}.

e. Documentation that describes known vulnerabilities regarding configuration and use of administrative (i.e., privileged) functions for the device {for reference only: Relates to CCI-003128}.

f. Documentation that describes user-accessible security functions or mechanisms in the device and how to effectively use those security functions or mechanisms {for reference only: Relates to CCI-003129}.

g. Documentation that describes methods for user interaction which enables individuals to use the device in a more secure manner {for reference only: Relates to CCI-003130}.

h. Documentation that describes user responsibilities in maintaining the security of the device {for reference only: Relates to CCI-003131}.

1.8.6 Proposed Security Technical Implementation Guides

Provide a proposed list of Security Technical Implementation Guides (STIGS) matched to the corresponding hardware/software as well as a completed hardware/software list for the control system devices. The proposed STIG list should include all operating system, application, network and other hardware devices. If there is no corresponding STIG for a device or application and there is a generic STIG that can be applied list that generic STIG.

1.9 SOFTWARE UPDATE LICENSING

{For Reference Only: This subpart (and its subparts) relates to SI-2 (a), (c); CCI-001227, CCI-002605}

In addition to all other licensing requirements, all software licensing must include licensing of the following software updates for a period of no less than 5 years:

a. Security and bug-fix patches issued by the software manufacturer.

b. Security patches to address any vulnerability identified in the National Vulnerability Database at http://nvd.nist.gov with a Common Vulnerability Scoring System (CVSS) severity rating of MEDIUM or

SECTION 25 05 11.01 Page 9 higher.

Provide a single Software Licenses submittal with documentation of the software licenses for all software provided.

1.10 CYBERSECURITY DURING CONSTRUCTION

{For Reference Only: This subpart (and its subparts) relates to AC-18, SA-3, CCI-00258}

In addition to the control system cybersecurity requirements indicated in this section an as noted in UFC 4-010-06 , meet following requirement throughout the construction process.

1.10.1 Contractor Computer Equipment

Contractor owned computers may be used for construction. When used, Contractor computers must meet the following requirements:

1.10.1.1 Operating System

The operating system must be an operating system currently supported by the manufacturer of the operating system. The operating system must be current on security patches and operating system manufacturer required updates.

1.10.1.2 Anti-Malware Software

The computer must run anti-malware software from a reputable software manufacturer. Anti-malware software must be a version currently supported by the software manufacturer, must be current on all patches and updates, and must use the latest definitions file. All computers used on this project must be scanned using the installed software at least once per day.

1.10.1.3 Passwords and Passphrases

The passwords and passphrases for all computers must be changed from their default values. Passwords must be a minimum of eight characters with a minimum of one uppercase letter, one lowercase letter, one number and one special character.

1.10.1.4 Contractor Computer Cybersecurity Compliance Statements

Provide a single submittal containing completed Contractor Computer Cybersecurity Compliance Statements for each company using Contractor owned computers. Contractor Computer Cybersecurity Compliance Statements must use the template published at http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ forms-graphics-tables . Each Statement must be signed by a cybersecurity representative for the relevant company.

1.10.2 Temporary IP Networks

Temporary Contractor-installed IP networks may be used during construction. When used, temporary Contractor-installed IP networks must meet the following requirements:

SECTION 25 05 11.01 Page 10

1.10.2.1 Network Boundaries and Connections

The network must not extend outside the project site and must not connect to any IP network other than IP networks provided under this project or Government furnished IP networks provided for this purpose. Any and all network access from outside the project site is prohibited.

1.10.3 Government Access to Network

Government personnel must be allowed to have complete and immediate access to the network at any time in order to verify compliance with this specification.

1.10.4 Temporary Wireless IP Networks

In addition to the other requirements on temporary IP networks, temporary wireless IP (WiFi) networks must not interfere with existing wireless network and must use WPA2 security. Network names (SSID) for wireless networks must be changed from their default values.

1.10.5 Passwords and Passphrases

The passwords and passphrases for all network devices and network access must be changed from their default values. Passwords must be a minimum 8 characters with a minimum of one uppercase letter, one lowercase letter, one number and one special character.

1.10.6 Contractor Temporary Network Cybersecurity Compliance Statements

Provide a single submittal containing completed Contractor Temporary Network Cybersecurity Compliance Statements for each company implementing a temporary IP network. Contractor Temporary Network Cybersecurity Compliance Statements must use the template published at http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ forms-graphics-tables . Each Statement must be signed by a cybersecurity representative for the relevant company. If no temporary IP networks will be used, provide a single copy of the Statement indicating this.

1.11 CYBERSECURITY DURING WARRANTY PERIOD

All work performed on the control system after acceptance must be performed using Government Furnished Equipment or equipment specifically and individually approved by the Government.

PART 2 PRODUCTS

(NOT USED)

PART 3 EXECUTION

3.1 ACCESS CONTROL REQUIREMENTS

3.1.1 User Accounts

{For Reference Only: This subpart (and its subparts) relate to AC-2(a)and

AC-3; CCI-002110, CCI-000213.}

Any device supporting user accounts (either FULLY or MINIMALLY) must limit access to the device according to specified limitations for each account.

SECTION 25 05 11.01 Page 11

Install and configure any device having a STIG or SRG in accordance with that STIG or SRG.

3.1.1.1 Computers

All computers must FULLY support user accounts.

3.1.1.2 For EMCS Control System Devices

Devices with web interfaces must either FULLY support user accounts or have their web interface disabled. Field devices with full local user interfaces allowing modification of data must at least MINIMALLY support user accounts.

3.1.1.3 Default Requirements for Control System Devices

For control system devices where User Account requirements are not otherwise indicated in this Section:

a. Devices with web interfaces must either at least MINIMALLY support user accounts or have their web interface disabled.

b. Field devices with full local user interfaces allowing modification of data must at least MINIMALLY support user accounts.

c. Field devices with read-only full local user interfaces must at least MINIMALLY support user accounts.

3.1.2 Unsuccessful Logon Attempts

{For Reference Only: This subpart (and its subparts) relate AC-7 (a), AC-7 (b); CCI-000043, CCI-000044, CCI-001423, CCI-002236, CCI-002237, CCI-002238}

Except for high availability user interfaces indicated as exempt, devices must meet the indicated requirements for handling unsuccessful logon attempts.

3.1.2.1 Devices MINIMALLY Supporting Accounts

Devices which MINIMALLY support accounts are required to lock when three unsuccessful logon attempts occur within a 15 minute interval unless a life safety issue will occur.

3.1.2.2 Devices FULLY Supporting Accounts

Devices which FULLY support accounts must meet the following requirements. If a device cannot meet these requirements, document device capabilities to protect from subsequent unsuccessful logon attempts and propose alternate protections in a Device Account Lock Exception Request submittal. Do not implement alternate protection measures without explicit permission from the Government.

a. It must lock the user account when three unsuccessful logon attempts occur within a 15 minute interval.

b. Once an account is locked, the account must stay locked until unlocked by an administrator.

SECTION 25 05 11.01 Page 12

c. Once the indicated number of unsuccessful logon attempts occurs, delay further logon prompts by 5 seconds.

3.1.2.3 High Availability Interfaces Exempt from Unsuccessful Logon Attempts Requirements

There are no high availability interfaces which are exempt from unsuccessful logon attempts requirements.

3.1.3 System Use Notification

{For Reference Only: This subpart (and its subparts) relates to AC-8;

CCI-000048, CCI-002247, CCI-002243, CCI-002244, CCI-002245, CCI-002246,

CCI-000050, CCI-002248}

Web interfaces must display a warning banner meeting the requirements of

DTM 08-060 .

Devices which are connected to a network and have a user interface must display a warning banner meeting the requirements of DTM 08-060 if capable of doing so. Devices which are connected to a network and have a user interface but are not capable of displaying a banner must have a permanently affixed label displaying an approved banner from DTM 08-060 .

Labels must be machine printed or engraved, plastic or metal, designed for permanent installation, must use a font no smaller than 14 point, and must provide a high contract between font and background colors.

3.1.3.1 User Interface Banner Schedule

Provide a User Interface Schedule using the format indicated showing each user interface provided and how the information banner requirement has been implemented for each user interface.

User I nt er f ace Schedul e For mat ( wi t h sampl e ent r i es)

User I nt er f ace Description

User I nt er f ace Location

Type of User Interface

Banner I mpl ement at i on

Sample 1 Room 1 Remote DTM 08-060 Banner "A" Displayed at Logon

Sample 2 Room 2 Limited Local DTM 08-060 Banner "B" on Affixed Label

Sample 3 Room 3 Full Local DTM 08-060 Banner "B" Displayed on Screen

3.1.4 Permitted Actions Without Identification or Authentication

{For Reference Only: This subpart (and its subparts) relates to AC-14;

CCI-000061, CCI-000232}

The control system must require identification and authentication before allowing any actions by a user acting from a user interface which MINIMALLY or FULLY supports accounts.

SECTION 25 05 11.01 Page 13

3.1.5 Wireless Access

{For Reference Only: This subpart (and its subparts) relates to AC-18;

CCI-001438, CCI-001439, CCI-002323, CCI-001441}

Unless explicitly authorized by the Government, do not use any wireless communication. Any device with wireless communication capability is considered to be using wireless communication, regardless of whether or not the device is actively communicating wirelessly, except when wireless communication has been physically permanently disabled (such as through the removal of the wireless transceiver).

3.1.5.1 Wireless IP Communications

Unless specifically approved and installed in accordance with the project site requirements, do not install wireless IP networks, including: Do not install a wireless access point; do not install or configure an ad-hoc wireless network; do not install or configure a WiFi Direct communication.

When explicitly authorized by the Government, wireless IP communication may be used to communicate with an existing wireless network.

3.1.5.2 Non-IP Wireless Communication

When non-IP wireless communication is explicitly authorized by the Government, use the maximum level of encryption supported by the specific protocol employed and select signal strength and radiated power to the minimum necessary for reliable communication.

3.2 CYBERSECURITY AUDITING

3.2.1 Audit Events, Content of Audit Records, and Audit Generation

{For Reference Only: This subpart (and its subparts) relates to AU-2(a),(c),(d), AU-3, AU-12; CCI-000123, CCI-001571, CCI-000125, CCI-001485, CCI-000130, CCI-000131, CCI-000132, CCI-00133, CCI-000134, CCI-001487, CCI-000169, CCI-001459, CCI-000171, CCI-000172, CCI-001910}

For devices that have STIG/SRGs related to audit events, content of audit records or audit generation, comply with the requirements of those STIG/SRGs.

3.2.1.1 Computers

For each computer, provide the capability to select audited events and the content of audit logs. Configure computers to audit the indicated events, and to record the indicated information for each auditable event.

3.2.1.1.1 Audited Events

Configure each computer to audit the following events:

a. Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels).

b. Successful and unsuccessful logon attempts.

SECTION 25 05 11.01 Page 14

c. Privileged activities or other system level access.

d. Starting and ending time for user access to the system.

e. Concurrent logons from different workstations.

f. Successful and unsuccessful accesses to objects.

g. All program initiations.

h. All direct access to the information system.

i. All account creations, modifications, disabling, and terminations.

j. All kernel module load, unload, and restart.

3.2.1.1.2 Audit Event Information To Record

Configure each computer to record, for each auditable event, the following information (where applicable to the event):

a. What type of event occurred.

b. When the event occurred.

c. Where the event occurred.

d. The source of the event.

e. The outcome of the event.

f. The identity of any individuals or subjects associated with the event.

3.2.1.2 For EMCS Control System Devices

3.2.1.2.1 EMCS Control System Devices FULLY Supporting User Accounts

For devices FULLY supporting accounts, provide the capability to select audited events, and the contents of audit logs. Configure devices to audit the following events:

a. Successful and unsuccessful logon attempts to the device.

b. Starting and ending time for user access to the device.

c. All account creations, modifications, disabling, and terminations.

d. All device shutdown and startup.

Configure the device to record for each event the following information (as applicable): The type of event, when the event occurred and the identity of any individuals or subjects associated with the event.

3.2.1.2.2 Other EMCS Control System Devices

There are no requirements to perform auditing at EMCS field devices that do not FULLY support accounts.

SECTION 25 05 11.01 Page 15

3.2.1.3 Default Requirements for Control System Devices

For control system devices where Audit Events, Content of Audit Records, and Audit Generation are not otherwise indicated in this Section:

3.2.1.3.1 Devices Which FULLY Support Accounts

For each device which FULLY supports accounts, provide the capability to select audited events and the content of audit logs. Configure devices to audit the indicated events, and to record the indicated information for each auditable event.

3.2.1.3.1.1 Audited Events

Configure each device to audit the following events:

a. Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels).

b. Successful and unsuccessful logon attempts.

c. Privileged activities or other system level access.

d. Starting and ending time for user access to the system.

e. Concurrent logons from different workstations.

f. All account creations, modifications, disabling, and terminations.

g. All kernel module load, unload, and restart.

3.2.1.3.1.2 Audit Event Information To Record

Configure each computer to record, for each auditable event, the following information (where applicable to the event):

a. What type of event occurred.

b. When the event occurred.

c. Where the event occurred.

d. The source of the event.

e. The outcome of the event.

f. The identity of any individuals or subjects associated with the event.

3.2.1.3.2 Devices Which Do Not FULLY Support Accounts

For each Device which does not FULLY support accounts configure the device to audit all device shutdown and startup events and to record for each event the type of event and when the event occurred.

3.2.2 Audit Storage Capacity and Audit Upload

{For Reference Only: This subpart (and its subparts) relates to AU-4;

CCI-001848, CCI-001849}

SECTION 25 05 11.01 Page 16

a. For devices that have STIG/SRGs related to audit storage capacity (CCI-001848 or CCI-001849) comply with the requirements of those STIG/SRGs.

b. For non-computer control system devices capable of generating audit records, provide 60 days worth of secure local storage, assuming 10 auditable events per day.

c. For computers, provide storage for at least 90 days of audit records.

3.2.2.1 Device Audit Record Upload Software

For each non-computer device required to audit events, provide, and license to the Government, software implementing a secure mechanism of uploading audit records from the device to a computer and of exporting the uploaded audit records as a Microsoft Excel file or comma separated value text file. Where different devices use different software, provide software of each type required to upload audit logs from all devices.

Submit copies of device audit record upload software. If there are no non-computer devices requiring auditing, provide a document stating this in lieu of this submittal.

3.2.3 Response to Audit Processing Failures

{For Reference Only: This subpart (and its subparts) relates to AU-5;

CCI-000139, CCI-000140, CCI-001490}.

Front end computers associated with auditing must, in the case of a failure in the auditing system, notify the ISSM. In case of an audit failure, if possible, continue to collect audit records by overwriting existing audit records.

3.2.4 Time Stamps

{For Reference Only: This subpart (and its subparts) relates to AU-8;

CCI-000159, CCI-001889, CCI-001890}

3.2.4.1 Computers

Computers generating audit records must have internal clocks capable of providing time with a resolution of 1 second. Clocks must not drift more than 10 seconds per day.

Configure the system so that each computer generating audit records maintains accurate time to within 1 second.

3.2.4.2 For EMCS Control System Devices

Devices generating audit records must have internal clocks capable of providing time with a resolution of 1 second. Clocks cannot drift more than 10 seconds per day. Configure the system so that each device generating audit records maintains accurate time to within 1 second.

3.2.4.3 Default Requirements for Control System Devices

For control system devices where Time Stamps requirements are not otherwise indicated in this Section: Devices generating audit records

SECTION 25 05 11.01 Page 17 must have internal clocks capable of providing time with a resolution of 1 second. Clocks must not drift more than 10 seconds per day. Configure the system so that each device generating audit records maintains accurate time to within 1 second.

3.3 REQUIREMENTS FOR LEAST FUNCTIONALITY

{For Reference Only: This subpart (and its subparts), along with the network communication report submittal specified elsewhere in this section, relates to CM-6 (a), (c), CM-7, CM-7 (1)(b), SC-41; CCI-000363, CCI-000364, CCI-000365, CCI-001588, CCI-001755, CCI-000381, CCI-000380, CCI-00382, CCI-001761, CCI-001762, CCI-002544, CCI-002545, CCI-002546.}

For devices that have a STIG or SRG related to Requirements for Least Functionality (such as configuration settings and port and device I/O access for least functionality), install and configure the device in accordance with that STIG or SRGs.

For EMCS Control Systems: Do not provide devices with user interfaces where one was not required. Do not use a networked sensor or actuator where a non-networked sensor or actuator would suffice.

For Other Control Systems: Do not provide devices with user interfaces where one was not required. Do not use a networked sensor or actuator where a non-networked sensor or actuator would suffice.

3.3.1 Non-IP Control Networks

When control system specifications require particular communication protocols, use only those communication protocols and only as specified.

Do not implement any other communication protocol, or use any protocol on ports other than those specified.

When control system specifications do not indicate requirements for communication protocols, use only those protocols required for operation of the system as specified.

3.3.2 IP Control Networks

Do not use nonsecure functions, ports, protocols and services as defined in DODI 8551.01 unless those ports, protocols and services are specifically required by the control system specifications or otherwise specifically authorized by the Government. Do not use ports, protocols and services that are not specified in the control system specifications or required for operation of the control system.

3.4 SAFE MODE AND FAIL SAFE OPERATION

{For Reference Only: This subpart (and its subparts) relates to CP-12, SI-17; CCI-002855, CCI-002856, CCI-002857, CCI-002773, CCI-002774, CCI-002775}

For all control system components with an applicable STIG or SRG, configure the component in accordance with all applicable STIGs and SRGs.

SECTION 25 05 11.01 Page 18

3.5 IDENTIFICATION AND AUTHENTICATION

3.5.1 User Identification and Authentication

{For Reference Only: This subpart (and its subparts) relates to

IA-2,(1),(12); CCI-000764, CCI-000765, CCI-001953, CCI-001954}

a. Devices that FULLY support accounts must uniquely identify and authenticate organizational users.

b. Devices which allow network access to privileged accounts must implement multifactor authentication for network access to privileged accounts.

3.5.1.1 EMCS Control Systems Devices

Identification and Authentication for network access to privileged accounts must be implemented by either accepting and electronically verify Personal Identity Verification (PIV) credentials or inheriting identification and authentication from the operating system.

3.5.1.2 Default Requirements for Control System Devices

For control system devices where User Identification and Authentication requirements are not otherwise indicated in this Section, User Identification and Authentication for network access to privileged accounts must be implemented by inheriting identification and authentication from the operating system.

3.5.2 Authenticator Management

{For Reference Only: This subpart (and its subparts) relates to IA-5 (b),(c),(e),(g),(1),(11); CCI-000176, CCI-001544, CCI-001989, CCI-000182, CCI-001610, CCI-000192, CCI-000193, CCI-000194, CCI-000205, CCI-001619, CCI-001611, CCI-001612, CCI-001613, CCI-001614, CCI-000195, CCI-001615, CCI-000196, CCI-000197, CCI-000199, CCI-000198, CCI-001616, CCI-001617, CCI-000200, CCI-001618, CCI-002041, CCI-002002, CCI-002003}

3.5.2.1 Authentication Type

3.5.2.1.1 For EMCS Control System Devices

Unless otherwise indicated:

a. Software which FULLY supports accounts and which runs on a computer must use password-based authentication or hardware token-based authentication.

b. Other devices which FULLY support accounts must use password-based authentication.

c. Devices MINIMALLY supporting accounts must use password-based authentication.

3.5.2.1.2 Default Requirements for Control System Devices

For control system devices where Authentication Type requirements are not otherwise indicated in this Section:

SECTION 25 05 11.01 Page 19

a. Software which FULLY supports accounts and which runs on a computer must use password-based authentication or hardware token-based authentication.

b. Other devices which FULLY support accounts must use either password-based authentication or hardware token-based authentication.

c. Devices MINIMALLY supporting accounts must use either password-based authentication or hardware token-based authentication.

3.5.2.2 Password-Based Authentication Requirements

3.5.2.2.1 Passwords for Computers

All computers supporting password-based authentication must enforce the following…