W912QR25R0052_Specs_Vol3-0000.pdf

Solicitation For Manned/Unmanned Tactical Vehicle Lab (MUMT), Detroit Arsenal, Detroit, MI

P2: 506474

Design-Bid-Build

Specifications - Vol 3 of 3 (Div 25-41) Certified Final Design

12 May 2025

W912QR25R0052

ARIMS: 200A

Disposition: Maintain for 15yrs after construction

W912QR25R0052_Specs_Vol3-0000

P2#: 506474 - Manned/Unmanned Tactical Vehicle Lab (MUMT) Detroit Arsenal, MI

PROJECT TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

00 80 00.00 06 04/21 SPECIAL PROVISIONS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 08/15, CHG 2: 08/21 SUMMARY OF WORK

01 32 01.00 06 07/18 PROJECT SCHEDULE

01 33 00 08/18, CHG 4: 02/21 SUBMITTAL PROCEDURES

01 33 29.00 06 11/17 SUSTAINABILITY REPORTING

01 35 26.00 06 GOVERNMENT SAFETY REQUIREMENTS

01 42 00 02/19 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.15 10 11/16, CHG 2: 08/19 RESIDENT MANAGEMENT SYSTEM CONTRACTOR

MODE (RMS CM)

01 45 04.10 06 CONTRACTOR QUALITY CONTROL

01 45 35 11/20 SPECIAL INSPECTIONS

01 46 00.00 06 04/20 TOTAL BUILDING COMMISSIONING

01 50 00 11/20, CHG 1: 08/21 TEMPORARY CONSTRUCTION FACILITIES AND

CONTROLS

01 57 19.00 06 04/20 TEMPORARY ENVIRONMENTAL CONTROLS AND

PERMITS

01 74 19 02/19, CHG 3: 11/21 CONSTRUCTION WASTE MANAGEMENT AND

DISPOSAL

01 78 23 08/15, CHG 2: 08/21 OPERATION AND MAINTENANCE DATA

DIVISION 02 - EXISTING CONDITIONS

02 41 00 05/10, CHG 2: 02/19 DEMOLITION

DIVISION 03 - CONCRETE

03 30 00 02/19, CHG 3: 11/21 CAST-IN-PLACE CONCRETE

03 45 00 05/16, CHG 2: 11/21 PRECAST ARCHITECTURAL CONCRETE

DIVISION 04 - MASONRY

04 20 00 11/15, CHG 2: 05/19 UNIT MASONRY

DIVISION 05 - METALS

05 05 23.13 10 08/18 ULTRASONIC INSPECTION OF WELDMENTS

05 05 23.16 08/18 STRUCTURAL WELDING

05 12 00 08/18, CHG 2: 05/21 STRUCTURAL STEEL

05 12 13 07/24 ARCHITECTURALLY EXPOSED STRUCTURAL

STEEL

05 21 00 05/15, CHG 1: 08/18 STEEL JOIST FRAMING

05 30 00 05/15, CHG 2: 08/18 STEEL DECKS

05 40 00 05/15, CHG 1: 08/18 COLD-FORMED METAL FRAMING

05 50 13 05/17, CHG 1: 08/18 MISCELLANEOUS METAL FABRICATIONS

05 51 33 02/16, CHG 2: 02/18 METAL LADDERS

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 08/16, CHG 2: 11/18 ROUGH CARPENTRY

06 41 16.00 10 08/10, CHG 1: 11/18 PLASTIC-LAMINATE-CLAD ARCHITECTURAL

CABINETS

06 61 16 08/20 SOLID SURFACING FABRICATIONS

PROJECT TABLE OF CONTENTS Page 1 Certified Final Submittal

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 05 23 08/19 PRESSURE TESTING AN AIR BARRIER SYSTEM

FOR AIR TIGHTNESS

07 21 13 02/16, CHG 2: 08/20 BOARD AND BLOCK INSULATION

07 22 00 02/16, CHG 3: 11/18 ROOF AND DECK INSULATION

07 27 10.00 10 08/19, CHG 1: 02/20 BUILDING AIR BARRIER SYSTEM

07 27 19.01 05/17, CHG 2: 08/20 SELF-ADHERING AIR BARRIERS

07 27 36 05/17, CHG 2: 08/20 SPRAY FOAM AIR BARRIERS

07 42 13 05/11, CHG 2: 02/18 METAL WALL PANELS

07 54 19 THERMOPLASTIC POLYOLEFIN (TPO) ROOFING

07 60 00 05/17, CHG 2: 11/18 FLASHING AND SHEET METAL

07 81 00 02/11 SPRAY-APPLIED FIREPROOFING

