Volume3_DTRA_Admin_Bldg_RTA_Specifications.pdf

Solicitation No. W912PP21R0009

Date: January 2021

U.S. ARMY CORPS OF ENGINEERS

DTRA Albuquerque Administrative Office Building

Kirtland AFB New Mexico

RTA

Volume 3—Specifications Division 25

DTRA ABQ Administrative Office Building Solicitation No. W912PP21R0009 Kirtland AFB, New Mexico RTA

PROJECT TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

00 10 00 SOLICITATION, OFFER, AND AWARD, SF 1442; PROPOSAL

SCHEDULE, CORPORATE, PARTNERSHIP, JOINT VENTURE CERTIFICATES

00 20 00 INSTRUCTIONS TO OFFERORS

00 21 00 INSTRUCTIONS

00 22 16 00 45 00 00 50 00

SUPPLEMENTARY INSTRUCTIONS

REPRESENTATIONS AND CERTIFICATIONS

CONTRACTING FORMS AND SUPPLEMENTS - Wage Determination

00 70 00 CONDITIONS OF THE CONTRACT

DIVISION 01 - GENERAL REQUIREMENTS

01 01 01 SPECIAL CONTRACT REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 20 00 INTERFACE WITH OTHER WORK

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 35 53.00 10 SECURITY PROCEDURES FOR SECURE AREAS

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 54 00 SECURITY

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 58 00 PROJECT IDENTIFICATION

01 62 35 RECYCLED / RECOVERED MATERIALS

01 72 00 AS-BUILT DRAWINGS

01 72 80 TRANSFER AND ACCEPTANCE OF MILITARY REAL PROPERTY

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

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

DIVISION 03 - CONCRETE

03 30 00 CAST-IN-PLACE CONCRETE

03 45 00 PRECAST ARCHITECTURAL CONCRETE

DIVISION 04 - MASONRY

04 20 00 UNIT MASONRY

DIVISION 05 - METALS

05 05 23.16 STRUCTURAL WELDING

05 12 00 STRUCTURAL STEEL

PROJECT TABLE OF CONTENTS Page 1

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

05 72 00 DECORATIVE METAL SPECIALTIES

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 ROUGH CARPENTRY

06 41 16.00 10 PLASTIC-LAMINATE-CLAD ARCHITECTURAL CABINETS

06 61 16 SOLID SURFACING FABRICATIONS

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

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

07 14 00 FLUID-APPLIED WATERPROOFING

07 21 13 BOARD AND BLOCK INSULATION

07 21 16 MINERAL FIBER BLANKET INSULATION

07 22 00 ROOF AND DECK INSULATION

07 27 10.00 10 BUILDING AIR BARRIER SYSTEM

07 27 19.01 SELF-ADHERING AIR BARRIERS

07 27 26 FLUID-APPLIED MEMBRANE AIR BARRIERS

07 42 13.19 INSULATED CORE METAL WALL PANELS

07 54 23 THERMOPLASTIC POLYOLEFIN (TPO) ROOFING

07 60 00 FLASHING AND SHEET METAL

07 81 00 SPRAY-APPLIED FIREPROOFING

07 84 00 FIRESTOPPING

07 92 00 JOINT SEALANTS

DIVISION 08 - OPENINGS

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 32 13 ALUMINUM SLIDING GLASS DOORS

08 34 01 FORCED ENTRY RESISTANT COMPONENTS

08 34 73 SOUND CONTROL DOOR ASSEMBLIES

08 41 13 ALUMINUM-FRAMED ENTRANCES AND STOREFRONTS

08 44 00 CURTAIN WALL AND GLAZED ASSEMBLIES

08 71 00 DOOR HARDWARE

08 81 00 GLAZING

08 91 00 METAL WALL LOUVERS

DIVISION 09 - FINISHES

09 22 00 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 29 00 GYPSUM BOARD

09 30 10 CERAMIC TILING

09 51 00 ACOUSTICAL CEILINGS

09 62 38 STATIC-CONTROL FLOORING

09 65 00 RESILIENT FLOORING

09 66 23 RESINOUS MATRIX TERRAZZO FLOORING

09 68 00 CARPETING

09 90 00 PAINTS AND COATINGS

PROJECT TABLE OF CONTENTS Page 2

DIVISION 10 - SPECIALTIES

10 11 00 VISUAL DISPLAY UNITS

