W912QR25BA017_Specs_Vol3-0000.pdf

Solicitation For Indoor Small Arms Range, Rickenbacker, OH

P2: 508679

Design-Bid-Build

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

04 August 2025

W912QR25BA017

RRS-A: 200A Disposition: Maintain for 15 yrs after construction.

W912QR25BA017_Specs_Vol3-0000

P2# 508679 Indoor Small Arms Range Rickenbacker ANG, OH

THIS PAGE INTENTIONALLY LEFT BLANK

Certified Final Submittal

PROJECT TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

00 80 00.00 06 02/20 SPECIAL PROVISIONS

DIVISION 01 - GENERAL REQUIREMENTS

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

01 32 01.00 06 10/23 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 05/24 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.15 10 11/23 RESIDENT MANAGEMENT SYSTEM CONTRACTOR

MODE (RMS CM)

01 45 04.10 06 CONTRACTOR QUALITY CONTROL

01 45 35 11/20 SPECIAL INSPECTIONS

01 50 00 11/20, CHG 2: 08/22 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 05/23 OPERATION AND MAINTENANCE DATA

01 91 00.15 05/23, CHG 1: 08/23 BUILDING COMMISSIONING

01 91 19 05/2023 BUILDING ENCLOSURE COMMISSIONING

DIVISION 03 - CONCRETE

03 30 00 02/19, CHG 5: 08/23 CAST-IN-PLACE CONCRETE

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

03 62 15.00 06 07/16 FLOWABLE FILL

DIVISION 04 - MASONRY

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

DIVISION 05 - METALS

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

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

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

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 13 53 02/16, CHG 1: 08/17 ELASTOMERIC SHEET WATERPROOFING

07 21 13 08/23 BOARD AND BLOCK INSULATION

07 21 16 08/23 MINERAL FIBER BLANKET INSULATION

07 21 23 08/23 LOOSE FILL THERMAL INSULATION

07 22 00 08/23 ROOF AND DECK INSULATION

07 27 10 08/23 BUILDING AIR BARRIER SYSTEM

PROJECT TABLE OF CONTENTS

07 27 19.01 08/23 SELF-ADHERING AIR BARRIERS

07 27 26 08/23 FLUID-APPLIED MEMBRANE AIR BARRIERS

07 41 13 05/11, CHG 4: 02/21 METAL ROOF PANELS

07 60 00 08/23 FLASHING AND SHEET METAL

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

07 92 00 08/23 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 34 02 08/09 BULLET-RESISTANT COMPONENTS

08 41 13 08/18, CHG 1: 08/18 ALUMINUM-FRAMED ENTRANCES AND

STOREFRONTS

08 71 00 02/16, CHG 4: 02/22 DOOR HARDWARE

08 81 00 05/19 GLAZING

08 91 00 08/20 METAL WALL LOUVERS

DIVISION 09 - FINISHES

09 06 00 08/22 SCHEDULES FOR 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 65 00 08/10, CHG 3: 08/18 RESILIENT FLOORING

09 69 13 11/15, CHG 1: 08/18 RIGID GRID ACCESS FLOORING

09 90 00 02/21 PAINTS AND COATINGS

09 96 00 11/14 HIGH-PERFORMANCE COATINGS

DIVISION 10 - SPECIALTIES

10 14 00.10 08/17, CHG 1: 11/18 EXTERIOR SIGNAGE

10 14 00.20 08/20 INTERIOR SIGNAGE

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 11 - EQUIPMENT

11 48 60 08/07 FIREARMS TRAINING EQUIPMENT

11 67 10 BAFFLE AND SAFETY CEILING SYSTEMS

DIVISION 12 - FURNISHINGS

12 24 13 08/20 ROLLER WINDOW SHADES

12 48 13 08/23 ENTRANCE FLOOR MATS AND FRAMES

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 48.19 05/18, CHG 2: 08/20 BRACING FOR HVAC

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

(TAB) OF HVAC

PROJECT TABLE OF CONTENTS

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

SYSTEMS

