ATT G 1615269spc3of4.pdf

WORK ORDER NO.

At the

PREPARED BY:

Architectural: Mechanical:

Civil: Electrical:

Structural:

APPROVED BY:

Specifications:

For Commander, NAVFAC:

Date:

Submitted By: Date:

UNCLASSIFIED/FOR OFFICIAL USE ONLY

P131 Communications Center

Landscape Arch: Chad St. John Telecommunication: Rich Hoffman Interiors: Jennifer Adams

Help Note All fields can be edited. If you have trouble selecting a field, either use the tab key or click "highlight fields" in Acrobat 7. Fields that are not needed can be selected and deleted. Tool tips with "additional field" can be deleted or changed. The contract number can also be deleted or changed.

09059054 Typewriter

Snyder, Brandi LGI00704201 Text Box This page left intentionally blank

P131 Communications Center eProjects No.: 1615269 NSA Souda Bay, Greece

PROJECT TABLE OF CONTENTS

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

00 01 15 02/11 LIST OF DRAWINGS

00 73 04 08/08 SUPPLEMENTARY CONDITIONS FOR PROJECTS

IN MEDITERRANEAN AREA

DI VI SI ON 01 - GENERAL REQUI REMENTS

01 11 00 08/15 SUMMARY OF WORK

01 14 00 11/11 WORK RESTRICTIONS

01 20 00.00 20 11/11 PRICE AND PAYMENT PROCEDURES

01 30 00 08/15 ADMINISTRATIVE REQUIREMENTS

01 30 01.00 20 06/20 DESIGN, PROCUREMENT AND INSTALLATION

OF FURNITURE, FIXTURES, AND EQUIPMENT

01 31 23.13 20 05/17, CHG 6: 02/21 ELECTRONIC CONSTRUCTION AND FACILITY

SUPPORT CONTRACT MANAGEMENT SYSTEM

01 32 17.00 20 05/18 COST-LOADED NETWORK ANALYSIS SCHEDULES

(NAS)

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

01 33 29 02/17 SUSTAINABILITY REPORTING

01 35 13 11/11 SPECIAL PROJECT PROCEDURES

01 35 26 11/15 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 02/19 SOURCES FOR REFERENCE PUBLICATIONS

01 42 15 02/14 METRIC MEASUREMENTS

01 45 00.00 20 11/11 QUALITY CONTROL

01 45 35 11/20 SPECIAL INSPECTIONS

01 50 00 05/18 TEMPORARY CONSTRUCTION FACILITIES AND

CONTROLS

01 57 19 11/15, CHG 4: 08/20 TEMPORARY ENVIRONMENTAL CONTROLS

01 57 19.01 20 11/15, CHG 3: 08/20 SUPPLEMENTAL TEMPORARY ENVIRONMENTAL

CONTROLS

01 58 00 08/19, CHG 2: 11/20 PROJECT IDENTIFICATION

01 74 19 02/19, CHG 1: 08/20 CONSTRUCTION WASTE MANAGEMENT AND

DISPOSAL

01 78 00 05/19 CLOSEOUT SUBMITTALS

01 78 23 08/15, CHG 1: 11/20 OPERATION AND MAINTENANCE DATA

01 78 24.00 20 02/15, CHG 2: 11/20 FACILITY ELECTRONIC OPERATION AND

MAINTENANCE SUPPORT INFORMATION (eOMSI)

01 91 00.15 20 02/21 TOTAL BUILDING COMMISSIONING

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

02 41 00 05/10 DEMOLITION

DI VI SI ON 03 - CONCRETE

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

DI VI SI ON 05 - METALS

05 12 00 08/18 STRUCTURAL STEEL

05 30 00 05/15 STEEL DECKS

05 50 13 05/17 MISCELLANEOUS METAL FABRICATIONS

05 51 33 02/16 METAL LADDERS

05 52 00 02/18 METAL RAILINGS

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

PROJECT TABLE OF CONTENTS Page 1

06 10 00 08/16 ROUGH CARPENTRY

06 41 16.00 10 08/10 PLASTIC-LAMINATE-CLAD ARCHITECTURAL

CABINETS

06 61 16 08/20 SOLID SURFACING FABRICATIONS

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

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

FOR AIR TIGHTNESS

07 13 53 02/16 ELASTOMERIC SHEET WATERPROOFING

07 21 13 02/16 BOARD AND BLOCK INSULATION