07 84 00 05/10, CHG 1: 08/13 FIRESTOPPING

07 92 00 08/16, CHG 3: 11/18 JOINT SEALANTS

DIVISION 08 - OPENINGS

08 11 13 08/20 STEEL DOORS AND FRAMES

08 14 00 08/16, CHG 1: 08/18 WOOD DOORS

08 31 00 05/17, CHG 1: 08/18 ACCESS DOORS AND PANELS

08 33 23 08/20 OVERHEAD COILING DOORS

08 34 73 11/19, CHG 1: 02/21 SOUND CONTROL DOOR ASSEMBLIES

08 51 13 05/19 ALUMINUM WINDOWS

08 60 45 08/20 TRANSLUCENT PANELS

08 71 00 02/16, CHG 3: 08/20 DOOR HARDWARE

08 81 00 05/19 GLAZING

08 91 00 08/20 METAL WALL LOUVERS

DIVISION 09 - FINISHES

09 22 00 02/10, CHG 2: 08/18 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 29 00 08/16, CHG 4: 02/20 GYPSUM BOARD

09 30 10 08/20 CERAMIC, QUARRY, AND GLASS TILING

09 51 00 08/20 ACOUSTICAL CEILINGS

09 62 38 08/17, CHG 1: 08/18 STATIC-CONTROL FLOORING

09 65 00 08/10, CHG 3: 08/18 RESILIENT FLOORING

09 67 23.15 02/21 FUEL RESISTIVE RESINOUS FLOORING,

3-COAT SYSTEM

09 68 00 11/17, CHG 2: 08/20 CARPETING

09 84 20 08/16, CHG 1: 08/18 ACOUSTICAL WALL PANELS

09 90 00 02/21 PAINTS AND COATINGS

DIVISION 10 - SPECIALTIES

10 11 00 08/20 VISUAL DISPLAY UNITS

10 14 00.20 08/20 INTERIOR SIGNAGE

10 21 13 08/20 TOILET COMPARTMENTS

10 23 10 06/24 GLAZED INTERIOR WALL AND DOOR

ASSEMBLIES

10 26 00 08/20 WALL AND DOOR PROTECTION

10 28 13 08/20 TOILET ACCESSORIES

10 44 16 11/19 FIRE EXTINGUISHERS

10 51 13 05/11 METAL LOCKERS

DIVISION 12 - FURNISHINGS

12 24 13 08/20 ROLLER WINDOW SHADES

PROJECT TABLE OF CONTENTS Page 2

12 50 00.13 10 08/17, CHG 1: 11/18 FURNITURE AND FURNITURE INSTALLATION

12 59 00 08/17, CHG 1: 08/18 SYSTEMS FURNITURE

DIVISION 21 - FIRE SUPPRESSION

21 13 13 08/20 WET PIPE SPRINKLER SYSTEMS, FIRE

PROTECTION

21 30 00 04/08, CHG 1: 08/13 FIRE PUMPS

DIVISION 22 - PLUMBING

22 00 00 11/15, CHG 4: 05/21 PLUMBING, GENERAL PURPOSE

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

23 05 93.00 06 08/16 TESTING, ADJUSTING, AND BALANCING

(TAB) OF HVAC

23 07 00 02/13, CHG 7: 05/20 THERMAL INSULATION FOR MECHANICAL

SYSTEMS

23 08 00.00 20 02/21, CHG 1: 05/21 COMMISSIONING OF MECHANICAL AND

PLUMBING SYSTEMS

23 09 00 02/19, CHG 3: 05/21 INSTRUMENTATION AND CONTROL FOR HVAC

23 09 13 11/15, CHG 2: 05/21 INSTRUMENTATION AND CONTROL DEVICES

FOR HVAC

23 09 23.02 02/19, CHG 1: 02/20 BACNET DIRECT DIGITAL CONTROL FOR HVAC

AND OTHER BUILDING CONTROL SYSTEMS

23 11 20 05/20 FACILITY GAS PIPING

23 23 00 08/21 REFRIGERANT PIPING

23 30 00 05/20 HVAC AIR DISTRIBUTION

23 35 16.17 10 05/20 MECHANICAL ENGINE EXHAUST SYSTEMS

23 81 00 05/18, CHG 1: 02/21 DECENTRALIZED UNITARY HVAC EQUIPMENT

23 81 23 11/20 COMPUTER ROOM AIR CONDITIONING UNITS

DIVISION 25 - INTEGRATED AUTOMATION

25 05 11.01 05/21 CYBERSECURITY FOR HVAC DDC SYSTEMS

25 05 11.02 05/21 CYBERSECURITY FOR FIRE & MASS