23 08 00 05/23 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 09 93 11/15 SEQUENCES OF OPERATION FOR HVAC CONTROL

23 11 20 05/20 FACILITY GAS PIPING

23 23 00 08/21 REFRIGERANT PIPING

23 30 00 05/20, CHG 1: 02/22 HVAC AIR DISTRIBUTION

23 80 20.00 10 05/20 GAS-FIRED HEATING EQUIPMENT

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

DIVISION 25 - INTEGRATED AUTOMATION

25 05 11.01 05/21 CYBERSECURITY FOR FIRE ALARM / MASS

NOTIFICATION SYSTEMS

25 05 11.02 05/21 CYBERSECURITY FOR HVAC CONTROL SYSTEMS

25 05 11.03 05/21 CYBERSECURITY FOR INTERCOM CONTROL

SYSTEMS

DIVISION 26 - ELECTRICAL

26 05 73 08/23 POWER SYSTEM STUDIES

26 08 00 11/22 APPARATUS INSPECTION AND TESTING

26 20 00 08/23 INTERIOR DISTRIBUTION SYSTEM

26 27 13.10 30 10/07, CHG 2: 08/18 ELECTRIC METERS

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

26 56 00 08/21 EXTERIOR LIGHTING

DIVISION 27 - COMMUNICATIONS

27 10 00 08/11 BUILDING TELECOMMUNICATIONS CABLING

SYSTEM

27 41 00 11/21 AUDIO-VISUAL SYSTEMS

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 05/24 CHG 1: 12/24 EARTHWORK

31 05 19.13 02/21 GEOTEXTILES FOR EARTHWORK

31 05 22.00 06 07/16 GEOTEXTILES USED AS FILTERS

31 10 00 02/21 SITE CLEARING

31 21 13 11/18 RADON MITIGATION

31 31 16.13 08/22 CHEMICAL TERMITE CONTROL

31 31 16.19 08/22 TERMITE CONTROL BARRIERS

31 32 19.16 02/21 GEOTEXTILE SOIL STABILIZATION

31 62 50 11/20, CHG 1: 05/22 DENSIFIED AGGREGATE PIERS

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 01 13.62 11/23 BITUMINOUS SURFACE TREATMENT

PROJECT TABLE OF CONTENTS

32 01 13.64 11/23 REJUVENATION OF ASPHALT PAVEMENT

SURFACES

32 01 16.71 11/22 COLD MILLING ASPHALT PAVING

32 01 16.74 05/18 IN PLACE HOT REUSED ASPHALT PAVING

32 01 17.61 05/22, CHG 1: 11/23 SEALING CRACKS IN ASPHALT PAVING

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

32 05 33 08/17 LANDSCAPE ESTABLISHMENT

32 11 23 05/22 AGGREGATE BASE COURSE AND/ORGRADED

CRUSHED AGGREGATE BASE COURSE FOR

FLEXIBLE PAVING

32 11 23.23 08/22 BASE COURSE DRAINAGE LAYERS

32 11 26.19 05/20 BITUMINOUS-STABILIZED BASE AND SUBBASE

COURSES

32 11 33.13 05/20 PORTLAND CEMENT-STABILIZED BASE COURSES

32 11 36.13 11/19 LEAN CONCRETE BASE COURSE

32 12 16.16 11/20 ROAD-MIX ASPHALT PAVING

32 13 13.06 05/20 PORTLAND CEMENT CONCRETE PAVEMENT FOR

ROADS AND SITE FACILITIES

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

ROADS AND SITE FACILITIES

32 13 73.00 06 07/16 COMPRESSION JOINT SEALS FOR CONCRETE

PAVEMENTS

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

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

32 31 13 11/21 CHAIN LINK FENCES AND GATES

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

DIVISION 33 - UTILITIES

33 11 00 02/18, CHG 2: 11/23 WATER UTILITY DISTRIBUTION PIPING

33 30 00 05/18 SANITARY SEWERAGE

33 40 00 11/21 STORMWATER UTILITIES

33 46 13 05/20 FOUNDATION DRAINAGE

33 71 02 08/21 UNDERGROUND ELECTRICAL DISTRIBUTION