07 21 16 11/11 MINERAL FIBER BLANKET INSULATION

07 22 00 02/16 ROOF AND DECK INSULATION

07 27 10.00 10 08/19 BUILDING AIR BARRIER SYSTEM

07 52 00 05/12 MODIFIED BITUMINOUS MEMBRANE ROOFING

07 60 00 05/17 FLASHING AND SHEET METAL

07 84 00 05/10 FIRESTOPPING

07 92 00 08/16 JOINT SEALANTS

DI VI SI ON 08 - OPENI NGS

08 11 13 08/20 STEEL DOORS AND FRAMES

08 11 16 05/17 ALUMINUM DOORS AND FRAMES

08 14 00 08/16 WOOD DOORS

08 31 00 05/17 ACCESS DOORS AND PANELS

08 33 23 08/20 OVERHEAD COILING DOORS

08 34 73 11/19 SOUND CONTROL DOOR ASSEMBLIES

08 41 13 08/18 ALUMINUM-FRAMED ENTRANCES AND

STOREFRONTS

08 44 00 05/19 CURTAIN WALL AND GLAZED ASSEMBLIES

08 71 00 02/16 DOOR HARDWARE

08 81 00 05/19 GLAZING

08 91 00 08/20 METAL WALL LOUVERS

DI VI SI ON 09 - FI NI SHES

09 22 00 02/10 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 29 00 08/16 GYPSUM BOARD

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

09 51 00 08/17 ACOUSTICAL CEILINGS

09 62 38 08/17 STATIC-CONTROL FLOORING

09 65 00 08/10 RESILIENT FLOORING

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

09 69 13 11/15 RIGID GRID ACCESS FLOORING

09 90 00 02/21 PAINTS AND COATINGS

09 96 00 11/14 SILICONE ELASTOMERIC COATINGS

DI VI SI ON 10 - SPECI ALTI ES

10 11 00 08/20 VISUAL DISPLAY UNITS

10 14 00.10 08/17 EXTERIOR SIGNAGE

10 14 00.20 08/20 INTERIOR SIGNAGE

10 21 13 08/20 TOILET COMPARTMENTS

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

10 56 13 04/06 STEEL SHELVING

PROJECT TABLE OF CONTENTS Page 2

DI VI SI ON 12 - FURNI SHI NGS

12 21 00 08/17 WINDOW BLINDS

12 24 13 08/20 ROLLER WINDOW SHADES

12 48 13 08/17 ENTRANCE FLOOR MATS AND FRAMES

12 93 00 08/17 SITE FURNISHINGS

DI VI SI ON 13 - SPECI AL CONSTRUCTI ON

13 48 73 05/20, CHG 1: 08/20 SEISMIC CONTROL FOR NON-STRUCTURAL

COMPONENTS

DI VI SI ON 14 - CONVEYI NG EQUI PMENT

14 21 23 05/16 ELECTRIC TRACTION PASSENGER ELEVATORS

DI VI SI ON 21 - FI RE SUPPRESSI ON

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

PROTECTION

21 22 00 04/20 CLEAN AGENT FIRE EXTINGUISHING SYSTEMS

DI VI SI ON 22 - PLUMBI NG

22 00 00 11/15 PLUMBING, GENERAL PURPOSE

22 05 48.00 20 04/06 MECHANICAL SOUND, VIBRATION, AND

SEISMIC CONTROL

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

23 03 00.00 20 08/10 BASIC MECHANICAL MATERIALS AND METHODS

23 05 15 02/14 COMMON PIPING FOR HVAC

23 05 93 11/15 TESTING, ADJUSTING, AND BALANCING FOR

HVAC

23 07 00 02/13 THERMAL INSULATION FOR MECHANICAL

SYSTEMS

23 09 00 02/19 INSTRUMENTATION AND CONTROL FOR HVAC

23 09 13 11/15 INSTRUMENTATION AND CONTROL DEVICES

FOR HVAC

23 09 23.02 02/19 BACNET DIRECT DIGITAL CONTROL FOR HVAC

AND OTHER BUILDING CONTROL SYSTEMS

23 21 23 08/17 HYDRONIC PUMPS

23 23 00 10/07 REFRIGERANT PIPING

23 25 00 11/08 CHEMICAL TREATMENT OF WATER FOR

MECHANICAL SYSTEMS

23 30 00 05/20 HVAC AIR DISTRIBUTION