NOTIFICATION CONTROL SYSTEMS

25 05 11.03 05/21 CYBERSECURITY FOR LIGHTING CONTROL

SYSTEMS

25 08 10 05/21 UTILITY MONITORING AND CONTROL SYSTEM

TESTING

25 10 10 02/19, CHG 1: 05/21 UTILITY MONITORING AND CONTROL SYSTEM

(UMCS) FRONT END AND INTEGRATION

DIVISION 26 - ELECTRICAL

26 05 73 08/23 POWER SYSTEM STUDIES

26 08 00 11/21 APPARATUS INSPECTION AND TESTING

26 11 16 11/21 SECONDARY UNIT SUBSTATIONS

26 13 00 05/21 SF6/HIGH-FIREPOINT FLUIDS INSULATED

PAD-MOUNTED SWITCHGEAR

26 20 00 08/19, CHG 3: 11/21 INTERIOR DISTRIBUTION SYSTEM

26 24 13 08/21 SWITCHBOARDS

26 29 23 02/20, CHG 1: 05/21 ADJUSTABLE SPEED DRIVE (ASD) SYSTEMS

UNDER 600 VOLTS

26 41 00 11/13 LIGHTNING PROTECTION SYSTEM

26 51 00 05/20, CHG 2: 11/21 INTERIOR LIGHTING

PROJECT TABLE OF CONTENTS Page 3

DIVISION 27 - COMMUNICATIONS

27 10 00 08/11 BUILDING TELECOMMUNICATIONS CABLING

SYSTEM

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 31 76 08/20 INTERIOR FIRE ALARM AND MASS

NOTIFICATION SYSTEM, ADDRESSABLE

DIVISION 31 - EARTHWORK

31 00 00.00 06 07/18 EARTHWORK

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 01 19.61 11/19 SEALING OF JOINTS IN RIGID PAVEMENT

32 05 33 08/17 LANDSCAPE ESTABLISHMENT

32 11 20 08/17 BASE COURSE FOR RIGID AND SUBBASES FOR

FLEXIBLE PAVING

32 12 13 05/17 BITUMINOUS TACK AND PRIME COATS

32 12 16.16 11/20 ROAD-MIX ASPHALT PAVING

32 13 13.06 06 06/18 PORTLAND CEMENT CONCRETE PAVEMENT FOR

ROADS AND SITE FACILITIES

32 16 19 05/18 CONCRETE CURBS, GUTTERS AND SIDEWALKS

32 17 23 08/16, CHG 5: 11/18 PAVEMENT MARKINGS

32 92 19 08/17, CHG 1: 08/21 SEEDING

32 93 00 08/17, CHG 1: 08/21 EXTERIOR PLANTS

DIVISION 33 - UTILITIES

33 05 07.13 02/24 UTILITY DIRECTIONAL DRILLING

33 05 23 08/15, CHG 2: 08/16 TRENCHLESS UTILITY INSTALLATION

33 11 00 02/18 WATER UTILITY DISTRIBUTION PIPING

33 30 00 05/18 SANITARY SEWERAGE

33 40 00 11/21 STORMWATER UTILITIES

33 46 16 05/18 SUBDRAINAGE PIPING

33 71 02 08/21 UNDERGROUND ELECTRICAL DISTRIBUTION

33 82 00 04/06 TELECOMMUNICATIONS OUTSIDE PLANT (OSP)

DIVISION 41 - MATERIAL PROCESSING AND HANDLING EQUIPMENT

41 22 13.14 11/19, CHG 1: 02/21 BRIDGE CRANES, OVERHEAD ELECTRIC, TOP

RUNNING

41 24 26 05/20, CHG 1: 11/20 HYDRAULIC POWER SYSTEMS

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 4

SECTION 25 05 11.01

CYBERSECURITY FOR HVAC DDC SYSTEMS

05/21

PART 1 GENERAL

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

This Section refers to Security Requirements Guide (SRGs) and Security Technical Implementation Guide (STIGs). STIGs and SRGs are available online at the Information Assurance Support Environment (IASE) website at https://public.cyber.mil/stigs/downloads/ and an SRG/STIG Applicability Guide and Collection Tool is available at https://public.cyber.mil/stigs/SCAP/ . Not all control system components have applicable STIGs or SRGs. Typically this requirement will apply to BCS workstations and servers as part of the whole solution, or supported systems where STIGs can be applied.

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: HVAC DDC Systems.

1.2 RELATED REQUIREMENTS

This section does not contain sufficient requirements to procure a control system and must be used in conjunction with other Sections which specify control systems. This Section adds cybersecurity requirements to the control systems specified in other Sections, and as these requirements are conditioned on the control system being provided, there may be requirements in this Section that will not apply to this project. 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.