DIVISION 35 - WATERWAY AND MARINE CONSTRUCTION

35 42 37.00 06 07/16 STONE PROTECTION

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS

SECTION 25 05 11 .01

CYBERSECURITY FOR FIRE ALARM / MASS NOTIFICATION 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. The "Control Systems SRG" does not apply to work performed under this Section; all requirements within this section to apply applicable SRGs DO NOT include the "Control Systems SRG".

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 Alarm & Mass Notification .

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 extent referenced. The publications are referred to within the text by the basic designation only.

SECTION 25 05 11.01 Page 1

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

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

NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY (NIST)

NIST FIPS 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 annunciators.

SECTION 25 05 11.01 Page 2

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.

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

SECTION 25 05 11.01 Page 3

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 for Fire Alarm Systems are privileged user interfaces as indicated and shown, or when another requirement of this Section establishes they are privileged. For all other systems, 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. For Fire Protection Systems, User Interfaces that can inhibit or force the activation of a fire suppression system (e.g. such as for a

SECTION 25 05 11.01 Page 6 pre-action or deluge system) are privileged user interfaces.

f . 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, 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 requesting permission for wireless or wired broadcast communication, the Wireless and Wired Broadcast Communication Request submittal must be approved prior to control system device selection and installation.

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

c. If requesting permission for the use of a device with multiple physical connections to IP networks, the Multiple IP Connection

SECTION 25 05 11.01 Page 7

Device Request must be approved prior to control system device selection and installation.

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.

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

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

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

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

Wireless and Wired Broadcast Communication Request ; G

Device Account Lock Exception Request ; G

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

SD-07 Certificates

Software Licenses ; G

SD-11 Closeout Submittals

Confidential Password Report ; G

Enclosure Keys ; G

SECTION 25 05 11.01 Page 8

Auditing Front End Software ; G

Device Audit Record Upload Software ; G

System Maintenance Tool Software ; G

Control System Inventory Report ; G

Integrity Verification Software ; 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.

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(9), SC-7(11); CCI-000258, CCI-003072, CCI-003073, CCI-003075, CCI-002402. For MODERATE Impact systems, this subpart also relates to SC-7; CCI-001126

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. For MODERATE Impact Systems: Also describe the impact of loss of the connection on the control system. 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, SECTION 25 05 11.01 Page 9 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

{For Government Reference Only: This subpart (and its subparts) relates to CA-9, PL-8; CCI-003075; CCI-003072, CCI-003073, CCI-003075. }

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

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

Provide a Control System Inventory report using the Inventory Spreadsheet listed under this Section at https://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/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.

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-003053, CCI-003072, CCI-003073, 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.

1.8.5 Control System Cybersecurity Documentation

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

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

SECTION 25 05 11.01 Page 10

CCI-003130, CCI-003131

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

1.8.5.1 Software Applications

For all software applications running on computers provide:

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

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

c. administrator documentation that describes secure operation of the software {For Government Reference Only: relates to CCI-00312 6}

d. administrator documentation that describes effective use and maintenance of security functions or mechanisms for the software {For Government Reference Only: relates to CCI-003127}

e. administrator documentation that describes known vulnerabilities regarding configuration and use of administrative (i.e. privileged) functions for the software {For Government Reference Only: relates to

CCI-003128}

f. user documentation that describes user-accessible security functions or mechanisms in the software and how to effectively use those security functions or mechanisms {For Government Reference Only:

relates to CCI-003129}

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

h. user documentation that describes user responsibilities in maintaining the security of the software {For Government Reference Only: relates to CCI-003131}

1.9 SOFTWARE LICENSING

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

For all software provided that has not already been licensed to the government or project site, provide a license to the Governmentfor 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

SECTION 25 05 11.01 Page 11

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.

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.

SECTION 25 05 11.01 Page 12

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.

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 Wireless and Wired Broadcast Communication for Fire Protection Systems

The use of wireless and wired broadcast communication for fire protection systems within a facility is prohibited. Wireless communication may be used to provide communication from the fire protection system in a facility to the central monitoring station. Communication between the fire protection system and the central monitoring station must be via FIPS 140-2 certified devices.