10 14 00.10 EXTERIOR SIGNAGE

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

10 56 13 STEEL SHELVING

DIVISION 12 - FURNISHINGS

12 24 13 ROLLER WINDOW SHADES

12 48 13 ENTRANCE FLOOR MATS AND FRAMES

DIVISION 14 - CONVEYING EQUIPMENT

14 21 23 ELECTRIC TRACTION PASSENGER ELEVATORS

DIVISION 21 - FIRE SUPPRESSION

21 13 13.00 10 WET PIPE SPRINKLER SYSTEM, FIRE PROTECTION

DIVISION 22 - PLUMBING

22 00 00 PLUMBING, GENERAL PURPOSE

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

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

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

23 05 15 COMMON PIPING FOR HVAC

23 05 48.19 SEISMIC AND NON-SEISMIC 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.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING

CONTROL SYSTEMS

23 11 25 FACILITY GAS PIPING

23 21 23 HYDRONIC PUMPS

23 23 00 REFRIGERANT PIPING

23 25 00 CHEMICAL TREATMENT OF WATER FOR MECHANICAL SYSTEMS

23 52 46.00 20 LOW PRESSURE WATER HEATING BOILERS (OVER 800,000 BTU/HR

OUTPUT)

23 64 10 WATER CHILLERS, VAPOR COMPRESSION TYPE

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

23 81 00 UNITARY AIR CONDITIONING EQUIPMENT

DIVISION 25 - INTEGRATED AUTOMATION

25 05 11.21 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS FIRE

AND LIFE SAFETY INCLUDING MASS NOTIFICATION SYSTEM

25 05 11.23 01 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS

UTILITY MONITORING CONTROL SYSTEM (UMCS) TO INCLUDE HVAC

25 05 11.26 01 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS

UTILITY CONTROL SYSTEMS INCLUDING ELECTRICAL TRANSMISSION

AND DISTRIBUTION AND UNINTERRUPTIBLE POWER SUPPLY (UPS)

PROJECT TABLE OF CONTENTS Page 3

25 05 11.26 02 CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS

BUILDING CONTROL SYSTEMS INCLUDING ELECTRICAL, LIGHTING,

IRRIGATION CONTROL SYSTEM, AND ELEVATOR CONTROLS

DIVISION 26 - ELECTRICAL

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

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 24 13 SWITCHBOARDS

26 28 01.00 10 COORDINATED POWER SYSTEM PROTECTION

26 29 23 VARIABLE FREQUENCY DRIVE SYSTEMS UNDER 600 VOLTS

26 31 00 SOLAR PHOTOVOLTAIC (PV) COMPONENTS

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

APPLICATIONS

26 33 53 STATIC UNINTERRUPTIBLE POWER SUPPLY (UPS)

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 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 08 10 ELECTRONIC SECURITY SYSTEM ACCEPTANCE TESTING

28 10 05 ELECTRONIC SECURITY SYSTEMS (ESS)

28 31 76 INTERIOR FIRE ALARM AND MASS NOTIFICATION SYSTEM

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 05 19 GEOTEXTILE

31 11 00 CLEARING AND GRUBBING

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 01 19 FIELD MOLDED SEALANTS FOR SEALING JOINTS IN RIGID

PAVEMENTS

32 05 33 LANDSCAPE ESTABLISHMENT

32 11 23 AGGREGATE BASE COURSES

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

32 13 13.06 PORTLAND CEMENT CONCRETE PAVEMENT FOR ROADS AND SITE

FACILITIES

32 16 19 CONCRETE CURBS, GUTTERS AND SIDEWALKS

32 17 23 PAVEMENT MARKINGS

32 31 13 CHAIN LINK FENCES AND GATES

32 84 24 IRRIGATION SPRINKLER SYSTEMS

32 93 00 EXTERIOR PLANTS

DIVISION 33 - UTILITIES

33 11 00 WATER UTILITY DISTRIBUTION PIPING

33 11 23 NATURAL GAS AND LIQUID PETROLEUM PIPING

33 30 00 SANITARY SEWERAGE

33 40 00 STORM DRAINAGE UTILITIES

33 46 13 FOUNDATION DRAINAGE SYSTEM

33 71 01 OVERHEAD TRANSMISSION AND DISTRIBUTION

PROJECT TABLE OF CONTENTS Page 4

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

33 82 00 TELECOMMUNICATIONS OUTSIDE PLANT (OSP)

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 5