In cases where a requirement is specified in both this Section and in another Section, the more stringent requirement must be met. In cases where a requirement in this Section conflicts with the requirements of another Section such that both requirements cannot be met at the same time, request direction from the Contracting Officer Representative to determine which requirement applies to the project.

1.3 REFERENCES

The publications listed below form a part of this specification to the

SECTION 25 05 11.01 Page 1 extent referenced. The publications are referred to within the text by the basic designation only.

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE 135 (2020; Interpretation 1-8 2021; Errata 1-2 2021; Addenda CD 2021; Addenda BV-CE 2022;

Interpretation 9-12 2022; Interpretation 13-17 2023; Addenda BV-CF 2023; Errata 3 2023) BACnet—A Data Communication Protocol for Building Automation and Control Networks

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

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

U.S. DEPARTMENT OF DEFENSE (DOD)

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 Administrator Account

An administrator account is an account with full permissions to a device, application, or operating system, including the ability to create and modify other user accounts.

Note that the operating system Administrator Account may be different than Administrator Accounts for applications hosted on that operating system.

Also, most controllers will not have any support for accounts and will therefore not have an 'Aministrator Account'.

1.4.2 Computer

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 Operating System, where Android is considered separate from Linux

e. a device running a version of Apple iOS

Unless otherwise indicated or clear from context use of the word "device" in this Section includes computers.

SECTION 25 05 11.01 Page 2

1.4.3 Controller

A device other than a computer or Ethernet switch.

1.4.4 Mission Space

A device or media is in mission space if physical access to the device or media is controlled by the organization served by the device. For example, a VAV box controller in a suspended ceiling is in mission space if the VAV box serves that room; an electrical switchgear in an electrical room or an AHU in a mechanical room or on a rooftop may still be considered to be in mission space if the organization (mission) served by that switchgear or AHU controls access to the electrical room, mechanical room or rooftop.

1.4.5 Network

A network is a group of two or more devices that can communicate using a network protocol. Network protocols must provide a method for addressing devices on the network; a communication method that does not provide an addressing scheme is not a networked form of communication. Devices that communicate using a method of communication that does not support device addressing are not using a network.

1.4.6 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 (unlike many IT definitions of "Network Connected") 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).

1.4.6.1 Wireless Network Connected

Any device that supports wireless network communication is network connected to a wireless network, regardless of whether the device is communicating using wireless. Unless physically disabled, devices with wireless transceivers support wireless, it is not sufficient to disable the wireless in software.

1.4.7 Network Media

The thing that provides the communication channel between the devices on a network. Typically wire, but might include wireless, fiber optic, or even power line (some network protocols allow sending network signals over power wiring).

1.4.8 User Account Support Levels

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

1.4.8.1 FULLY Supported

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

SECTION 25 05 11.01 Page 3

These devices support user-based (as opposed to role-based) authentication.

1.4.8.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 "username and password" structure). These devices typically only support role-based authentication.

Examples of devices which MINIMALLY support accounts are a) a variable frequency drive with a single account which requires a PIN for access to configuration; and b) a room lighting control touchpad interface that has a single account.

1.4.8.3 NOT Supported

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

1.4.9 Manual Local Input

Manual Local Inputs are system analog or binary inputs that are adjustable by a person but are, by intrinsic hardware design, very limited in potential capabilities. Manual Local Inputs do not have touch screens or full keyboards, but may have a few buttons or dials to allow input.

Manual Local Inputs do not have full graphic screens or dot-matrix displays, but may have simple lights (LEDs) or 7-segment displays. Manual Local Inputs do not have any sort of menu structure, each button has a single well-defined function.

Examples of Manual Local Inputs are H-O-A switches, simple thermostats, and disconnect switches.

1.4.10 Card Reader

A card reader is an input/output device whose primary function is to assist in two-factor authentication. A card reader must have an interface to read data from a card and may be able to write data to a card. A card reader may have a means (such as buttons, keypad, touchscreen, etc.) for a user to input a PIN or password, as well as a limited display.

1.4.11 User Interface

A User Interface (UI) is something other than a Manual Local Input or Card Reader that allows a person to interact with the system or device. Note that while a Card Reader is not by itself a User Interface, a User Interface may contain a Card Reader in order for it to authenticate its user. Within control systems, there are a wide range of User Interfaces.

Two important distinctions are 1) whether the user interface is Local or Remote, and 2) the effective capabilities of the User Interface to alter data, which is the "privilege" of the user interface (where effective privilege available to a specific user at a specific user interface is the combination of the greatest privilege offered by the user interface and the specific account the user is logged into).