23 64 10 11/16 WATER CHILLERS, VAPOR COMPRESSION TYPE

23 64 26 08/09 CHILLED, CHILLED-HOT, AND CONDENSER

WATER PIPING SYSTEMS

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

23 81 23.00 20 02/10 COMPUTER ROOM AIR HANDLING UNITS

23 82 00.00 20 02/16 TERMINAL HEATING UNITS

DI VI SI ON 25 - I NTEGRATED AUTOMATI ON

25 05 11.21 11/17 CYBERSECURITY FOR FACILITY-RELATED

CONTROL SYSTEMS FIRE, AND LIFE SAFETY

25 05 11.23 11/17 CYBERSECURITY FOR FACILITY-RELATED

PROJECT TABLE OF CONTENTS Page 3

CONTROL SYSTEMS ENERGY MANAGEMENT

CONTROL SYSTEM (EMCS) TO INCLUDE HVAC

25 05 11.26 11/17 CYBERSECURITY FOR FACILITY-RELATED

CONTROL SYSTEMS UTILITY CONTROL

SYSTEMS PLC FOR GENERATOR

CONOTROLS,FUEL SYSTEM, UPS, AND

ADVANCE METERING INFRASTRUCTURE (AMI)

25 05 11.28 11/17 CYBERSECURITY FOR FACILITY-RELATED

CONTROL SYSTEMS ELECTRONIC SECURITY

SYSTEMS INCLUDING CCTV, ACCESS

CONTROLS SYSTEMS, AND INTRUSION

DETECTION SYSTEMS

25 10 10 02/19 UTILITY MONITORING AND CONTROL SYSTEM

(UMCS) FRONT END AND INTEGRATION

DI VI SI ON 26 - ELECTRI CAL

26 08 00 08/08 APPARATUS INSPECTION AND TESTING

26 11 16 02/10, CHG 2: 11/19 SECONDARY UNIT SUBSTATIONS

26 20 00 08/19 INTERIOR DISTRIBUTION SYSTEM

26 23 00 05/15 LOW-VOLTAGE SWITCHGEAR

26 24 13 05/15, CHG 1: 08/17 SWITCHBOARDS

26 27 14.00 20 02/11 ELECTRICITY METERING

26 28 01.00 10 10/07 COORDINATED POWER SYSTEM PROTECTION

26 29 23 02/20 ADJUSTABLE SPEED DRIVE (ASD) SYSTEMS

UNDER 600 VOLTS

26 31 00 05/15 SOLAR PHOTOVOLTAIC (PV) COMPONENTS

26 32 15.00 05/20 ENGINE-GENERATOR SET STATIONARY

15-2500 KW, WITH AUXILIARIES

26 33 53 05/19 STATIC UNINTERRUPTIBLE POWER SUPPLY

(UPS)

26 41 00 11/13 LIGHTNING PROTECTION SYSTEM

26 51 00 05/20 INTERIOR LIGHTING

26 56 00 05/20 EXTERIOR LIGHTING

DI VI SI ON 27 - COMMUNI CATI ONS

27 10 00 08/11 BUILDING TELECOMMUNICATIONS CABLING

SYSTEM

27 51 16 05/20 PUBLIC ADDRESS SYSTEMS

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

28 08 10 05/16 ELECTRONIC SECURITY SYSTEM ACCEPTANCE

TESTING

28 10 05 05/16 ELECTRONIC SECURITY SYSTEMS (ESS)

28 31 76 08/20 INTERIOR FIRE ALARM AND MASS

NOTIFICATION SYSTEM, ADDRESSABLE

DI VI SI ON 31 - EARTHWORK

31 05 19 08/08 GEOTEXTILE

31 05 22 08/08 GEOTEXTILES USED AS FILTERS

31 11 00 11/18 CLEARING AND GRUBBING

31 21 13 11/18 RADON MITIGATION

31 23 00.00 20 02/11 EXCAVATION AND FILL

DI VI SI ON 32 - EXTERI OR I MPROVEMENTS

PROJECT TABLE OF CONTENTS Page 4

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

32 05 33 08/17 LANDSCAPE ESTABLISHMENT

32 11 23 08/17 AGGREGATE BASE COURSES

32 12 13 05/17 BITUMINOUS TACK AND PRIME COATS

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 14 13.13 11/19 INTERLOCKING PRECAST CONCRETE UNIT

PAVING

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

32 17 23 08/16 PAVEMENT MARKINGS

