6. Critical Infrastructure Securitybe needed, something that is not even supported by most SCADA systems andtheir backbones.Subsequent milestones were Duqu (2011) and Flame (2012), both designedwith intelligence gathering purposes, although Flame is more opportunistic asit spreads also to mobile devices and uses ambient sensors (e.g., microphone)to steal information. These are two examples of the second most importantapplication of cyber weapons: espionage. Due to the similarity of some codefragments of Duqu, Flame and the variants of Stuxnet, it is not unrealistic toconclude that Duqu was designed to be the precursor of the next Stuxnet [127],to gather intelligence about CI targets.Whether Flame will be the precursor of the often p<strong>red</strong>icted “year of cyberattacks (2013),” remains to be seen. As mentioned in Section 6.7, recentindustrial research efforts are moving toward this direction by deployinghoneypot ICSs to collect object evidence of attacks, which would be of help inanswering these questions.6.4 What Is the Worst That Can Happen?The discovery of Stuxnet, and the related events, concretelyshowed to the security the potential impactof attacks against CIs; this significantly increasedthe concerns and interest of the community. Today,vulnerabilities and attacks against CIs continue to bediscove<strong>red</strong> every week in the wild. A recent case isdated February 23, 2013, when the US Departmentof Homeland Security (DHS) reported that in a cyberattackagainst 23 natural gas pipeline operators,crucial information was stolen [71]. Although theDHS report, not yet disclosed to the public, does notmention the sources of the espionage, the digital signatures of the attackshave been identified by independent researchers as belonging to a particulargroup recently linked to China’s military (although China has denied theallegations) [72]. Unfortunately, these attacks will continue to spread. This iscorroborated by the increased amount of incidents reported and, more importantly,by the recent cyber-espionage cases, which are likely to be the precursorof more targeted and sophisticated attacks.In addition to (intentional) attacks and unintentional incidents in ICSs,which both impact the physical world, we believe that unintentionally causedfailures are also bound to happen. Instability, natural and artificial faults [259]or unexpected conditions in the physical systems, which eventually translateinto “signals,” processed by ICSs to take proper control actions, can44
6.5. State of the Artretroactively lead to unexpected conditions in the ICS software, which couldultimately lead to failure loops with devastating consequences.These premises allow us to draw a global picture of what could happenin the future if the current menaces continue their evolution. The word“cyberwar” [119] appears frequently in the majority of recent threat reportsand news subsections. This word should be used with care, because, as ofMarch 2013, there is no strong evidence as to whether the aforementionedthreats have translated into concrete, planned attacks, as opposed to “testing”performed by the attackers (or governments). On the other hand, the futurescenario is frightening as it includes disasters caused by viruses like Stuxnetthat infect critical control systems, causing such events as traffic accidents, trainor plane collisions, nuclear power plans meltdowns or explosions. Needless tosay, such attacks may end up with a massive loss of life and an exacerbate theglobal financial crisis. Ultimately, the economy is also a critical system, withstrong impact on the physical world, which is highly dependent on computers.Once attackers have gained control of a CI, they can operate it at their will.6.5 State of the ArtRecent EU-funded research projects concerning the security of CIs are CRISALIS(http://www.crisalis-project.eu/), which focuses on practical aspects ofdetection of vulnerabilities and attacks, and SESAME (https://www.sesameproject.eu/),with the same focus, although more oriented toward observingthe CIs from the physical side (mainly on smart grids). We also refer the readerto recent work on attack assessment [381], analysis [376] (on espionage attacktriage), survey and challenges of smart grid security [392] and critique [314].Recent reference <strong>book</strong>s worth mentioning are [146, 328].With system security of CIs being a young research field, a few notablepublications—reviewed in the remainder of this section—appea<strong>red</strong> in the lasttwo years at leading conferences. Most of the literature about detection orprotection methods focuses on SCADA protocols or on smart grids.6.5.1 Anomaly Detection of SCADA Events and Protocols[203, 204] address the detection of process-related threats in ICS used in CIs.These threats take place when an attacker impersonates a user to perform actionsthat appear legitimate although they are intended to disrupt the industrialprocess. They tested their approach on 101,025 log entries to detect anomalouspatterns of user actions. This preliminary case study suggests that the approachis effective. One year later the same authors extended their work beyond loganalysis and are concentrating on binary protocols, including those adopted bySCADA implementations (e.g., MODBUS). The motivation behind [68] is thatseveral complex and high-impact attacks specifically targeting binary protocols45
- 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 50 and 51: 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