{"id":301,"date":"2024-11-17T20:35:16","date_gmt":"2024-11-17T20:35:16","guid":{"rendered":"https:\/\/sites.wp.odu.edu\/matt-surratt\/?p=301"},"modified":"2024-11-17T20:35:16","modified_gmt":"2024-11-17T20:35:16","slug":"overview-of-scada-vulnerabilities-and-mitigation-of-risks","status":"publish","type":"post","link":"https:\/\/sites.wp.odu.edu\/matt-surratt\/2024\/11\/17\/overview-of-scada-vulnerabilities-and-mitigation-of-risks\/","title":{"rendered":"Overview of SCADA Vulnerabilities and Mitigation of Risks"},"content":{"rendered":"\n<p>Overview of SCADA Vulnerabilities and Mitigation of Risks<\/p>\n\n\n\n<p><br>Supervisory control and data acquisition (SCADA) systems are unique to the critical infrastructure system they control. This unique configuration of the SCADA systems also makes the mitigation of vulnerabilities to be unique as well. In this write-up, I will discuss vulnerabilities associated with critical infrastructure systems focusing on implementation issues and security misconfiguration issues. Then, we will touch base on different tools available to critical infrastructure systems to mitigate cybersecurity risks. <\/p>\n\n\n\n<p><br>Vulnerabilities<\/p>\n\n\n\n<p><br>The evolution of SCADA systems has encouraged industrial control systems (ICS) to implement the use of commercial off-the-shelf (COTS) hardware and software. This trend has inadvertently increased the attack surface in SCADA systems that previously did not exist in air-gapped ICS environments (Alanazi et al., 2023). The increase in vulnerabilities due to the use of COTS hardware and software paired with the vulnerabilities of SCADA systems older infrastructure still in use, create a very significant taxonomy of SCADA vulnerabilities. <\/p>\n\n\n\n<p><br>Implementation Issues<\/p>\n\n\n\n<p><br>The vulnerabilities caused by implementation issues are flaws in the architecture of the programming. This section of the write-up briefly lists and explains vulnerabilities caused by implementation issues (Alanazi et al., 2023):<br>\u2022 Lack of input validation occurs when inputs are not validated to be safe or correct. <br>\u2022 Improper validation of array index occurs because lacking input validation from upstream components are not checked by the software.<br>\u2022 Untrusted search paths exploit can lead to data link library (DLL) hijacking.<br>\u2022 Improper limitation of memory buffer can lead to buffer overflow or an off by one error when the memory buffer is used outside of its limits.<br>\u2022 Improper control flow management which can create modified execution logic due to code not effectively managing flow. This can lead to race conditions, time-of-check time-of-use vulnerability, server-side request forgery, and hidden functionality.<\/p>\n\n\n\n<p><br>Security Misconfiguration Issues<\/p>\n\n\n\n<p><br>The vulnerabilities caused by security misconfiguration issues are the result of implementation of weak security techniques. This section of the write-up briefly lists and explains vulnerabilities caused by security misconfiguration issues (Alanazi et al., 2023):<br>\u2022 Protection mechanism failure caused by lack of encryption, inadequate encryption strength, insufficient random values, and insufficient verification of data authenticity.<br>\u2022 Weak password requirements: a successful exploit leads to privilege escalation.<br>\u2022 Improper access control allows access to critical resources by mistake.<br>\u2022 Improper authentication occurs when the software does not validate the identity of a user and can cause: Bypass authentication, use of hard-coded credentials, authentication bypass by capture-replay, lack of certificate validation, default password configuration, improper restriction of invalid authentication attempts, improper authorization, and unsalted hash value.<\/p>\n\n\n\n<p><br>Mitigation Tools<\/p>\n\n\n\n<p><br>The differences between ICS and IT systems prevent IT mitigation mechanisms from being utilized in ICS systems. This is because of the conflicts with the ICS system requirements. The following cybersecurity controls can help mitigate risk on SCADA systems (Alanazi et al., 2023):<br>\u2022 Assets management inventory can be utilized to discover unauthorized devices that are connected to the network.<br>\u2022 Vulnerability assessment and management can help determine entries that attackers may use.<br>\u2022 Using safe memory languages such as Rust.<br>\u2022 Integrity checks can prevent attempts to crash a server by the use of DoS and DDoS attacks.<br>\u2022 Input validation by employing a whitelist approach.<br>\u2022 Output encoding that transforms a user input into a safe form.<br>\u2022 Privilege access management to prevent privilege escalation.<br>\u2022 Credential management: avoid using default password configurations and passwords should be salted.<br>\u2022 Intrusion detection, prevention, and prediction systems.<\/p>\n\n\n\n<p><br>Conclusion<\/p>\n\n\n\n<p><br>The uniqueness of SCADA systems creates individual challenges that need to be addressed for every critical infrastructure system.  Utilizing tools like the NIST framework and MITRE\u2019s Common Weakness Enumeration (CWE), will help discover vulnerabilities, and create a plan to mitigate cybersecurity risks.<br><br>References<br>Alanazi, M., Mahmood, A., &amp; Chowdhury, M. J. M. (2023). SCADA vulnerabilities and attacks: A review of the state\u2010of\u2010the\u2010art and open issues. Computers &amp; security, 125(103028), 1-29. https:\/\/doi.org\/10.1016\/j.cose.2022.103028<br><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Overview of SCADA Vulnerabilities and Mitigation of Risks Supervisory control and data acquisition (SCADA) systems are unique to the critical infrastructure system they control. This unique configuration of the SCADA systems also makes the mitigation of vulnerabilities to be unique as well. In this write-up, I will discuss vulnerabilities associated with critical infrastructure systems focusing&#8230; <\/p>\n<div class=\"link-more\"><a href=\"https:\/\/sites.wp.odu.edu\/matt-surratt\/2024\/11\/17\/overview-of-scada-vulnerabilities-and-mitigation-of-risks\/\">Read More<\/a><\/div>\n","protected":false},"author":29497,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","wds_primary_category":5},"categories":[5],"tags":[4,6],"_links":{"self":[{"href":"https:\/\/sites.wp.odu.edu\/matt-surratt\/wp-json\/wp\/v2\/posts\/301"}],"collection":[{"href":"https:\/\/sites.wp.odu.edu\/matt-surratt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sites.wp.odu.edu\/matt-surratt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/matt-surratt\/wp-json\/wp\/v2\/users\/29497"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/matt-surratt\/wp-json\/wp\/v2\/comments?post=301"}],"version-history":[{"count":2,"href":"https:\/\/sites.wp.odu.edu\/matt-surratt\/wp-json\/wp\/v2\/posts\/301\/revisions"}],"predecessor-version":[{"id":305,"href":"https:\/\/sites.wp.odu.edu\/matt-surratt\/wp-json\/wp\/v2\/posts\/301\/revisions\/305"}],"wp:attachment":[{"href":"https:\/\/sites.wp.odu.edu\/matt-surratt\/wp-json\/wp\/v2\/media?parent=301"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/matt-surratt\/wp-json\/wp\/v2\/categories?post=301"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/matt-surratt\/wp-json\/wp\/v2\/tags?post=301"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}