32 31 13.53 02/20 HIGH-SECURITY FENCES (CHAIN LINK AND

ORNAMENTAL) AND GATES

32 84 24 08/11 IRRIGATION SPRINKLER SYSTEMS

32 93 00 08/17 EXTERIOR PLANTS

DI VI SI ON 33 - UTI LI TI ES

33 01 50.31 02/20 LEAK DETECTION FOR FUELING SYSTEMS

33 11 00 02/18 WATER UTILITY DISTRIBUTION PIPING

33 30 00 05/18 SANITARY SEWERAGE

33 40 00 02/10 STORM DRAINAGE UTILITIES

33 52 10 11/18 FUEL SYSTEMS PIPING (SERVICE STATION)

33 56 10 05/19 FACTORY-FABRICATED FUEL STORAGE TANKS

33 71 02 02/15 UNDERGROUND ELECTRICAL DISTRIBUTION

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

DI VI SI ON 34 - TRANSPORTATI ON

34 71 13.19 02/20 CRASH RATED ACTIVE VEHICLE BARRIERS

AND CONTROLS

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 5

THIS PAGE INTENTIONALLY LEFT BLANK

PROJECT TABLE OF CONTENTS Page 6

SECTION 25 05 11.21

CYBERSECURITY FOR FACILITY-RELATED CONTROL SYSTEMS

FIRE, AND LIFE SAFETY

11/17

PART 1 GENERAL

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

1.1 CONTROL SYSTEM APPLICABILITY

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

Different versions have requirements applicable to different control systems. This specific Section applies only to the following control systems: Fire, and Life Safety.

1.2 RELATED REQUIREMENTS

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

1.3 REFERENCES

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

U.S. DEPARTMENT OF DEFENSE (DOD)

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

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

1.4 DEFINITIONS

1.4.1 Computer

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

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

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

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

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

SECTION 25 05 11.21 Page 1

e. a device running a version of Apple iOS

1.4.2 Network Connected

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

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

1.4.3 User Account Support Levels

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

1.4.3.1 FULLY Supported

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

1.4.3.2 MINIMALLY Supported

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

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

1.4.3.3 NOT Supported

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

1.4.4 User Interface

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

1.4.4.1 Limited Local User Interface

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

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

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

FOR HVAC).

SECTION 25 05 11.21 Page 2

1.4.4.2 Full Local User Interface

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

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

1.4.4.3 Remote User Interface

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

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

1.5 ADMINISTRATIVE REQUIREMENTS

1.5.1 Coordination

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

a. If requesting permission for wireless communication, the Wireless Communication Request submittal must be approved prior to control system device selection and integration.

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

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

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

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

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

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

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

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

SECTION 25 05 11.21 Page 3

1.6 SUBMITTALS

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

submittals not having a "G" designation are for Contractor Quality Control approval. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance with Section 01 33 29 SUSTAINABILITY REPORTING.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-01 Preconstruction Submittals

Wireless Communication Request

Device Account Lock Exception Request; G

Multiple IP Connection Device Request; G

Contractor Computer Cybersecurity Compliance Statements; G

Contractor Temporary Network Cybersecurity Compliance Statements; G

SD-02 Shop Drawings

User Interface Banner Schedule; G

Network Communication Report; G

Cybersecurity Riser Diagram; G

Control System Inventory Report; G

Cybersecurity Interconnection Schedule; G

SD-03 Product Data

Control System Cybersecurity Documentation

SD-07 Certificates

Software Licenses

Cybersecurity Representative's Certification of Qualifications; G

SD-11 Closeout Submittals

Password Summary Report; G

Software Recovery and Reconstitution Images

Device Audit Record Upload Software; G

1.7 QUALITY CONTROL

1.7.1 Cybersecurity Representative

Provide a Cybersecurity Representative as the key person to implement and manage the cybersecurity of all related control systems of the project.

Submit the Cybersecurity Representative's certification of qualifications

SECTION 25 05 11.21 Page 4 in accordance with DoDD 8570/DoDD 8140 requirements no later than 30 calendar days after Notice to Proceed. Submit one hard copy and an electronic copy.

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

1.8 CYBERSECURITY DOCUMENTATION

1.8.1 Cybersecurity Interconnection Schedule

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

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

Device Identifier, Device Description, Transport layer Protocol, Network Address, Port (if applicable), MAC (Layer 2) address (if applicable), Media, Application Protocol, Service (if applicable), Descriptive Purpose of communication. 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 http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/forms-graphics-tables