SECTION 25 05 11.01 Page 4

1.4.11.1 Local User Interface

A Local User Interface is a user interface where the physical hardware the user interacts with (keyboard, buttons, display, etc.) is physically part of the device being affected. All of the relevant characteristics of the user interface are embodied within a single device.

Note that a Local UI may be able to access data in a different device, Local versus Remote in this context refers to the user interface itself;

the capability to access data in a different device is covered under "Full User Interface".

1.4.11.2 Remote User Interface

A Remote User Interface implements a Client/Server model where the physical hardware the user interacts with (Client) is physically distinct from the device being affected (Server). Most or all of the security and functionality characteristics of the user interface are defined by the Server, not the Client. The Client and Server communicate via a network connection. A common example of a remote user interface is a web-based interface where the browser (client) is generally on different hardware than the web server (server). A Remote UI remains a Remote UI even if the user happens to be at a Client on the same hardware as the Server. What is important is that a) the Client may be on different hardware than the Server and b) the majority of the security and functional characteristics of the interface are defined at the Server.

Note that this definition of "remote" is consistent with that generally used in the control industry but is not aligned with the NIST 800-53 definition of "Remote", which refers to "outside the system". The term "Remote" here better aligns with the NIST 800-53 definition of "Network" (remote from within the system) Access.

1.4.11.3 Types of User Interface (by capability)

User interfaces are also categorized by their capabilities as being Read Only, Limited, or Full.

1.4.11.3.1 Read-Only User Interface

A Read Only User Interface (also referred to as a View-Only User Interface) is a user interface that only allows for reading data, it does not allow (have the capability to) modify data. A Read Only User Interface may be either Local or Remote. A User Interface that is configured to be Read Only (by some other means than the interface itself, such as using configuration software on a laptop) is a Read-Only Interface. Note a Read Only User Interface may have buttons (or touch screen, etc.) allowing the user to navigate through the presentation of data.

Examples of a Read Only User Interfaces are a) a publicly viewable "energy dashboard" showing weather data and energy usage within a building and b) digital wayfinding signage.

1.4.11.3.2 Limited User Interface

A Limited User Interface is a user interface that - by design - can only alter information local to the user interface. Note that the determination of "alter" includes only direct interactions, it explicitly excludes

SECTION 25 05 11.01 Page 5 interactions that might occur as secondary effects. For example, an interface changing the flow setpoint in a pump controller is a direct interaction, the subsequent change in flow (as well as any subsequent downstream changes in valve position) are not direct interactions.

Two examples of LIMITED UIs are: a) a variable speed drive has a Limited Local User Interface which allows the user to change properties within the drive, but does not allow affecting things outside the drive; and b) a typical home WiFi Router has a Limited Remote User Interface which allows configuration of the Router, but does not allow direct interaction with other devices.

1.4.11.3.3 Full User Interface

A Full User Interface can alter information in devices outside the device with the user interface. For example, a typical Local Display Panel is a Full Local User Interface while a browser-based front end is a Full Remote User Interface.

1.4.11.3.4 View-Only User Interface

See Read-Only User Interface

1.4.11.4 Other User Interface Terminology

In addition to defining whether a user interface is a Hardware Limited, Read-Only, Limited or Full, and whether it is Local or Remote, user interfaces are classified by whether they are writable or privileged.

1.4.11.4.1 Writable User Interface

Any User Interface that is not Read-Only is Writable. (Limited User Interfaces and Full User Interfaces are both writable user interfaces (as they are capable of changing a value)).

1.4.11.4.2 Privileged User Interface

A Privileged UI is a UI that has sufficient capabilities or functionality that it requires specific cybersecurity measures to be put in place to limit its unauthorized use. Ultimately, whether a specific user interface is considered a Privileged User Interface must be determined by usage.

Unless otherwise specified, user interfaces can be determined to be privileged or not using the following:

a. Read-Only User Interfaces are not privileged user interfaces.

b. Full User Interfaces are privileged user interfaces.

c. User interfaces that allow for configuration of auditing or allows for modification or deletion of audit logs are privileged user interface.

d. User interfaces that allow for reprogramming a network connected device is a privileged user interface.

e. Except as specified above, a Limited User Interface must be determined to be privileged or not based on the specific capabilities and use case of the user interface. In general however, user interfaces that do not offer significant capabilities above and beyond those available at that location via other means (e.g. such as a disconnect switch, SECTION 25 05 11.01 Page 6 breaker, or hand-off-auto switch, or physical attack) are not privileged.

1.4.12 Wireless Network

