West Point Bldg. 620 Repair RTA Specifications (Vol. IV) Rev 1.pdf

West Point Building 620 Repair West Point, NY

RTA Specifications Volume IV

USACE New York District USACE Contract No. W91278-18-D-0004

May 29, 2020

West Point Building 620 Repair - West Point, NY Ready to Advertise 05/29/2020

THIS PAGE INTENTIONALLY LEFT BLANK

West Point Bldg. 620 Repair

West Point, NY

PN: 93952

May 29, 2020 Burns & McDonnell 9400 Ward Parkway

Kansas City, MO 64114

CERTIFICATION PAGE

CIVIL STRUCTURAL ARCHITECTURAL

FIRE PROTECTION MECHANICAL ELECTRICAL

5/29/20205/29/2020

THIS PAGE INTENTIONALLY LEFT BLANK

PROJECT TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

00 00 01 COVER SHEET

00 00 02 CHECK LIST FOR BIDDERS

00 10 00 SF 1442 AND BIDDING SCHEDULE

00 21 16 INSTRUCTIONS, CONDITIONS, AND NOTICE TO BIDDERS

00 22 20 PROPOSAL SUBMISSION REQUIREMENTS AND INSTRUCTIONS

00 24 00 EVALUATION FACTORS FOR AWARD

00 72 00 CONTRACT CLAUSES

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 22 00.00 10 PRICE AND PAYMENT PROCEDURES

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 33 29 SUSTAINABILITY REPORTING

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 QUALITY CONTROL

01 45 00.15 10 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM)

01 45 35 SPECIAL INSPECTIONS

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 58 00 PROJECT IDENTIFICATION

01 74 19 CONSTRUCTION WASTE MANAGEMENT AND DISPOSAL

01 78 00 CLOSEOUT SUBMITTALS (WEST POINT)

01 78 23 OPERATION AND MAINTENANCE DATA

01 78 24.00 10 FACILITY DATA REQUIREMENTS

01 91 00.15 10 TOTAL BUILDING COMMISSIONING

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

02 81 00 TRANSPORTATION AND DISPOSAL OF HAZARDOUS MATERIALS

02 82 00 ASBESTOS REMEDIATION

02 83 00 LEAD REMEDIATION

02 85 00 MOLD REMEDIATION

DIVISION 03 - CONCRETE

03 30 00 CAST-IN-PLACE CONCRETE

DIVISION 04 - MASONRY

04 03 00 CONSERVATION TREATMENT FOR PERIOD MASONRY

04 20 00 UNIT MASONRY

DIVISION 05 - METALS

05 12 00 STRUCTURAL STEEL

05 40 00 COLD-FORMED METAL FRAMING

05 50 13 MISCELLANEOUS METAL FABRICATIONS

05 52 00 METAL RAILINGS

PROJECT TABLE OF CONTENTS Page 1

VOLUME I

VOLUME II

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 ROUGH CARPENTRY

06 20 00 FINISH CARPENTRY

06 41 16.00 10 PLASTIC-LAMINATE-CLAD ARCHITECTURAL CABINETS

06 61 16 SOLID SURFACING FABRICATIONS

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 21 13 BOARD AND BLOCK INSULATION

07 21 16 MINERAL FIBER BLANKET INSULATION

07 27 10.00 10 BUILDING AIR BARRIER SYSTEM

07 27 19.01 SELF-ADHERING AIR BARRIERS

07 27 36 SPRAY FOAM AIR BARRIERS

07 31 26 SLATE SHINGLES

07 52 00 MODIFIED BITUMINOUS MEMBRANE ROOFING

07 62 13 COPPER SHEET METAL FLASHING AND TRIM

07 84 00 FIRESTOPPING

07 92 00 JOINT SEALANTS

DIVISION 08 - OPENINGS

08 11 13 STEEL DOORS AND FRAMES

08 14 00 WOOD DOORS

08 51 13 ALUMINUM WINDOWS

08 71 00 DOOR HARDWARE

08 81 00 GLAZING

08 91 00 METAL WALL LOUVERS

DIVISION 09 - FINISHES

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 65 00 RESILIENT FLOORING

09 65 66 RESILIENT ATHLETIC FLOORING

09 66 16 TERRAZZO FLOOR TILE

09 90 00 PAINTS AND COATINGS

DIVISION 10 - SPECIALTIES

10 14 00.20 INTERIOR SIGNAGE

10 21 13 TOILET COMPARTMENTS

10 26 00 WALL AND DOOR PROTECTION

10 28 13 TOILET ACCESSORIES

10 51 13 METAL LOCKERS

DIVISION 12 - FURNISHINGS

12 24 13 ROLLER WINDOW SHADES

12 48 13 ENTRANCE FLOOR MATS AND FRAMES

DIVISION 21 - FIRE SUPPRESSION

21 12 00 STANDPIPE SYSTEMS

21 13 13.00 10 WET PIPE SPRINKLER SYSTEM, FIRE PROTECTION

21 13 17.00 10 DRY PIPE SPRINKLER SYSTEM, FIRE PROTECTION