1.8.2 Network Communication Report

{For Reference Only: This subpart (and its subparts) relates to CA-9;CCI-002102, CCI-002103, CCI-002104, CCI-002105 and also the submittal requirements associated with CM-6, CM-7 and SC-41}

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

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

1.8.3 Control System Inventory Report

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

Provide a Control System Inventory report using the Inventory Spreadsheet listed under this Section at

SECTION 25 05 11.21 Page 5 http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/forms-graphics-tables documenting all devices, including network infrastructure devices, non-networked devices, input devices (e.g. sensors) and output devices (e.g. actuators). For each device provide all applicable information for which there is a field on the spreadsheet in accordance with the instructions on the spreadsheet.

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

1.8.4 Software Recovery and Reconstitution Images

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

CP-10;CCI-000550, CCI-000551, CCI-000552}

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

1.8.5 Cybersecurity Riser Diagram

{For Reference Only: This subpart (and its subparts) relates to PL-2(a);CCI-003051, CCI-003053}

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

1.8.6 Control System Cybersecurity Documentation

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

CCIs:CCI-003124, CCI-003125, CCI-003126, CCI-003127, CCI-003128, CCI-003129,CCI-003130, CCI-003131}

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

1.8.6.1 Default Requirements for Control System Devices

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

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

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

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

d. Documentation that describes effective use and maintenance of security functions or mechanisms for the device. {for reference only: relates

SECTION 25 05 11.21 Page 6 to CCI-003127}

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

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

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

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

1.9 SOFTWARE UPDATE LICENSING

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

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

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

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

1.10 CYBERSECURITY DURING CONSTRUCTION

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

AC-18,SA-3, CCI-00258}

In addition to the control system cybersecurity requirements indicated in this section, meet following requirement throughout the construction process.

1.10.1 Contractor Computer Equipment

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

1.10.1.1 Operating System

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

1.10.1.2 Anti-Malware Software

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

1.10.1.3 Passwords and Passphrases

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

1.10.1.4 Contractor Computer Cybersecurity Compliance Statements

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

1.10.2 Temporary IP Networks

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

1.10.2.1 Network Boundaries and Connections

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

1.10.3 Government Access to Network

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

1.10.4 Passwords and Passphrases

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

1.10.5 Contractor Temporary Network Cybersecurity Compliance Statements

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

SECTION 25 05 11.21 Page 8

1.11 CYBERSECURITY DURING WARRANTY PERIOD

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

PART 2 PRODUCTS

Not Used.

PART 3 EXECUTION

3.1 ACCESS CONTROL REQUIREMENTS

3.1.1 User Accounts

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

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

3.1.1.1 Default Requirements for Control System Devices

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

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

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

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

3.1.2 Unsuccessful Logon Attempts

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

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

3.1.2.1 Devices MINIMALLY Supporting Accounts

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

3.1.2.2 Devices FULLY Supporting Accounts

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

SECTION 25 05 11.21 Page 9

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

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

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

3.1.2.3 High Availability Interfaces Exempt from Unsuccessful Logon Attempts Requirements

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

3.1.3 System Use Notification

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

AC-8;CCI-000048, CCI-002247, CCI-002243, CCI-002244, CCI-002245,

CCI-002246,CCI-000050, CCI-002248}

Web interfaces must display a warning banner meeting the requirements of

DTM 08-060 .

Devices which are connected to a network and have a user interface must display a warning banner meeting the requirements of DTM 08-060 if capable of doing so. Devices which are connected to a network and have a user interface but are not capable of displaying a banner must have a permanently affixed label displaying an approved banner from DTM 08-060 .Labels must be machine printed or engraved, plastic or metal, designed for permanent installation, must use a font no smaller than 14 point, and must provide a high contract between font and background colors.

3.1.3.1 User Interface Banner Schedule

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

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

User I nt er f ace Description

User I nt er f ace Location

Type of User Interface

Banner I mpl ement at i on

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

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

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

3.1.4 Permitted Actions Without Identification or Authentication

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

SECTION 25 05 11.21 Page 10

AC-14;CCI-000061, CCI-000232}

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

3.1.5 Wireless Access

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

3.1.5.1 Wireless IP Communications

Do not install wireless IP networks, including: do not install a wireless access point; do not install or configure an ad-hoc wireless network; do not install or configure a WiFi Direct communication.

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