THIS PAGE INTENTIONALLY LEFT BLANK

SECTION 25 05 11.21

CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS FIRE AND LIFE SAFETY

INCLUDING MASS NOTIFICATION SYSTEM

PART 1 GENERAL

This section refers to Security Requirements Guide (SRGs) and Security Technical Implementation Guide (STIGs). STIGs and SRGs are available online at the Information Assurance Support Environment (IASE) website at http://iase.disa.mil/stigs/Pages/index.aspx . Not all control system components have applicable STIGs or SRGs.

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: Fire and Life Safety to include Mass Notification System .

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.

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

1.4 DEFINITIONS

1.4.1 Computer

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

SECTION 25 05 11.21 Page 1

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:

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

SECTION 25 05 11.21 Page 2

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.

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 wireless communication, the Wireless Communication Request submittal must be approved prior to control system device selection and integration.

b. If requesting permission for alternate account lock permissions, the Device Account Lock Exception Request must be approved prior to control system device selection and integration.

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

d. Wireless testing may be required as part of the control system testing. See requirements for the Wireless Communication Test Report submittal.

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

SECTION 25 05 11.21 Page 3

f. Cybersecurity Interconnection Schedule must be coordinated with other work that will be interconnected to, and interconnections must be approved by the Government before relying on them for system functionality.

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

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

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

j. Contractor Computer Cybersecurity Compliance Statements for each contractor using contractor owned computers.

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. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance with Section 01 33 29 SUSTAINABILITY REPORTING.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Wireless Communication Request ; G

Device Account Lock Exception Request ; G

Multiple IP Connection Device 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

Cybersecurity Interconnection Schedule ; G

SD-03 Product Data

Control System Cybersecurity Documentation ; G

SD-06 Test Reports

Wireless Communication Test Report ; G

SECTION 25 05 11.21 Page 4

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

1.7 QUALITY CONTROL

1.7.1 Cybersecurity Representative

Provide a Cybersecurity Representative as the key person to implement and manage the cybersecurity related control systems of the project. This individual must have a minimum of two years of cybersecurity control systems experience, including two projects of similar size and complexity.

Submit the Cybersecurity Representative's certification of qualifications no later than 60 calendar days after Notice to Proceed. Submit one hard copy and an electronic copy.

1.7.1.1 Duties

The Cybersecurity Representative must lead and oversee the cybersecurity control systems work specified herein and be the primary point of contact for the Government regarding the cybersecurity work.

1.7.1.2 Qualifications

The individual must have a minimum of 2 years with Risk Management Framework implementation experience and experience with Facility Related Control System cybersecurity implementation such as a control system related training or certification.

1.7.2 Cybersecurity Kickoff Meeting

Within 60 calendar days after contract award, the Cybersecurity Representative must schedule a Cybersecurity Kickoff Meeting with the Contracting Officer, system owner, system program manager, and Information System Security Manager (ISSM). The meeting will be located at a specific time and place to be determined by the Contracting Officer.

1.8 CYBERSECURITY DOCUMENTATION

1.8.1 Cybersecurity Interconnection Schedule

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. For communication with other authorized systems also provide the Foreign Destination and POC for Destination. If other control system Sections used on this project include submittals documenting this

SECTION 25 05 11.21 Page 5 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 http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/forms-graphics-tables .)

1.8.2 Network Communication Report

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.3 Control System Inventory Report

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

1.8.4 Software Recovery and Reconstitution Images

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.

1.8.5 Cybersecurity Riser Diagram

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.6 Control System Cybersecurity Documentation

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

SECTION 25 05 11.21 Page 6

1.8.6.1 Software Applications

For all software applications running on computers provide:

a. Administrator documentation that describes secure configuration of the software.

b. Administrator documentation that describes secure installation of the software.

c. Administrator documentation that describes secure operation of the software.

d. Administrator documentation that describes effective use and maintenance of security functions or mechanisms for the software.

e. Administrator documentation that describes known vulnerabilities regarding configuration and use of administrative (i.e. privileged) functions for the software.

f. User documentation that describes user-accessible security functions or mechanisms in the software and how to effectively use those security functions or mechanisms.

g. User documentation that describes methods for user interaction which enables individuals to use the software in a more secure manner.

h. User documentation that describes user responsibilities in maintaining the security of the software.

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

b. Documentation that describes secure installation of the device.

c. Documentation that describes secure operation of the device.