3.2.2 Wireless and Wired Broadcast Communication for Systems Other than Fire Protection Systems

{For Government Reference Only: This subpart (and its subparts) relates to AC-18, AC-18(3); CCI-001438, CCI-001439, CCI-002323, CCI-001441, CCI-002252}

Unless explicitly authorized by the Government, do not use any wireless or wired broadcast communication.

3.2.2.1 Wireless and Wired Broadcast IP Communications

Unless specifically approved and installed in accordance with the project

SECTION 25 05 11.01 Page 13 site requirements, Do not install wireless or wired broadcast 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.2.2.2 Non-IP Wireless Communication

For MODERATE Impact Systems: When non-IP wireless communication is explicitly authorized by the Government, the radios must meet NIST FIPS 140-2 Level 2.

3.2.2.3 Wireless and Wired Broadcast Communication Request

Provide a report documenting the proposed use of wireless or wired broadcast communication prior to device selection using the Wireless and Wired Broadcast Communication Request Schedule at https://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ufgs-25-05-11 If there is no proposed use of wireless or wired broadcast communication, provide a document indicating this instead of the Request Schedule.

For each device proposed to use wireless or wired broadcast 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. For wireless communication, also show: RF Frequency, Radiated Power in dBm (decibel with a milliwatt reference), free-space range, and the expected as-installed range.

3.2.3 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.4 IP Control Networks

{For Government Reference Only: This subpart relates to CM-6(a), CM-7(a), CM-7(b), CM-7(1)(b), SC-41; CCI-001588, CCI-000380, CCI-000381, CCI-000382, CCI-001761, CCI-001762, CCI-002544, CCI-002545, CCI-002546.}

IP Networks must be Ethernet networks and must use switches which are Ethernet Switches or Daisy Chain IP Controllers as defined in this Section. Do not use nonsecure functions, ports, protocols and services as defined in DODI 8551.01 unless those ports, protocols and services are specifically required by the control system specifications or otherwise specifically authorized by the Government. Do not use ports, protocols and services that are not specified in the control system specifications or required for operation of the control system.

For MODERATE Impact Systems, unless explicitly authorized, do not use IP networks if the same control functionality is available through the use of non-IP networks.

SECTION 25 05 11.01 Page 14

3.2.5 Device Identification and Authentication

{For Government Reference Only: 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.3 ACCESS CONTROL REQUIREMENTS

3.3.1 User Accounts

This subpart (and its subparts) relate to AC-2(a), AC-3, AC-6(1), AC-6(10), AC-6(2), AC-6(9), CM-11(2), and IA-2; CCI-002110, CCI-000213, CCI-002235, CCI-002221, CCI-002222, CCI-002223, CCI-002235, CCI-000039, CCI-001419, CCI-002234, CCI-001812, and CCI-000764.

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

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

All user interfaces FULLY supporting accounts must implement user-based authentication where each account is uniquely assigned to a specific user. User interfaces FULLY supporting accounts must implement at least three (3) levels of user account privilege including: 1) an account with read-only permissions 2) an account with full permissions including account creation and modification and 3) an account with greater permissions than read-only but without account creation and modification.

3.3.1.1 Computers

All computer operating systems must FULLY support user accounts and implement accounts for access. Each control system software application not supporting accounts and running on a computer must be installed such that use of the software is restricted by the computer operating system to specific users.

Applications running on computers shall not require the user be logged in to a computer operating system administrator account for normal operation. It is permissible to require the computer operating system administrator account for initial application installation and configuration.

3.3.1.2 Controllers

For user interfaces provided by controllers, provide access control in accordance with the User Interface Requirements table for the applicable control system and user interface type.

a. For table entries of "NA": NA means Not Applicable, there are no interfaces in this category.

b. For table entries of "None Required": The user interface is not required to support user accounts.

c. For table entries of "MINIMALLY": The user interface must at least MINIMALLY support user accounts.

SECTION 25 05 11.01 Page 15

