SCADA Worm Case Study Example | Topics and Well Written Essays - 1250 words

SCADA Worm - Case Study Example It is as well the first worm which encompasses a programmable logic controller (PLC) root kit. Additionally, in the beginning Stuxnet worm dispersed without rhyme or reason; however, it incorporated a high level and sophisticated malware payload that was particularly designed to target Siemens supervisory control and data acquisition (or simply SCADA) systems that are intended to manage and observe detailed industrial procedures. In this scenario, Stuxnet infects PLCs by weakening the Step-7 software system that is employed to reprogram these systems (O'Murchu, 2012; Keizer, 2009; John, 2010; Masood, Um-e-Ghazia, & Anwar, 2011). This paper discusses the impact and the vulnerability of the SCADA/Stuxnet Worm in the critical infrastructure of the United States. This paper will also discuss some of the important methods to mitigate the vulnerabilities. This research will investigate the levels of responsibility between government agencies and the private sector for mitigating threats an d vulnerabilities. Vulnerability of the SCADA This section outlines some of the major vulnerabilities regarding SCADA. Various research studies have shown that a range of vulnerabilities still exist inside SCADA systems. In this scenario, the majority of extensively publicized security based attacks on SCADA systems have taken place over the past few years as well as a large number of reports have been produced confidentially and publicly admitting issues and challenges securing similar systems. For example, SCADA system’s major vulnerability revealed itself when Japanese groups purportedly attacked control systems organizing commuter trains. Another major vulnerability attack was the Slammer worm that immobilized a security monitoring arrangement at Davis-Besse nuclear power plant located in the Oak Harbor, Ohio in the year 2003 (Swan, 2012; Fidler, 2011; Rebane, 2011). In addition, there are so many other instances of this attack, for instance a major vulnerability taking p lace due to an illegal intrusion through a previous, disgruntled worker into a worldwide chemical corporation attempting to cause damage. In the same way, Ira Winkler’s security based vulnerability instance in SCADA happened while conducting experiments at a power corporation network that was so flourishing that the test had to be stopped. Another major vulnerability in SCADA was identified due to the Sobig computer virus that influenced the CSX train signaling arrangement in the year 2003. Additionally, the disruption in collaboration and communication happened in Worcester, Massachusetts Air Traffic Communications system in 1997. SCADA vulnerability also happened due to foreign actors, where a cyber attacked a United States water plant in an obvious effort to achieve access as well as probably control of the significant corporate arrangement. In addition, the latest Stuxnet Worm that spreads extensively searching for exact SCADA applications and systems, supposedly attackin g Iran’s Natanz nuclear arrangement, allegedly reasoning 1,000 centrifuges to spin out of control (Swan, 2012; Fidler, 2011; Rebane, 2011). Moreover, these above stated different vulnerabilities could have taken place due to some of the reasons (Swan, 2012; Fidl