6. Critical Infrastructure Security6.1 What Is the Problem?From the above premises, it is clear that well-known challenging threats such asmalware, botnets, or denial of service attacks, which have been compromisingthe security of Internet-connected devices, are likely to become threats for CIsas well. In contrast to traditional Internet-connected devices, CIs can take tangibleactions in the physical environment, thus posing serious safety risks, alongwith the possibility of production loss, equipment damage and informationtheft. The first incident on a SCADA system dates back to 1982, when a trojansupposedly infected the ICS that controlled the so-called “Siberian Pipeline”and caused an explosion equivalent to 3 kilotons of TNT [278]. Further exacerbatingthis scenario, today’s SCADA-controlled systems are widespread,given the market traction of smart grids and smart buildings, and thus moreappealing to offenders [361, 392, 395]. Although SCADA implementations canvary from vendor to vendor, the specifications of the control protocols (e.g.,PLC) are publicly available [32] and the devices can be acqui<strong>red</strong> by anyonewho has sufficient funding. In addition, the control software runs on generalpurpose OSs (e.g., Windows), and devices were originally deployed in isolatedenvironments where network connectivity was not conside<strong>red</strong>. Needless tosay, SCADA software comes with several serious vulnerabilities [47], most ofthem caused by buffer overflow and input validation bugs, which culminatedin experts describing SCADA security as “laughable” [51]. Unfortunately,these vulnerable ICS are publicly accessible over the Internet. One such centerof exploits is called SHODAN [49], a search engine tailo<strong>red</strong> at finding andexposing online embedded devices such as webcams, routers, power plantsor even wind turbines. Unsurprisingly, “scada” is the most searched term onSHODAN. How well these exploits perform in real-world scenarios, however,is hard to estimate.According to the information that CERTS and governments collected, offendersincreasingly targeted critical infrastructures of countries: The IndustrialControl Systems-Cyber Emergency Response Team (ICS-CERT) responded to198 incidents against CIs in 2012, 52% more than the previous year. The twomost impacted sectors in 2012 are energy (41% of reported incidents) andwater (15%) [45]. There are debates within the research community aboutthe accuracy of the answers collected in a recent survey conducted by SANSamong industries and organizations that adopt SCADA and process-controlsystems [74]. Despite such debates, the survey corroborates the anecdotalbelief that SCADA and ICS adopters are aware of the security risks. Roughly50% of the participants reported that they were taking countermeasures thatincluded patching, access control and log analysis. Unfortunately, the PLClayer appears to be a weak spot, where it is often difficult to deploy propermonitoring mechanisms.42
6.2. Who Is Going to Be Affected?6.2 Who Is Going to Be Affected?Several sectors are theoretically exposed to the aforementioned threats. Basically,every adopter of network-connected process-control systems is likely tobe affected. Public health, energy production, telecommunication and publicwater supply are just a few examples of systems that will be under threatunless they deploy adequate countermeasures.Furthermore, an aggravating factor is, that today’s CIs are getting larger.With the increasing adoption of smart grids, virtually everyone, even individuals,is part of the CPS ecosystem. Cyber attacks are therefore likely to affecteveryone. Even when ordinary people are not directly affected by failuresof modern CPSs, they are still susceptible to cascade effects. Since sectorsadopting ICSs are also influenced by cultural, political or economical factors,the impact of an attack is more widespread than in an isolated system thatuses ICSs, for instance, to control production.6.3 What Is Expected to Happen?The critical nature of CIs renders them intriguing targets with disastrousconsequences, including loss of human lives. In some respects, p<strong>red</strong>ictionsfrom 3 years ago can already be observed in the wild. Yet, it appears thatthe actors behind the weekly reported threats are probing without causingdeliberate damage. For instance, the Stuxnet [176] infection of 2009–2010,which influenced thousands of devices, reached very sensitive targets. A recentreport [272] describes that earlier versions of the sophisticated cyber weaponcontained other known versions of the malicious code that were reportedlyunleashed by the US and Israel several years ago, in an attempt to sabotageIran’s nuclear program. This indicates that Stuxnet was active about two yearsbefore the main incident. It also implies that none of the two campaigns ofStuxnet (2007 and 2009–2010) had a serious impact on Iran’s nuclear facilities,the avowed main target of the attack. Even though Stuxnet essentially failed,an important fact remains: Stuxnet was developed (by offices of nation states,as recently confirmed officially [69, 70], although the US government has neveradmitted using cyber weapons) with careful planning and the use of productspecific0-day vulnerabilities, and it had the potential and the opportunity tocause serious damage on a national level.The widespread belief that standard protection tools (e.g., VPNs, firewalls,etc.) would suffice to secure network-connected SCADA equipment is justa myth. In fact, Stuxnet reached its targets from an infected USB drive. Itthen used other exploits and local-network probing techniques to find andinfect other targets within the production environment. This attack vectoris impossible to restrict with network-based access control alone. Instead, afull-blown security infrastructure, including access and account policies would43
- Page 1: SEVENTH FRAMEWORK PROGRAMMETHERED B
- Page 4 and 5: The Red Book. ©2013 The SysSec Con
- Page 7 and 8: PrefaceAfter the completion of its
- Page 9 and 10: Contents1 Executive Summary 32 Intr
- Page 11 and 12: 1 Executive SummaryBased on publish
- Page 13: 1.2. Grand Challenges4. will have t
- Page 16 and 17: 2. Introductionwho want to get at t
- Page 18 and 19: 2. Introduction• Although conside
- Page 20 and 21: 2. Introductionfuture, where each a
- Page 22 and 23: 2. Introductiondrones), such sensor
- Page 24 and 25: 2. Introductioncover our energy nee
- Page 27: Part I: Threats Identified
- Page 30 and 31: 3. In Search of Lost Anonymity3.2 W
- Page 32 and 33: 3. In Search of Lost Anonymityguide
- Page 35 and 36: 4 Software VulnerabilitiesExtending
- Page 37 and 38: 4.1. What Is the Problem?infrastruc
- Page 39 and 40: 4.5. State of the Artparts of criti
- Page 41: 4.7. Example Problemstem mitigation
- Page 44 and 45: 5. Social Networks5.1 Who Is Going
- Page 46 and 47: 5. Social Networksby such an applic
- Page 48 and 49: 5. Social Networksdisasters. This r
- Page 52 and 53: 6. Critical Infrastructure Security
- Page 54 and 55: 6. Critical Infrastructure Security
- Page 56 and 57: 6. Critical Infrastructure Security
- Page 59 and 60: 7 Authentication and AuthorizationH
- Page 61 and 62: 7.2. Who Is Going to Be Affected?so
- Page 63 and 64: 7.5. State of the ArtFinally, ident
- Page 65 and 66: 7.6. Research Gapshashes and evalua
- Page 67 and 68: 8 Security of Mobile DevicesIn an e
- Page 69 and 70: 8.3. What Is the Worst That Can Hap
- Page 71 and 72: 8.4. State of the ArtAll the other
- Page 73: 8.6. Example Problemserated anomaly
- Page 76 and 77: 9. Legacy Systemsthe execution of a
- Page 78 and 79: 9. Legacy Systemsparts of the progr
- Page 81 and 82: 10 Usable SecurityKeys, locks, and
- Page 83 and 84: 10.4. What Is the Worst That Can Ha
- Page 85 and 86: 10.6. Research Gaps10.6 Research Ga
- Page 87: 10.7. Example Problemsof value for
- Page 90 and 91: 11. The Botnet that Would not DieNu
- Page 92 and 93: 11. The Botnet that Would not Diefa
- Page 94 and 95: 11. The Botnet that Would not Dieti
- Page 96 and 97: 12. Malwarethan 128 million malware
- Page 98 and 99: 12. Malwareequipped with auto-updat
- Page 100 and 101:
12. Malwarethe introduction of App
- Page 102 and 103:
13. Social Engineering and Phishing
- Page 104 and 105:
13. Social Engineering and Phishing
- Page 106 and 107:
13. Social Engineering and Phishing
- Page 108 and 109:
13. Social Engineering and Phishing
- Page 111 and 112:
14 Grand ChallengesOne of the most
- Page 113:
Part II: Related Work
- Page 116 and 117:
15. A Crisis of Prioritization•
- Page 118 and 119:
16. Forwardare accessible from the
- Page 120 and 121:
16. ForwardRecommendation 4: “The
- Page 122 and 123:
17. Federal Plan for Cyber Security
- Page 124 and 125:
17. Federal Plan for Cyber Security
- Page 126 and 127:
18. EffectsPlus18.1 Roadmap Structu
- Page 128 and 129:
18. EffectsPlus18.6 Identified Prio
- Page 130 and 131:
19. Digital GovernmentThe roadmap o
- Page 132 and 133:
20. Horizon2020• “Making cyber
- Page 135 and 136:
21 Trust in the Information Society
- Page 137:
21.2. Recommendationsallows for the
- Page 140 and 141:
22. ENISA Threat Landscape2. Malwar
- Page 142 and 143:
22. ENISA Threat LandscapeSocial Te
- Page 144 and 145:
22. ENISA Threat Landscapewriters w
- Page 146 and 147:
23. Cyber Security Research Worksho
- Page 149 and 150:
24 Cyber Security Strategy of theEu
- Page 151 and 152:
24.2. Strategic PrioritiesProposed
- Page 153 and 154:
25 The Dutch National Cyber Securit
- Page 155 and 156:
25.1. ContextsInternet (e.g., smart
- Page 157 and 158:
25.1. Contextsdefensive approaches
- Page 159 and 160:
25.2. Research Themesand radio broa
- Page 161 and 162:
25.2. Research Themesconsists of se
- Page 163 and 164:
25.2. Research ThemesRisk managemen
- Page 165 and 166:
AMethodologiesIn this appendix we o
- Page 167 and 168:
BSysSec Threats Landscape Evolution
- Page 169 and 170:
B.4. SysSec 2013 Threats LandscapeT
- Page 171 and 172:
B.4. SysSec 2013 Threats LandscapeS
- Page 173 and 174:
Bibliography[1] 10 Questions for Ke
- Page 175 and 176:
Bibliography[45] SCADA & Security o
- Page 177 and 178:
Bibliography[88] A. Avizienis, J.-C
- Page 179 and 180:
Bibliography[130] G. Cluley. 600,00
- Page 181 and 182:
Bibliography[172] D. Evans. Top 25
- Page 183 and 184:
Bibliography[214] ICS-CERT. Monthly
- Page 185 and 186:
Bibliography[253] C. Lever, M. Anto
- Page 187 and 188:
Bibliography[291] Mozilla. Browseri
- Page 189 and 190:
Bibliography[329] F. Raja, K. Hawke
- Page 191 and 192:
Bibliography[370] T. Telegraph. Bog
- Page 193 and 194:
Bibliography[407] W. Yang, N. Li, Y