I happened across [Between Hype and Understatement: Reassessing Cyber Risks as a Security Strategy](http:\/\/scholarcommons.usf.edu\/cgi\/viewcontent.cgi?article=1107&context=jss) [PDF] when looking for something else at the [Journal of Strategic Security](http:\/\/scholarcommons.usf.edu\/jss\/) site and thought it was a good enough primer to annoy everyone with a tweet about it.<\/p>\n
The paper is—well—_kinda_ wordy and has a Flesch-Kincaid grade reading level of 16*<\/sup>, making well suited for academia, but not rapid consumption in this blog era we abide in. I promised some folks that I’d summarize it (that phrase always reminds me [of this](http:\/\/www.youtube.com\/watch?v=uwAOc4g3K-g)) and so I shall (try).<\/p>\n The fundamental arguments are:<\/p>\n – we underrate & often overlook pre-existing software weaknesses (a.k.a. vulnerabilities) The author discusses specific media references (there are a plethora of links in the endnotes) when it comes to hype and notes specific government initiatives when it comes to other topics such as incident handling\/threat sharing (the author has a definite UK slant).<\/p>\n I especially liked this quote on threat actors\/actions\/motives & information sharing:<\/p>\n > _[the] distributed nature of the Internet can make it difficult to clearly attribute some incidents [as] criminal, terrorist actions, or acts of war. Consequently, to affirm that “the principal difference” between [these] “is in the attacker’s intent” is far too simplistic when many cyber-attackers cannot be identified. It is also quite simplistic to attribute financial motivation only to cyber criminals since terrorists can be motivated by monetary gain in order to finance their political actions. [An] added difficulty is that a pattern of cyber incidents may not reveal itself unless information is shared between the different stakeholders. For example, taken in isolation, a bank’s website being temporarily unavailable may look innocuous and not worth reporting to the competent agencies. Yet, when associated with other cyber incidents in which the victims and timeframe are similar, it may reveal a concerted effort to target a particular type of business or e-government resources, a pattern of behavior that could amount to crime (fraud, espionage) or terrorism if the motive can be established. Detection thus may depend on information being shared._<\/p>\n She does spend quite a bit of ink on vulnerabilities. Some choice (shorter) quotes:<\/p>\n > _[the] economic analysis adopted by software companies does not take into account (or not sufficiently) that the costs of non- secure software are significant, that these costs will be borne by others on the network and ultimately by themselves in clean-up operations_<\/p>\n > _Of course, to fix the vulnerabilities after release is laudable; it is also commendable that those companies participate in huge clean-up operations of botnets like Microsoft did in 2010. However, there is nothing more paradoxical than Microsoft (and others) spending money to circumscribe the effects of the very vulnerabilities they contributed to create in the first place_<\/p>\n She then concludes with suggesting that governments work with ISPs to actually severely restrict or disable internet connections of users found to be infected and contributing to spam\/botnets, positing that this will cause users to demand more out of software vendors or use the free market to shift their loyalties to other software providers who do more to build less vulnerable software.<\/p>\n Again, I think it’s a good primer on the subject (despite some dubious analogies peppered throughout), but I also think there is too much focus on vulnerabilities and not enough on threat actors\/actions\/motives. I do like how she mixes economic theory into a topic that is usually defined solely in terms of warfare without diminishing the potential impacts of either.<\/p>\n It would have been pretty evident to see the influence of Beck & Giddens even if her references to [Risk Society](http:\/\/en.wikipedia.org\/wiki\/Risk_society) didn’t bookend the prose. I’ll leave you with what might just be her own one-sentence summary of the entire paper and definitely apropo for our current “cyber” situation:<\/p>\n > _[the] risks that industrialization and modernization created tend to be global, systemic with a “boomerang effect,” and denied, overlooked, or overhyped._<\/p>\n I happened across [Between Hype and Understatement: Reassessing Cyber Risks as a Security Strategy](http:\/\/scholarcommons.usf.edu\/cgi\/viewcontent.cgi?article=1107&context=jss) [PDF] when looking for something else at the [Journal of Strategic Security](http:\/\/scholarcommons.usf.edu\/jss\/) site and thought it was a good enough primer to annoy everyone with a tweet about it. The paper is—well—_kinda_ wordy and has a Flesch-Kincaid grade reading level of […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"activitypub_content_warning":"","activitypub_content_visibility":"","activitypub_max_image_attachments":3,"activitypub_interaction_policy_quote":"anyone","activitypub_status":"","footnotes":""},"categories":[681,3,650],"tags":[],"class_list":["post-2089","post","type-post","status-publish","format-standard","hentry","category-cybersecurity","category-information-security","category-risk-management-2"],"yoast_head":"\n
\n– we undervalue the costs of cybercrime by focusing solely on breaches & not including preventative\/deterrence costs
\n– we get distracted from identifying real threats by over-hyped ones
\n– we suck at information sharing (not enough of it; incomplete, at times; too many “standards”)
\n– we underreport incidents—and that this actually _enables_ attackers
\n– we need a centralized body to report incidents to
\n– we should develop a complete & uniform taxonomy
\n– we must pay particular attention to vulnerabilities in critical infrastructure
\n– we must pressure governments & vendors to take an active role in “encouraging” removing vulnerabilities from software during the SDLC, not after deployment<\/p>\n