3.1.5.2 Non-IP Wireless Communication

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

3.1.5.3 Wireless Communication Request

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

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

3.1.5.4 Wireless Communication Testing

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

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

SECTION 25 05 11.21 Page 11

3.2 CYBERSECURITY AUDITING

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

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

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

3.2.1.1 Default Requirements for Control System Devices

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

3.2.1.1.1 Devices Which FULLY Support Accounts

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

3.2.1.1.1.1 Audited Events

Configure each device to audit the following events:

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

b. Successful and unsuccessful logon attempts

c. Privileged activities or other system level access

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

e. Concurrent logons from different workstations

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

g. All kernel module load, unload, and restart

3.2.1.1.2 Devices Which Do Not FULLY Support Accounts

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

3.2.2 Audit Storage Capacity and Audit Upload

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

AU-4;CCI-001848, CCI-001849}

a. For devices that have STIG/SRGs related to audit storage capacity comply with the requirements of those STIG/SRGs.

SECTION 25 05 11.21 Page 12

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

3.2.2.1 Device Audit Record Upload Software

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

Contact local ISSM and System Owner/Program Manager for device audit record upload software requirements. Submit copies of device audit record upload software. If there are no non-computer devices requiring auditing, provide a document stating this in lieu of this submittal.

3.2.3 Time Stamps

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

AU-8;CCI-000159, CCI-001889, CCI-001890}

3.2.3.1 Control System Devices

Time stamp requirements for Control Systems are as indicated in the Control System specifications. Devices generating audit records must have internal clocks capable of providing time with a resolution of 1 second.

Clocks cannot drift more than 10 seconds per day. Configure the system so that each device generating audit records maintains accurate time to within 1 second.

3.2.3.2 Default Requirements for Control System Devices

For control system devices where Time Stamps requirements are not otherwise indicated in this Section: Devices generating audit records must have internal clocks capable of providing time with a resolution of 1 second. Clocks must not drift more than 10 seconds per day. Configure the system so that each device generating audit records maintains accurate time to within 1 second.

3.3 REQUIREMENTS FOR LEAST FUNCTIONALITY

{For Reference Only: This subpart (and its subparts), along with the network communication report submittal specified elsewhere in this section, relates to CM-6 (a), (c), CM-7, CM-7 (1)(b), SC-41;

CCI-000363,CCI-000364, CCI-000365, CCI-001588, CCI-001755, CCI-000381,

CCI-000380,CCI-00382, CCI-001761, CCI-001762, CCI-002544, CCI-002545,

CCI-002546.}

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

Do not provide devices with user interfaces where one was not required.

Do not use a networked sensor or actuator where a non-networked sensor or actuator would suffice.

SECTION 25 05 11.21 Page 13

3.3.1 Non-IP Control Networks

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

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

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

3.3.2 IP Control Networks

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

3.4 SAFE MODE AND FAIL SAFE OPERATION

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

CP-12,SI-17; CCI-002855, CCI-002856, CCI-002857, CCI-002773,

CCI-002774,CCI-002775}

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

3.5 IDENTIFICATION AND AUTHENTICATION

3.5.1 User Identification and Authentication

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

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

3.5.1.1 Default Requirements for Control System Devices

For control system devices where User Identification and Authentication requirements are not otherwise indicated in this Section, User Identification and Authentication for network access to privileged accounts must be implemented by accepting and electronically verify Personal Identity Verification (PIV) credentials or inheriting identification and authentication from the operating system.

3.5.2 Authenticator Management

3.5.2.1 Authentication Type

3.5.2.1.1 Default Requirements for Control System Devices

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

SECTION 25 05 11.21 Page 14

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

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

3.5.2.2 Password-Based Authentication Requirements

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

3.5.2.2.1 Passwords for Non-Computer Devices FULLY Supporting Accounts

All non-computer devices FULLY supporting accounts and supporting password-based authentication must enforce the following requirements:

a. Minimum password length of twelve (12) characters

b. Password must contain at least one uppercase character.

c. Password must contain at least one lowercase character.

d. Password must contain at least one numeric character.

e. Password must contain at least one special character.

f. Password must have a maximum lifetime of sixty (60) days. When passwords expire, prompt users to change passwords. Do no lock accounts due to expired passwords.

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

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

3.5.2.2.2 Passwords for Web Interfaces

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

a. Minimum password length of 12 characters

b. Password must contain at least one uppercase character.