d. Documentation that describes effective use and maintenance of security functions or mechanisms for the device.

e. Documentation that describes known vulnerabilities regarding configuration and use of administrative (i.e. privileged) functions for the device.

f. Documentation that describes user-accessible security functions or mechanisms in the device and how to effectively use those security functions or mechanisms.

g. Documentation that describes methods for user interaction which enables individuals to use the device in a more secure manner.

h. Documentation that describes user responsibilities in maintaining the security of the device.

SECTION 25 05 11.21 Page 7

1.9 SOFTWARE UPDATE LICENSING

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

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

1.10 CYBERSECURITY DURING CONSTRUCTION

In addition to the control system cybersecurity requirements indicated in this section, 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.

SECTION 25 05 11.21 Page 8

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:

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.

SECTION 25 05 11.21 Page 9

PART 3 EXECUTION

3.1 ACCESS CONTROL REQUIREMENTS

3.1.1 User Accounts

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.

Implement a warning banner on terminal interfaces that conforms to DoD warning banner guidelines. Configure each component of the product to operate using the principle of least privilege. This includes operating communications, and energy delivery system services.

Provide user accounts with configurable access and permissions associated with one or more organizationally defined user role(s), where roles are used. Provide a system administration mechanism for changing user(s') role (e.g., group) associations.

Configure the product such that when a session or interprocess communication is initiated from a less privileged application, access shall be limited and enforced at the more critical side. Provide a method for protecting against unauthorized privilege escalation.

Document options for defining access and security permissions, user accounts, and applications with associated roles. Configure these options as specified.

Prevent unauthorized changes to the Basic Input/Output System (BIOS) and other firmware and document if not feasible, provide mitigation recommendations.

Verify and provide documentation for the procured product, attesting that unauthorized logging devices are not installed (e.g., key loggers, cameras, and microphones).

3.1.1.1 Computers

All computers must FULLY support user accounts.

3.1.1.2 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 FULLY support user accounts.

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

3.1.2 Account Management

Document all accounts (including but not limited to, generic or default)

SECTION 25 05 11.21 Page 10 that need to be active for proper operation of the product. Change default account settings to specific settings (e.g., length, complexity, history, and configurations) provided by government representative.

Changed account information will not be published. All new account information will be provided by a protected mechanism. Remove or disable any accounts that are not needed for normal or maintenance operations of the control system. Accounts for emergency operations shall be placed in a highly secure configuration and documentation must be provided.

3.1.3 Unsuccessful Logon Attempts

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

3.1.3.1 Devices MINIMALLY Supporting Accounts

Devices which MINIMALLY support accounts must lock the user input after three unsuccessful logon attempts and must support unlocking of the user input when unlocked by an administrator.

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

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

3.1.3.3 High Availability Interfaces Exempt from Unsuccessful Logon Attempts Requirements

Contact local ISSM and System Owner/Program Manager for requirements for high availability interfaces that are exempt from unsuccessful logon attempts. Work with local ISSM and local CIO to complete the following:

Hi gh Avai l abi l i t y I nt er f aces Exempt f r om Unsuccessf ul Logon At t empt s Requi r ement s

User I nt er f ace Location Act i on t o t ake i n l i eu of l ocki ng scr een

3.1.4 System Use Notification

Web interfaces must display a warning banner meeting the requirements of

DTM 08-060 .

SECTION 25 05 11.21 Page 11

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.4.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.5 Permitted Actions Without Identification or Authentication

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.6 Wireless Access

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

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

3.1.6.2 Non-IP Wireless Communication

When non-IP wireless communication is explicitly authorized by the

SECTION 25 05 11.21 Page 12

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.1.6.3 Wireless Communication Request

Provide a report documenting the proposed use of wireless communication prior to beginning construction using the Wireless Communication Request Schedule at http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/forms-graphics-tables .

For each device proposed to use wireless communication show: the device identifier, a description of the device, the location of the device, the device identifiers of other devices communicating with the device, the protocol used for communication, encryption type and strength, RF Frequency, Radiated Power in dBm (decibel with a milliwatt reference), free-space range, and the expected as-installed range.

3.1.6.4 Wireless Communication Testing

As part of Performance Verification Testing (PVT), conduct testing of wireless communication for all devices indicated on the approved Wireless Communication Request as requiring testing.

To test wireless communication, test for wireless network reception at multiple points along the wireless test boundary in the vicinity of the wireless device, and record whether a network connection can be established at each point. The wireless test boundary is the building exterior walls. If wireless testing is required, provide a Wireless Communication Test Report documenting the testing points and results at each point for each wireless device.

3.2 CYBERSECURITY AUDITING

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

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

c. Privileged activities or other system level access

SECTION 25 05 11.21 Page 13

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

SECTION 25 05 11.21 Page 14

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

g. All kernel module load, unload, and restart

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

a. For devices that have STIG/SRGs related to audit storage capacity 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 audit records in conformance with applicable STIG/SRG's.

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.

Contact local ISSM and System Owner/Program Manager for device audit record upload software requirements. 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

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

SECTION 25 05 11.21 Page 15

3.2.4 Time Stamps

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 Control System Devices

Time stamp requirements for Control Systems are as indicated in the Control System specifications. 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 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 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.

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

SECTION 25 05 11.21 Page 16 or required for operation of the control system.

3.4 SAFE MODE AND FAIL SAFE OPERATION

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

3.5 IDENTIFICATION AND AUTHENTICATION

3.5.1 User Identification and Authentication

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 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 or inheriting identification and authentication from the operating system.

3.5.2 Authenticator Management

3.5.2.1 Authentication Type

3.5.2.1.1 Default Requirements for Control System Devices

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

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 12 characters

b. Password must contain at least one uppercase character.

c. Password must contain at least one lowercase character.

SECTION 25 05 11.21 Page 17

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 no t 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.

3.5.2.2.2 Passwords for Non-Computer Devices FULLY Supporting Accounts

All non-computer devices FULLY supporting accounts and 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 maximum lifetime of sixty (60) days. When passwords expire, prompt users to change passwords. Do no t lock accounts due to expired passwords.

g. Password must differ from previous five (5) passwords, where differ is defined as changing at least fifty percent of the characters.

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

3.5.2.2.3 Passwords for Web Interfaces

Passwords for connecting to a web interface supporting password-based authentication must enforce the following requirements:

a. Minimum password length of 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 maximum lifetime of 60 days. When passwords expire, prompt users to change passwords. Do no t lock accounts due to expired passwords.

SECTION 25 05 11.21 Page 18

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

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

3.5.2.2.4 Passwords for Devices Minimally Supporting Accounts

Devices minimally supporting accounts must support passwords with a minimum length of four characters.

3.5.2.2.5 Password Configuration and Reporting

For all devices with a password, change the password from the default password. Coordinate selection of passwords with ISSM. Do not use the same password for more than one device unless specifically instructed to do so. Provide a Password Summary Report documenting the password for each device and describing the procedure to change the password for each device.

Do not provide the Password Summary Report in electronic format. Provide two hard copies of the Password Summary Report, each copy in its own sealed envelope.

3.5.2.3 Hardware Token-Based Authentication Requirements

Devices supporting hardware token-based authentication must use Personal Identity Verification (PIV) credentials for the hardware token.

3.5.3 Authenticator Feedback

Devices must never show authentication information, including passwords, on a display. Devices that momentarily display a character as it is entered, and then obscure the character, are acceptable. For devices that have STIGs or SRGs related to obscuring of authenticator feedback, comply with the requirements of those STIGS/SRGs.

3.5.4 Device Identification and Authentication

All computers must use IEEE 802.1x for authentication to the network. All web servers running on computers must use HTTPS and must implement HTTPS using web server certificates obtained from ISSM.

3.5.4.1 Default Requirements for Control System Devices

For control system devices where Device Identification and Authentication requirements are not otherwise indicated in this Section: Devices using Ethernet must support IEEE 802.1x . Devices using HTTP as a control protocol must use HTTPS using a web server certificate obtained from ISSM.

3.5.5 Cryptographic Module Authentication

For devices that have STIG/SRGs related to cryptographic module authentication, comply with the requirements of those STIG/SRGs.

3.6 EMERGENCY POWER

Emergency power is specified in the control system and equipment

SECTION 25 05 11.21 Page 19 specifications.

3.7 DURABILITY TO VULNERABILITY SCANNING

All IP devices must be scannable, such that the device can be scanned by industry standard IP network scanning utilities without harm to the device, application, or functionality.

Computers must respond to scans from Assured Compliance Assessment Solution (ACAS) by responding with a valid credentialed scan. For control system devices other than computers:

3.7.1 Default…