d. For table entries of "FULLY": The user interface must at FULLY support user accounts.

e. For table entries of "KEY": The user interface must have physical security in the form of either a key lock on the interface itself or be furnished inside a locked enclosure. Where this is required for a read only interface, this lock must prevent viewing of data on the interface; for other interfaces, this lock must prevent using the interface to alter data.

f. For table entries of "Physical Security": For Local FULL interfaces, the interface must be located inside mission space. For Local Limited (not FULL) interfaces, the user interface must either a) be located within mission space or b) be protected by physical security at least as good as the control devices (and equipment controlled by the control devices) affected by the interface. For purposes of this requirement, 'affected' includes controllers with data that can be directly altered by the interface, as well as mechanical and/or electrical equipment directly controlled by those controllers, but does not include other interactions.

g. Entries of the form "X and Y" must meet both the requirement indicated for X and the requirement indicated for Y. For example, an entry of "MINIMALLY and Physical Security" indicates the user interface must both MINIMALLY support accounts and have physical security.

h. Entries of the form "X or Y" must meet either the requirement indicated for X or the requirement indicated for Y.

3.3.1.2.1 Fire Protection Systems

User Interface Requirements for MODERATE Impact Fire Protection Systems

User Interface Type Access Control Requirement (See note 2)

Local Read Only None Required

Local Limited, Non-privileged KEY or MINIMALLY

Local Limited, Privileged FULLY

Local Full KEY

Remote Read Only MINIMALLY

Remote Limited, Non-Privileged FULLY

Remote Limited, Privileged

AND

Remote Full

FULLY

SECTION 25 05 11.01 Page 16

User Interface Requirements for MODERATE Impact Fire Protection Systems

User Interface Type Access Control Requirement (See note 2)

Notes:

1)Local Read Only User Interfaces are always Non-Privileged 2)Devices outside mission space require physical security protections as indicated (in "PHYSICAL SECURITY IN MODERATE IMPACT SYSTEMS")

3.3.1.3 Additional User Account Expiration Requirements In MODERATE Impact Systems:

In addition to other user account requirements, user account expiration and auditing must be configured as indicated.

3.3.1.3.1 For Control System Applications Running on Computers

If temporary accounts are supported, expire temporary accounts 72 hours after creation. Expire all other accounts after 35 days of inactivity.

3.3.2 Unsuccessful Logon Attempts

This subpart (and its subparts) relate to AC-7 (a), AC-7 (b); CCI-001423, CCI-002236, CCI-002237, CCI-002238 .

Except for high availability user interfaces indicated as exempt, devices must meet the indicated requirements for handling unsuccessful logon attempts. If a device cannot meet these requirements, document device capabilities to protect from subsequent logon attempts and propose alternate protections in a Device Account Lock Exception Request submittal. Do not implement alternate protection measures in lieu of the indicated requirements without explicit permission from the Government.

If no Device Account Lock Exceptions are requested, provide a document stating that no approval is being requested as the Device Account Lock Exception Request.

3.3.2.1 Devices MINIMALLY Supporting Accounts

For MODERATE Impact Systems: Devices which MINIMALLY (but not FULLY) support accounts must lock the user account account after five consecutive failed login attempts and must unlock the user account after 60 minutes have elapsed without an unsuccessful login attempt or by a successful login to a separate administrator account.

3.3.2.2 Devices FULLY Supporting Accounts

Devices which FULLY support accounts must meet the following requirements.

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. If the account being locked is the sole administrator account on the device, the account must stay locked for

SECTION 25 05 11.01 Page 17

1 hour and then automatically unlock.

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

3.3.2.3 High Availability Interfaces Exempt from Unsuccessful Logon Attempts Requirements

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

3.3.3 System Use Notification

This subpart (and its subparts) relates to AC-8; CCI-000048, CCI-002247, CCI-002243, CCI-002244, CCI-002245, CCI-002246, CCI-002248.

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

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

{For Government Reference Only: This subpart (and its subparts) relates to AC-14; CCI-000061, CCI-000232}

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

3.3.5 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,…