Any network that communicates without using wires or fiber optics as the communication media. Wireless networks include: WiFi, Bluetooth, ZigBee, cellular, satellite, 900 MHz radio, 2.4 GHz, free space optical, point-to-point laser, and IR.

1.4.13 Wired Broadcast Network

Wired Broadcast Networks are any network, such as powerline carrier networks and modem (wired telephony), that use wire-based technologies where there is not a clearly defined boundary for signal propagation.

1.5 ADMINISTRATIVE REQUIREMENTS

1.5.1 Points of Contact

Coordinate with the following Points of Contact as indicated in this Section and as required. Not all projects will require coordination with all Points of Contact. When coordination is required and no Point of Contact is indicated, coordinate with The Contracting Office Representative (COR).

a. Government Computer Access Point of Contact: The Contracting Office Representative (COR)

b. Email Address Point of Contact: The Contracting Office Representative

(COR)

c. Password Point of Contact: The Contracting Office Representative (COR)

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

b. The 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.

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

d. Contractor Computer Cybersecurity Compliance Statements must be provided for each contractor using contractor owned computers.

SECTION 25 05 11.01 Page 7

1.6 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Contractor Computer Cybersecurity Compliance Statements; G

Cybersecurity Interconnection Schedule; G

SD-02 Shop Drawings

Network Communication Report; G

Cybersecurity Riser Diagram; G

SD-03 Product Data

Control System Cybersecurity Documentation; G

Software Licenses; G

SD-11 Closeout Submittals

Confidential Password Report; G

Enclosure Keys; G

Control System Inventory Report; G

1.7 QUALITY CONTROL

1.7.1 Cybersecurity Subject Matter Expert Qualifications

For the positions listed below resumes should be submitted to the Government within 14 days after notice to proceed. All certifications must be in effect prior to being hired.

These positions may serve across the contract and provide on-site support as required.

1.7.2 Cybersecurity Subject Matter Expert

The individual will oversee all work within this specification. This position requires that the individual currently meets Information Assurance Manager Level II Certification in accordance with DODD 8140 Cybersecurity Workforce Managment and DODI 8570 Information Workforce Improvement Program.

Individuals for this position should have experience securing DoD Systems and with Risk Management Framework.

SECTION 25 05 11.01 Page 8

1.8 CYBERSECURITY DOCUMENTATION

{For Government Reference Only: This subpart (and its subparts) relates to PL-7; CCI-003071}

1.8.1 Cybersecurity Interconnection Schedule

This subpart relates to CA-3(b), PL-8, SC-7(11); CCI-000258, CCI-002402.

Provide a completed Cybersecurity Interconnection Schedule documenting network connections between the installed system and other systems.

Provide the following information for each device directly 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 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/ufgs-25-05-11

1.8.2 Network Communication Report

This subpart (and its subparts) relates to CA-9; CCI-002104, CCI-002105, and also the submittal requirements including CM-7(3), CCI-000388.

Provide a network communication report. For each networked device, document the communication characteristics of the device including communication protocols, services used, encryption employed, and a general description of what information is communicated over the network. For each device using IP, document all TCP and UDP ports used. For non-IP communications, document communication protocol and media 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

This subpart (and its subparts) relates to CM-8(a), SI-17, IA-3;

CCI-000389, CCI-000392, CCI-000398.

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/ufgs-25-05-11 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.

SECTION 25 05 11.01 Page 9

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 Cybersecurity Riser Diagram

This subpart (and its subparts) relates to PL-2(a), PL-8; CCI-003051, CCI-003075.

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

1.8.5 Control System Cybersecurity Documentation

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

CCI-003124, CCI-003125, CCI-003126, CCI-003127.

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

1.8.5.1 For HVAC Control System Devices

1.8.5.1.1 HVAC Control System Devices FULLY Supporting User Accounts

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

a. Documentation that describes secure configuration of the device {For Government Reference Only: relates to CCI-003124}

b. Documentation that describes secure operation of the device {For Government Reference Only: relates to CCI-003126}

c. Documentation that describes effective use and maintenance of security functions or mechanisms for the device {For Government Reference Only:

relates to CCI-003127}

1.8.5.1.2 All Other HVAC Control System Devices

For all HVAC 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 Government 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 Government Reference Only: relates to CCI-003127}

1.8.5.2 Default Requirements for Control System Devices

For control system devices where Control System Cybersecurity Documentation requirements are not otherwise indicated in this Section, SECTION 25 05 11.01 Page 10 provide:

a. Documentation that describes secure configuration of the device {For Government Reference Only: relates to CCI-003124}

b. Documentation that describes secure installation of the device {For Government Reference Only: relates to CCI-003125}