PROJECT TABLE OF CONTENTS Page 2

VOLUME III

21 30 00 FIRE PUMPS

DIVISION 22 - PLUMBING

22 00 00 PLUMBING, GENERAL PURPOSE

DIVISION 23 - HEATING, VENTILATING, AND AIR CONDITIONING (HVAC)

23 00 00 AIR SUPPLY, DISTRIBUTION, VENTILATION, AND EXHAUST SYSTEMS

23 03 00.00 20 BASIC MECHANICAL MATERIALS AND METHODS

23 05 48.19 BRACING FOR HVAC

23 05 93 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.01 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER

BUILDING CONTROL SYSTEMS

23 11 25 FACILITY GAS PIPING

23 21 23 HYDRONIC PUMPS

23 25 00 CHEMICAL TREATMENT OF WATER FOR MECHANICAL SYSTEMS

23 52 00 HEATING EQUIPMENT

23 64 10 WATER CHILLERS, VAPOR COMPRESSION TYPE

23 64 26 CHILLED AND HEATING WATER PIPING SYSTEMS

23 81 00 DECENTRALIZED UNITARY HVAC EQUIPMENT

DIVISION 25 - INTEGRATED AUTOMATION

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 10 10 ENERGY MONITORING AND CONTROL SYSTEM (EMCS) FRONT END AND

INTEGRATION

DIVISION 26 - ELECTRICAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 28 01.00 10 COORDINATED POWER SYSTEM PROTECTION

26 29 23 VARIABLE FREQUENCY DRIVE SYSTEMS UNDER 600 VOLTS

26 32 14.00 10 DIESEL-GENERATOR SET, STATIONARY 15-300 KW, STANDBY

APPLICATIONS

26 36 00.00 10 AUTOMATIC TRANSFER SWITCH AND BY-PASS/ISOLATION SWITCH

26 41 00 LIGHTNING PROTECTION SYSTEM

26 51 00 INTERIOR LIGHTING

26 56 00 EXTERIOR LIGHTING

DIVISION 27 - COMMUNICATIONS

27 05 14.00 10 CABLE TELEVISION PREMISES DISTRIBUTION SYSTEM

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

27 81 15 EMERGENCY RESPONDER RADIO COMMUNICATIONS SYSTEM (ERRCS)

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 31 76 INTERIOR FIRE ALARM AND MASS NOTIFICATION SYSTEM

DIVISION 31 - EARTHWORK

PROJECT TABLE OF CONTENTS Page 3

VOLUME IV

31 00 00 EARTHWORK

31 05 19 GEOTEXTILE

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 11 23 AGGREGATE BASE COURSES

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 92 19 SEEDING

32 93 00 EXTERIOR PLANTS

DIVISION 33 - UTILITIES

33 01 30.72 RELINING SEWERS

33 11 00 WATER UTILITY DISTRIBUTION PIPING

33 11 23 NATURAL GAS AND LIQUID PETROLEUM PIPING

33 40 00 STORM DRAINAGE UTILITIES

33 61 13.13 PREFABRICATED UNDERGROUND HYDRONIC ENERGY 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

APPENDIX A - CYBERSECURITY CONTROLS LIST

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 4-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. Army: Control System Cybersecurity Center of Expertise, Huntsville Engineering and Support Center.

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 are available online at the DoD Cyber Exchange website at https://public.cyber.mil/stigs/ .

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.

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 the basic designation only.

SECTION 25 05 11.01 Page 1

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

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

NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY (NIST)

NIST FIPS 201-2 (2013) Personal Identity Verification (PIV) of Federal Employees and Contractors

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

1.4.3 User Account Support Levels

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

SECTION 25 05 11.01 Page 2

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 (Temperature Sensor Modules as defined in Section 23 09 23.01 LONWORKS DIRECT DIGITAL

CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS).

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.

Examples of Remote User Interfaces include web browsers and Local Display Panels as defined in Section 23 09 23.01 LONWORKS DIRECT DIGITAL CONTROL

FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS.

SECTION 25 05 11.01 Page 3

1.4.4.4 Usage and Applicability

As of 100 percent Design, no computers are included within the facility on this node of the EMCS network. All requirements related to the examples provided in this section are not applicable.

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 the control system accreditation is:

Name: Dan Bradford Title: CIO/G6 Organization: Army Materiel Command

The West Point POC for control systems is:

Name: Farshid Rahman Title: Project Manager Organization: Installation Management Command, Engineering Service Division, Directorate of Public Works, USAG West Point E-mail: farshid.s.rahman.civ@mail.mil

The change management process for existing control systems that will be

SECTION 25 05 11.01 Page 4 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 Current ATO Status

The EMCS, which includes the Building Management System (BMS), holds an ATO that expires in August 2020. West Point is currently pursuing an updated ATO, and reaccreditation should be completed by August 2020.

These systems are integrated with the USMA Niagara and Tridium infrastructure.

The Advanced Metering Infrastructure (AMI) also falls under the EMCS ATO.