c. Password must contain at least one lowercase character.

d. Password must contain at least one numeric character.

e. Password must contain at least one special character.

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

SECTION 25 05 11.21 Page 15

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

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

3.5.2.2.3 Passwords for Devices Minimally Supporting Accounts

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

3.5.2.2.4 Password Configuration and Reporting

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

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

3.5.2.3 Hardware Token-Based Authentication Requirements

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

3.5.3 Authenticator Feedback

{For Reference Only: This subpart relates to IA-6; CCI-000206}

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

3.5.4 Device Identification and Authentication

3.5.4.1 Default Requirements for Control System Devices

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

3.5.5 Cryptographic Module Authentication

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

IA-7;CCI-000803}

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

3.6 EMERGENCY POWER

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

PE-11,(1);CCI-02955, CCI-000961}

SECTION 25 05 11.21 Page 16

Emergency power is specified in the control system and equipment specifications.

3.7 DURABILITY TO VULNERABILITY SCANNING

{For Reference Only: This subpart (and its subparts) relates to RA-5(a),(b),(c),(d); CCI-001054, CCI-001055, CCI-0010156, CCI-001641,CCI-001643, CCI-001057, CCI-001058, CCI-001059}

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

3.7.1 Default Requirements for Control System Devices

Non-computer control system devices where Durability to Vulnerability Scanning requirements are not otherwise indicated in this Section are not required to respond to scans.

3.8 DEVICES WITH CONNECTION TO MULTIPLE IP NETWORKS

Except for Ethernet switches, do not use more than one physical connection to IP networks on the same device unless doing so is both required by the project specifications and the specific application is approved. If a device with multiple IP connections is required, provide a Multiple IP Connection Device Request using the Multiple IP Connection Device Request Schedule at http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/forms-graphics-tables to request approval for each device.

3.9 SYSTEM AND COMMUNICATION PROTECTION

3.9.1 Denial of Service Protection, Process Isolation and Boundary Protection

{For Reference Only: This subpart (and its subparts) relates to SC-5,SC-39, SC-7(a); CCI-001093, CCI-002385, CCI-002386, CCI-002430, CCI-001097}

To the greatest extent practical, implement control logic in non-computer hardware and without reliance on the network.

3.10 FIELD QUALITY CONTROL

3.10.1 Tests

In addition to testing and testing support required by other Sections, provide a minimum of 16 hours of technical support for cybersecurity testing of control systems.

-- End of Section --

SECTION 25 05 11.21 Page 17

THIS PAGE INTENTIONALLY LEFT BLANK

SECTION 25 05 11.21 Page 18

Section 25 05 11.21 Attachment A

CONTROL CORRELATION IDENTIFIERS

25 05 11.21 ATTACHMENT A

FIRE and LIFE SAFETY – LOW-MOD-MOD

This attachment includes the cybersecurity control set that will be used by the Contractor when configuring the control system to comply with the requirements in UFGS 25 05 11 as defined by UFC 4- 010-06. The Contractor will use these controls to deliver a secure control system to the system owner.

Cybersecurity controls are part of the Risk Management Framework as defined in DoD 8510.01. These controls have been selected based on the C-I-A impact that was assigned.

These controls have been tailored by the Designer to fit the control system being configured. The list of controls is taken from Table H-1 for LOW-MOD-MOD controls.

The following explains the columns used in the table below:

CCI Number – this number is taken from UFC 4-010-06 Table H-1. It is mapped to a control element in NIST SP 800-53r4.

NIST SP 800-53/800-82 Control Text Indicator - NIST SP 800-53 breaks individual controls (i.e., single Control IDs) down into multiple elements and enhancements, where an enhancement is a more stringent requirement than the base control. The Control Text Indicator uniquely identifies each of these elements and enhancements. A letter indicates an element within a control, a number is an enhancement. For example, “AC-17 (4)(b)” is the second element of the fourth enhancement to AC-17.

CCI Definition – This provides the definition of the control as it is written in NIST SP 800-53r4.

Designer Implementation – The information in this column is meant to provide supplemental guidance by the Designer for the Contractor to understand how the control applies to this specific control system.

Classification – This column was completed by the Designer. The Designer reviewed each control in this CCI control set and determined which were APPLICABLE to this specific control system. The following classifications have been defined:

APPLICABLE – These are actionable controls. Controls that fall within this category must be applied by the Contractor during the installation provided the control system has the capability.

These have been identified by the…