CM-7: LEAST FUNCTIONALITY
TAILORED FOR INDUSTRIAL CONTROL SYSTEMS
ICS Control Baselines:
- Low
- Moderate
- High
The organization:
- a. Configures the information system to provide only essential capabilities; and
- b. Prohibits or restricts the use of the following functions, ports, protocols, and/or services: [Assignment: organization-defined prohibited or restricted functions, ports, protocols, and/or services].
SUPPLEMENTAL GUIDANCE
Information systems can provide a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). Additionally, it is sometimes convenient to provide multiple services from single information system components, but doing so increases risk over limiting the services provided by any one component. Where feasible, organizations limit component functionality to a single function per device (e.g., email servers or web servers, but not both). Organizations review functions and services provided by information systems or individual components of information systems, to determine which functions and services are candidates for elimination (e.g., Voice Over Internet Protocol, Instant Messaging, auto-execute, and file sharing). Organizations consider disabling unused or unnecessary physical and logical ports/protocols (e.g., Universal Serial Bus, File Transfer Protocol, and Hyper Text Transfer Protocol) on information systems to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling. Organizations can utilize network scanning tools, intrusion detection and prevention systems, and end-point protections such as firewalls and host-based intrusion detection systems to identify and prevent the use of prohibited functions, ports, protocols, and services.
ICS SUPPLEMENTAL GUIDANCE
Ports, as used in NIST SP 800-53 Rev. 4, are part of the address space in network protocols and are often associated with specific protocols or functions. As such, ports are not relevant to non- routable protocols and devices. When dealing with non-routable and non-addressable protocols and devices, prohibiting or restricting the use of specified functions, protocols, and/or services must be implemented for the (sub)system granularity that is available (e.g., at a low level, interrupts could be disabled; at a high level, set points could be made read-only except for privileged users). Example compensating controls include employing non-automated mechanisms or procedures.
RELATED CONTROLS: CM-7
CONTROL ENHANCEMENTS
CM-7 (1) LEAST FUNCTIONALITY | PERIODIC REVIEW
ICS Control Baselines:
- Low (ADDED)
- Moderate
- High
The organization:
- (a) Reviews the information system [Assignment: organization-defined frequency] to identify unnecessary and/or nonsecure functions, ports, protocols, and services; and
- (b) Disables [Assignment: organization-defined functions, ports, protocols, and services within the information system deemed to be unnecessary and/or nonsecure].
Supplemental Guidance:
The organization can either make a determination of the relative security of the function, port, protocol, and/or service or base the security decision on the assessment of other entities. Bluetooth, FTP, and peer-to-peer networking are examples of less than secure protocols.
No ICS Supplemental Guidance.
Rational: Periodic review and removal of unnecessary and/or non-secure functions, ports, protocols, and services are added to the LOW baseline because many of the LOW impact ICS components could adversely affect the systems to which they are connected.
RELATED CONTROLS: CM-7 (1)
CM-7 (2) LEAST FUNCTIONALITY | PREVENT PROGRAM EXECUTION
ICS Control Baselines:
- Moderate
- High
The information system prevents program execution in accordance with [Selection (one or more): [Assignment: organization-defined policies regarding software program usage and restrictions]; rules authorizing the terms and conditions of software program usage].
Supplemental Guidance: NONE
No ICS Supplemental Guidance.
RELATED CONTROLS: CM-7 (2)
CM-7 (3) LEAST FUNCTIONALITY | REGISTRATION COMPLIANCE
ISC Control Baseline:
- REMOVED Moderate
The organization ensures compliance with [Assignment: organization-defined registration requirements for functions, ports, protocols, and services].
Supplemental Guidance:
Organizations use the registration process to manage, track, and provide oversight for information systems and implemented functions, ports, protocols, and services.
CM-7 (4) LEAST FUNCTIONALITY | UNAUTHORIZED SOFTWARE/BLACKLISTING
ICS Control Baselines:
- Moderate (ADDED)
- High
The organization:
- (a) Identifies [Assignment: organization-defined software programs not authorized to execute on the information system];
- (b) Employs an allow-all, deny-by-exception policy to prohibit the execution of unauthorized software programs on the information system; and
- (c) Reviews and updates the list of unauthorized software programs [Assignment: organization-defined frequency].
Supplemental Guidance:
The process used to identify software programs that are not authorized to execute on organizational information systems is commonly referred to as blacklisting. Organizations can implement CM-7 (5) instead of this control enhancement if whitelisting (the stronger of the two policies) is the preferred approach for restricting software program execution.
RELATED CONTROLS: CM-7 (4)
CM-7 (5) LEAST FUNCTIONALITY | AUTHORIZED SOFTWARE/WHITELISTING
The organization:
- (a) Identifies [Assignment: organization-defined software programs authorized to execute on the information system];
- (b) Employs a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the information system; and
- ( c) Reviews and updates the list of authorized software programs [Assignment: organization-defined frequency].
Supplemental Guidance:
The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting. In addition to whitelisting, organizations consider verifying the integrity of white-listed software programs using, for example, cryptographic checksums, digital signatures, or hash functions. Verification of white-listed software can occur either prior to execution or at system startup.
Whitelisting, CM-7 (5), is more effective than blacklisting, CM-7 (4). The set of applications that run in ICS is essentially static, making whitelisting practical. ICS-CERT recommends deploying application whitelisting on ICS. Reference: http://ics-cert.us- cert.gov/tips/ICS-TIP-12-146-01B.
RELATED CONTROLS: CM-7 (5)
REFERENCES:
- NIST Special Publication 800-82
- DoD Instruction 8551.01