c. Documentation that describes secure operation of the device {For Government Reference Only: relates to CCI-003126}

d. Documentation that describes effective use and maintenance of security functions or mechanisms for the device {For Government Reference Only:

relates to CCI-003127}

1.9 SOFTWARE LICENSING

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

For all software provided that has not already been licensed to the government or project site, provide a license to the project sitefor a period of no less than 5 years, and the license must also include the following software updates:

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

This subpart (and its subparts) relates to CA-3; CCI-000258.

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. Contractor computers connected to the control system, control system network, or a control system component at any point during construction 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.

SECTION 25 05 11.01 Page 11

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. 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 computers, applications, and web-based applications supporting passwords 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 User-Based Authentication

Each user must have a unique account; sharing of a single account between multiple users is prohibited.

1.10.1.5 Demonstration of Compliance

The Government has the right to require demonstration of computer compliance with these requirements at any time during the project.

1.10.1.6 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/ufgs-25-05-11 Each Statement must be signed by a cybersecurity representative for the relevant company.

1.10.2 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.3 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.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.01 Page 12

PART 3 EXECUTION

3.1 CYBERSECURITY HARDENING AND CONFIGURATION GUIDES

Install, configure, and harden all hardware and software furnished on this project in accordance with manufacturer provided documentation, procedures, or methods for secure configuration or installation. Do not implement specific hardening actions if that action would conflict with requireed functionality or another requirement of this Section.

3.2 NETWORK REQUIREMENTS

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

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

3.2.2 Device Identification and Authentication

This subpart (and its subparts) relates to IA-3; CCI-000777, CCI-000778, CCI-001958.

All computers must support IEEE 802.1x for device authentication to the network.

3.2.2.1 For HVAC Control System Devices

Devices using HTTP as a control protocol must use HTTPS instead. Devices using BACnet must support network security as specified for BACnet Secure Connect in ASHRAE 135.

3.2.2.2 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 HTTP as a control protocol must use HTTPS instead.

3.3 ACCESS CONTROL REQUIREMENTS

3.3.1 System Use Notification

{For Government 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}

3.3.1.1 System Use Notification for Local User Interfaces

Devices which are connected to a network and have a local user interface must display a warning banner meeting the requirements of DTM 08-060 on the user interface screen if capable of doing so and must have a permanently affixed label with an approved banner from DTM 08-060 if unable to display the warning banner on the screen. Where it is impractical (perhaps due to device size) to affix the label to the device, affix the label to the device enclosure.

SECTION 25 05 11.01 Page 13

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

This subpart (and its subparts) relates to AC-14; CCI-000061.

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

3.3.3 Enclosures

Prior to final acceptance of the sytsem, lock all lockable enclosures.

Submit an Enclosure Keys submittal with all copies of keys for all enclosures and a key inventory list documenting all keys. Label each key with the matching enclosure identifier.

3.4 USER IDENTIFICATION AND AUTHENTICATION

This subpart (and its subparts) relates to IA-2, IA-2(1),IA-2(12), IA-5 IA-5(b), IA-5(c), IA-5(e), IA-5(g), IA-5(1), IA-5(11); CCI-000764, 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.

This subpart indicates requirements for specific methods of identification and authentication for users and user accounts. Where these requirements conflict apply the following order of precedence: 1) If present, Device Specific Requirements take precedence over any other requirements; and then 2) multifactor authentication requirements take precedence over password requirements.

3.4.1 User Identification and Authentication for All System Types

Unless otherwise indicated, all user interfaces supporting accounts (either FULLY or MINIMALLY) must implement Identification and Authorization via passwords.

3.4.2 User Identification and Authentication for Specific System Types

System specific requirements are in addition to and supersede those indicated for all system types. When no additional requirements are indicated for a specific system type the requirements for all systems still apply to that system type.

3.4.2.1 HVAC Control Systems Devices

No additional system specific requirements apply.

3.4.3 User Identification and Authentication for Specific Devices

There are no additional device specific user interface requirements

SECTION 25 05 11.01 Page 14

3.4.4 Implementation of Identification and Authorization Requirements

Identification and Authorization must be met by one of the following methods:

a. Direct implementation in the user interface.

b. For user interfaces on a computer: inheriting the Identification and Authorization from the computer operating system, either by the operating system limiting access to specific applications by user, or by the application itself having permissions based on the user logged into the computer.

3.4.5 Password-Based Authentication Requirements

3.4.5.1 Passwords for Devices Minimally Supporting Accounts

Devices MINIMALLY supporting accounts must support passwords with a minimum length of six characters.

3.4.5.2 Password Configuration and Reporting

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

