Property:Has mitigation description

From attackics
Jump to navigation Jump to search

This is a property of type Text.

Showing 20 pages using this property.
B
Restrict unauthorized devices from accessing serial comm ports.  +
Ensure devices have an alternative method for communicating in the event that a valid COM port is unavailable.  +
Implement network allowlists to minimize serial comm port access to only authorized hosts, such as comm servers and RTUs.  +
Devices should authenticate all messages between master and outstation assets.  +
Utilize network allowlists to restrict unnecessary connections to network devices (e.g., comm servers, serial to ethernet converters) and services, especially in cases when devices have limits on the number of simultaneous sessions they support.  +
Segment operational assets and their management devices based on their functional role within the process. Enabling more strict isolation to more critical control and operational information within the control environment.[[CiteRef::Guidance - NIST SP800-41]][[CiteRef::Guidance - NIST SP800-82]][[CiteRef::Guidance - DHS Defense in Depth - 201609]][[CiteRef::mitigation - SANS whitelisting]]  +
Allow/denylists can be used to block access when excessive I/O connections are detected from a system or device during a specified time period.  +
C
All field controllers should restrict operating mode changes to only required authenticated users (e.g., engineers, field technicians), preferably through implementing a role-based access mechanism. Further, physical mechanisms (e.g., keys) can also be used to limit unauthorized operating mode changes.  +
Authenticate connections from software and devices to prevent unauthorized systems from accessing protected management functions.  +
All field controllers should require users to authenticate for all remote or local management sessions. The authentication mechanisms should also support <span class="smw-format list-format "><span class="smw-row"><span class="smw-field"><span class="smw-value">[[Mitigation/M0936]]</span></span></span></span>, <span class="smw-format list-format "><span class="smw-row"><span class="smw-field"><span class="smw-value">[[Mitigation/M0927]]</span></span></span></span>, and <span class="smw-format list-format "><span class="smw-row"><span class="smw-field"><span class="smw-value">[[Mitigation/M0918]]</span></span></span></span>.  +
Protocols used for device management should authenticate all network messages to prevent unauthorized system changes.  +
Segment operational network and systems to restrict access to critical system functions to predetermined management systems.[[CiteRef::Guidance - DHS Defense in Depth - 201609]]  +
Authenticate all access to field controllers before authorizing access to, or modification of, a device's state, logic, or programs. Centralized authentication techniques can help manage the large number of field controller accounts needed across the ICS.  +
Use host-based allowlists to prevent devices from accepting connections from unauthorized systems. For example, allowlists can be used to ensure devices can only connect with master stations or known management/engineering workstations.[[CiteRef::Guidance - DHS Defense in Depth - 201609]]  +
Execution prevention may block malicious software from accessing protected resources through the command line interface.  +
Consider removing or restricting features that are unnecessary to an asset's intended function within the control environment.  +
Ensure that unnecessary ports and services are closed to prevent risk of discovery and potential exploitation.  +
All field controllers should require users to authenticate for all remote or local management sessions. The authentication mechanisms should also support <span class="smw-format list-format "><span class="smw-row"><span class="smw-field"><span class="smw-value">[[Mitigation/M0936]]</span></span></span></span>, <span class="smw-format list-format "><span class="smw-row"><span class="smw-field"><span class="smw-value">[[Mitigation/M0927]]</span></span></span></span>, and <span class="smw-format list-format "><span class="smw-row"><span class="smw-field"><span class="smw-value">[[Mitigation/M0918]]</span></span></span></span>.  +
Configure internal and external firewalls to block traffic using common ports that associate to network protocols that may be unnecessary for that particular network segment.  +
Network intrusion detection and prevention systems that use network signatures to identify traffic for specific adversary malware can be used to mitigate activity at the network level. Signatures are often for unique indicators within protocols and may be based on the specific protocol used by a particular adversary or tool and will likely be different across various malware families and versions. Adversaries will likely change tool C2 signatures over time or construct protocols in such a way as to avoid detection by common defensive tools.[[CiteRef::University of Birmingham C2]]  +