The Cybersecurity and Infrastructure Agency (CISA) and the National Security Agency (NSA) have issued an activity alert due to the recent malicious cyber activity against critical infrastructure (CI) by exploiting internet-accessible operational technology (OT) assets.
According to CISA, "Due to the increase in adversary capabilities and activity, the criticality to U.S. national security and way of life, and the vulnerability of OT systems, civilian infrastructure makes attractive targets for foreign powers attempting to do harm to U.S. interests or retaliate for perceived U.S. aggression. OT assets are critical to the Department of Defense (DoD) mission and underpin essential National Security Systems (NSS) and services, as well as the Defense Industrial Base (DIB) and other critical infrastructure. At this time of heightened tensions, it is critical that asset owners and operators of critical infrastructure take the following immediate steps to ensure resilience and safety of U.S. systems should a time of crisis emerge in the near term."
The National Security Agency (NSA) along with the Cybersecurity and Infrastructure Security Agency (CISA) recommend that all DoD, NSS, DIB, and U.S. critical infrastructure facilities take immediate actions to secure their OT assets. Internet-accessible OT assets are becoming more prevalent across the 16 U.S. CI sectors as companies increase remote operations and monitoring, accommodate a decentralized workforce, and expand outsourcing of key skill areas such as instrumentation and control, OT asset management/maintenance, and in some cases, process operations and maintenance, adds CISA.
" Legacy OT assets that were not designed to defend against malicious cyber activities, combined with readily available information that identifies OT assets connected via the internet (e.g., Shodan, Kamerka), are creating a “perfect storm” of 1) easy access to unsecured assets, 2) use of common, open-source information about devices, and 3) an extensive list of exploits deployable via common exploit frameworks (e.g., Metasploit, Core Impact, and Immunity Canvas). Observed cyber threat activities can be mapped to the MITRE Adversarial Tactics, Techniques, and Common Knowledge (ATT&CK) for Industrial Controls Systems (ICS) framework. It is important to note that while the behavior may not be technically advanced, it is still a serious threat because the potential impact to critical assets is so high," says CISA.
Recently observed tactics, techniques, and procedures include:
- Spearphishing [T1192] to obtain initial access to the organization’s information technology (IT) network before pivoting to the OT network.
- Deployment of commodity ransomware to Encrypt Data for Impact [T1486] on both networks.
- Connecting to Internet Accessible PLCs [T883] requiring no authentication for initial access.
- Utilizing Commonly Used Ports [T885] and Standard Application Layer Protocols [T869], to communicate with controllers and download modified control logic.
- Use of vendor engineering software and Program Downloads [T843].
- Modifying Control Logic [T833] and Parameters [T836] on PLCs.
Some mitigation strategies that CISA recommends include:
1. Have a Resilience Plan for OT
Since the Ukraine cyberattack of 2015 organizations must assume in their planning of not only a malfunctioning or inoperative control system, but a control system that is actively acting contrary to the safe and reliable operation of the process. Organizations need an OT resilience plan that allows them to:
- Immediately disconnect systems from the Internet that do not need internet connectivity for safe and reliable operations. Ensure that compensating controls are in place where connectivity cannot be removed.
- Plan for continued manual process operations should the ICS become unavailable or need to be deactivated due to hostile takeover.
- Remove additional functionality that could induce risk and attack surface area.
- Identify system and operational dependencies.
- Restore OT devices and services in a timely manner. Assign roles and responsibilities for OT network and device restoration.
- Backup “gold copy” resources, such as firmware, software, ladder logic, service contracts, product licenses, product keys, and configuration information. Verify that all “gold copy” resources are stored off-network and store at least one copy in a locked tamperproof environment (e.g., locked safe).
- Test and validate data backups and processes in the event of data loss due to malicious cyber activity.
2. Exercise your Incident Response Plan
In a state of heightened tensions and additional risk and exposure, it is critical to have a well-exercised incident response plan that is developed before an incident.
- Conduct a tabletop exercise, including executive personnel, to test your existing incident response plan.
- Be sure to include your public affairs and legal teams in your exercise in addition to your IT, OT, and executive management.
- Discuss key decisions points in the response plan and identify who has the authority to make key decisions under what circumstances.
- Ensure your plan takes into account a scenario inclusive of the TTPs above and where the control system is actively operating counter to safe and reliable operations.
- Partner with third parties for support. Review service contracts and government services for emergency incident response and recovery support.
3. Harden Your Network
- Remote connectivity to OT networks and devices provides a known path that can be exploited by cyber actors. External exposure should be reduced as much as possible.
- Remove access from networks, such as non-U.S. IP addresses, if applicable, that do not have legitimate business reasons to communicate with the system.
- Use publicly available tools, such as Shodan, to discover internet-accessible OT devices. Take corrective actions to eliminate or mitigate internet-accessible connections immediately. Best practices include:
- Fully patch all Internet-accessible systems.
- Segment networks to protect PLCs and workstations from direct exposure to the internet. Implement secure network architectures utilizing demilitarized zones (DMZs), firewalls, jump servers, and/or one-way communication diodes.
- Ensure all communications to remote devices use a virtual private network (VPN) with strong encryption further secured with multifactor authentication.
- Check and validate the legitimate business need for such access.
- Filter network traffic to only allow IP addresses that are known to need access, and use geo-blocking where appropriate.
- Connect remote PLCs and workstations to network intrusion detection systems where feasible.
- Capture and review access logs from these systems.
- Encrypt network traffic preferably using NIAP-validated VPN products and/or CNSSP- or NIST-approved algorithms when supported by OT system components to prevent sniffing and man-in-the-middle tactics. Available at: https://niap-ccevs.org.
- Use the validated inventory to investigate which OT devices are internet-accessible.
- Use the validated inventory to identify OT devices that connect to business, telecommunications, or wireless networks.
- Secure all required and approved remote access and user accounts.
- Prohibit the use of default passwords on all devices, including controllers and OT equipment.
- Remove, disable, or rename any default system accounts wherever possible, especially those with elevated privileges or remote access.
- Enforce a strong password security policy (e.g., length, complexity).
- Require users to change passwords periodically, when possible.
- Enforce or plan to implement two-factor authentication for all remote connections.
- Harden or disable unnecessary features and services (e.g., discovery services, remote management services, remote desktop services, simulation, training, etc.).
4. Create an Accurate “As-operated” OT Network Map Immediately
An accurate and detailed OT infrastructure map provides the foundation for sustainable cyber-risk reduction.
- Document and validate an accurate “as-operated” OT network map.
- Create an asset inventory.
- Include OT devices assigned an IP address.
- Include software and firmware versions.
- Include process logic and OT programs.
- Include removable media.
- Include standby and spare equipment.
- Identify all communication protocols used across the OT networks.
- Investigate all unauthorized OT communications.
- Catalog all external connections to and from the OT networks.
- Include all business, vendor, and other remote access connections.
- Review service contracts to identify all remote connections used for third-party services.
5. Understand and Evaluate Cyber-risk on “As-operated” OT Assets
Informed risk awareness can be developed using a variety of readily available resources, many of which include specific guidance and mitigations.
- Use the validated asset inventory to investigate and determine specific risk(s) associated with existing OT devices and OT system software.
- Vendor-specific cybersecurity and technical advisories.
- CISA Advisories .
- Department of Homeland Security – Cybersecurity and Infrastructure Security Agency Cyber Security Evaluation Tool .
- MITRE Common Vulnerabilities and Exposures (CVE) for both Information Technology and OT devices and system software . Available at https://cve.mitre.org.
- National Institute of Standards and Technology – National Vulnerability Database . Available at https://nvd.nist.gov.
- Implement mitigations for each relevant known vulnerability, whenever possible (e.g., apply software patches, enable recommended security controls, etc.).
- Audit and identify all OT network services (e.g., system discovery, alerts, reports, timings, synchronization, command, and control) that are being used.
- Use vendor provided programming and/or diagnostic tools and procedures.
6. Implement a Continuous and Vigilant System Monitoring Program
A vigilant monitoring program enables system anomaly detection, including many malicious cyber tactics like “living off the land” techniques within OT systems.
- Log and review all authorized external access connections for misuse or unusual activity.
- Monitor for unauthorized controller change attempts.
- Implement integrity checks of controller process logic against a known good baseline.
- Where possible, ensure process controllers are prevented from remaining in remote program mode while in operation.
- Lock or limit set points in control processes to reduce the consequences of unauthorized controller access.