3.5 CYBERSECURITY AUDITING

Where an auditing requirement exists for email notification, notify via email the application administrator and Information System Security Officer (ISSO) of the event. Coordinate with the Email Address Point of Contact for email addresses. If outgoing email is not available to the system, configure the system for these notifications for future support of outgoing email.

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

This subpart (and its subparts) relates to AU-2(a), AU-2(c), AU-2(d);

CCI-000123, CCI-001571, CCI-001485, CCI-000130, CCI-000131, CCI-000132,

CCI-000133, CCI-000169, CCI-000172.

3.5.1.1 Default Requirements for Control System Controllers

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

3.5.1.1.1 Controllers Which FULLY Support Accounts

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

3.5.1.1.1.1 Audited Events

Configure each controller to audit the following events:

SECTION 25 05 11.01 Page 15

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. Successful logouts

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

3.5.1.1.1.2 Audit Event Information To Record

Configure each controller 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. the source of the event

d. the identity of any individuals or subjects associated with the event

3.5.1.1.2 Controllers Which Do Not FULLY Support Accounts

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

3.5.2 Audit Time Stamps

This subpart (and its subparts) relates to AU-8; CCI-000159, CCI-001889, CCI-001890.

Any device (computer or controller) generating audit records must have an internal clock capable of providing time with a resolution of one second.

Clocks must not drift more than 10 seconds per day. Configure the system so that each device (computer or controller) generating audit records maintains accurate time to within 1 second. Note that if the control system specifications include requirement for clocks, the most stringent requirement applies.

3.6 REQUIREMENTS FOR LEAST FUNCTIONALITY

This subpart (and its subparts), along with the network communication report submittal specified elsewhere in this section, relates to CM-6(a), CM-6(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.

3.6.1 Device Capabilities

For HVAC Control Systems: Do not provide devices with remote user interfaces or with full 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: For LOW Impact Systems:

Do not provide devices with remote user interfaces or with full user

SECTION 25 05 11.01 Page 16 interfaces where one was not required.

3.7 FIELD QUALITY CONTROL, CYBERSECURITY VALIDATION SUPPORT

In addition to testing and testing support required by other Sections, provide a minimum of 48 hours of technical support for cybersecurity testing of control systems to support the DoD Risk Management Framework process Cybersecurity assessment of the control system. This support is independent of (and in addition to) the Control System Cybersecurity Testing specified in this section.

-- End of Section --

SECTION 25 05 11.01 Page 17

SECTION 25 05 11.02

CYBERSECURITY FOR FIRE & MASS NOTIFICATION CONTROL SYSTEMS

05/21

PART 1 GENERAL

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

This Section refers to Security Requirements Guide (SRGs) and Security Technical Implementation Guide (STIGs). STIGs and SRGs are available online at the Information Assurance Support Environment (IASE) website at https://public.cyber.mil/stigs/downloads/ and an SRG/STIG Applicability Guide and Collection Tool is available at https://public.cyber.mil/stigs/SCAP/ . Not all control system components have applicable STIGs or SRGs. Typically this requirement will apply to BCS workstations and servers as part of the whole solution, or supported systems where STIGs can be applied.

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: Combined Fire Alarm and Mass Notification and Reporting.

1.2 RELATED REQUIREMENTS

This section does not contain sufficient requirements to procure a control system and must be used in conjunction with other Sections which specify control systems. This Section adds cybersecurity requirements to the control systems specified in other Sections, and as these requirements are conditioned on the control system being provided, there may be requirements in this Section that will not apply to this project. 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.

In cases where a requirement is specified in both this Section and in another Section, the more stringent requirement must be met. In cases where a requirement in this Section conflicts with the requirements of another Section such that both requirements cannot be met at the same time, request direction from the Contracting Officer Representative to determine which requirement applies to the project.

SECTION 25 05 11.02 Page 1

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.

NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY (NIST)

NIST FIPS 140-2 (2001) Security Requirements for Cryptographic Modules

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 Administrator Account

An administrator account is an account with full permissions to a device, application, or operating system, including the ability to create and modify other user accounts.

Note that the operating system Administrator Account may be different than Administrator Accounts for applications hosted on that operating system.

Also, most controllers will not have any support for accounts and will therefore not have an 'Aministrator Account'.

1.4.2 Computer

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 Operating System, where Android is considered separate from Linux

e. a device running a version of Apple iOS

Unless otherwise indicated or clear from context use of the word "device" in this Section includes computers.

1.4.3 Controller

A device other than a computer or Ethernet switch. For Fire Protection systems this includes fire alarm control panels, remote operating consoles, and remote…