syssec_red_book

Recommendations

Info

4. Software Vulnerabilitiescations [91, 106, 342]. Also, many academic efforts aim at applying securityconcepts from operating systems to the web platform [198, 332, 369, 389, 390].4.6 Research GapsAs software vulnerabilities are the primary source of security breaches, the useof software hardening and exploit mitigation techniques is very important, asthey can offer instant and effective protection against current and future threats.However, the runtime overhead that many of these mechanisms impose, andthe deployment complexity of others, often prevent their widespread adoption.Furthermore, not all software developers harden the software they write, sourcecode is not available for commercial applications, and determined attackershave been constantly bypassing security measures [82, 101, 114, 159, 304].For instance, although address space randomization is an effective countermeasureagainst code-reuse attacks, its effectiveness is hindered by code segmentsleft in static locations [186, 224], while, depending on the randomizationentropy, it might be possible to circumvent it using brute-force guessing [347].Even if all the code segments of a process are fully randomized, vulnerabilitiesthat allow the leakage of memory contents can enable the calculation of thebase address of a DLL at runtime [256, 346, 386]. The above is indicative ofa constantly recurring pattern of exploit mitigations that require significanteffort to be deployed and adopted, only to be bypassed by a more sophisticatedor alternative exploitation technique later on.Another important issue is the reliance on “remedy” methods that removespecific software vulnerabilities after they have been exposed (e.g., throughsoftware patches and automated operating system updates), or provide somemitigation by disinfecting infected hosts (e.g., through the use of virus scanners).Although such methods are very important for keeping systems in goodhealth and up to date with the latest security fixes, they cannot protect againstattacks that exploit previously unknown vulnerabilities. In such cases, therelevant patches or signatures provided by vendors to fix new security flaws ordetect new malware usually come late, as their generation relies on significant,time-consuming human intervention [350]. Furthermore, administrators aresometimes reluctant to use automated patch installation systems, as they firstneed to verify through extensive testing that the new patches will not introduceany stability problems [333].4.7 Example ProblemsA few indicative issues for which existing solutions still do not provide asatisfactory level of protection include:Memory corruption vulnerabilities: despite numerous approaches, from programminglanguage and compiler level improvements to operating sys-32
4.7. Example Problemstem mitigations, exploitable memory errors are still being found even inthe latest versions of widely used applications. The rise of mobile operatingsystems such as iOS and Android, in which third-party applicationsrun with lower privileges, has also made kernel-level memory corruptionvulnerabilities more relevant than ever—an area that has received lessattention compared to user-level applications because of the differentthreat model that usually applies on personal computers compared tomobile devices.Data exposure vulnerabilities: the fairly new ecosystem of feature-rich webservices and cloud-based applications, with the numerous componentsand interactions that are involved, continuously exposes subtle flawsin the languages, APIs, protocols, and client or server software used.Although so far a great deal of attention has been paid to preventing auser’s machine being taken over, as user data are shifted to the cloud,vulnerabilities in any of the above stages can lead to the exposure of confidentialinformation, ranging from browser cookies to private documents,with equally harmful consequences.33
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: 4.5. State of the Artparts of criti
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 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:
Page 106 and 107:
Page 108 and 109:
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
show all

syssec_red_book

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?