Metering is usually supported during design and construction only with the addition of DPW-specified metering equipment, with final networking accomplished by DPW and NEC personnel. Additional information can be found in the Division 26 ELECTRICAL specifications.

1.5.4 Categorization and Controls

Step 1 of the Risk Management Framework process is to categorize the information and control system according to potential impact of loss. For each information type and control system under consideration, the three FISMA-defined security objectives confidentiality, integrity, and availability (C-I-A) are associated with one of three levels of potential impact should there be a breach of security. For each security objective, the levels of potential impact are Low, Medium, or High. It is important to remember that for an ICS, availability is generally the greatest concern.

The proposed security categorization (C-I-A levels) for this system is Low-Low-Low or L-L-L.

1.6 SUBMITTALS

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

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Reference the Change Management Process established during the current ATO process for the EMCS mentioned above. Coordinate with the USAG West Point POC listed above.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Multiple IP Connection Device Request; G, RO

Contractor Computer Cybersecurity Compliance Statements; G, RO

Contractor Temporary Network Cybersecurity Compliance Statements; G, RO

SD-02 Shop Drawings

User Interface Banner Schedule; G, RO

Network Communication Report; G, RO

Cybersecurity Riser Diagram; G, RO

SECTION 25 05 11.01 Page 5

Control System Inventory Report; G, RO

SD-03 Product Data

Control System Cybersecurity Documentation; G, RO

SD-07 Certificates

Software Licenses; G, RO

SD-11 Closeout Submittals

Password Summary Report; G, RO

Software Recovery and Reconstitution Images; G, RO

Device Audit Record Upload Software; G, RO

1.7 CYBERSECURITY DOCUMENTATION

1.7.1 Cybersecurity Interconnection Schedule

{For Reference Only: This subpart (and its subparts) relates to CA-3(b), CCI-00258.}

Provide a completed Cybersecurity Interconnection Schedule documenting connections between the installed system and other systems. Provide the following information for each device communicating between systems:

Device Identifier, Device Description, Transport layer Protocol, Network Address, Port (if applicable), MAC (Layer 2) address (if applicable), Media, Application Protocol, Service (if applicable), Descriptive Purpose of communication. 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 Cybersecurity Interconnection Schedule as an editable Microsoft Excel file (a template Cybersecurity Interconnection Schedule in Excel format is available at https://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ forms-graphics-tables ).

1.7.2 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

SECTION 25 05 11.01 Page 6 file.

1.7.3 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 https://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, provide the Control System Inventory Report as an editable Microsoft Excel file.

1.7.4 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.7.5 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.7.6 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.7.6.1 Software Applications

For all software applications running on computers provide:

SECTION 25 05 11.01 Page 7

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 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.7.6.2 For EMCS Control System Devices

1.7.6.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}.

SECTION 25 05 11.01 Page 8

1.7.6.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}.

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

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

SECTION 25 05 11.01 Page 9 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 higher.

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

1.9 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 and as noted in UFC 4-010-06 , meet the following requirement throughout the construction process.

1.9.1 Contractor Computer Equipment

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

1.9.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.9.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.9.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.9.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 https://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ forms-graphics-tables .

Each Statement must be signed by a cybersecurity representative for the

SECTION 25 05 11.01 Page 10 relevant company. Subcontractors of the Prime Contract Holder are also subject to these requirements during the execution of this Project.

1.9.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:

1.9.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.9.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.9.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.9.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.9.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 https://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.

Subcontractors of the Prime Contract Holder are also subject to these requirements during the execution of this Project.

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

SECTION 25 05 11.01 Page 11

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.

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 FULLY 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 login attempts occur within 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.

SECTION 25 05 11.01 Page 12

a. It must lock the user account when three unsuccessful logon.

(1) Attempts occur within a 15 minute interval unless a life safety issue will occur.

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

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 contrast 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 Interface Schedule Format (with sample entries)

User Interface Description

User Interface Location

Type of User Interface

Banner Implementation

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

SECTION 25 05 11.01 Page 13

User Interface Schedule Format (with sample entries)

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.

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

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.

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

SECTION 25 05 11.01 Page 14 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. 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.

SECTION 25 05 11.01 Page 15

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.

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.

SECTION 25 05 11.01 Page 16

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

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.

SECTION 25 05 11.01 Page 17

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 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 non-secure 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 accepting and electronically verify Personal Identity Verification (PIV) credentials.

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 requirements:

a. Minimum password length of twelve (12) characters.

b. Password must contain at least one uppercase character.

c. Password must contain at least one lowercase character.

d. Password must contain at least one numeric character.

e. Password must contain at least one special character.

f. Password must have a minimum lifetime of 24 hours.

g. Password must have a maximum lifetime of 60 days. When passwords expire, prompt users to change passwords. Do not lock accounts due to expired passwords.

h. Password must differ from previous five passwords, where differ is defined as changing at least 50 percent of the characters.

i. Passwords must be cryptographically protected during storage and transmission.

j. Verify password rules with the System Owner and ISSM responsible for the system for…