Attacks/Breaches

7/11/2018
10:30 AM
Jack Jones
Jack Jones
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv

What We Talk About When We Talk About Risk

Measuring security risk is not that hard if you get your terms straight and leverage well-established methods and principles from other disciplines.

Source: Jack Jones
Source: Jack Jones

Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
7/11/2018 | 2:59:02 PM
Re: Cybersecurity Risk Taxonomy
Small Business - general rule is that a small business (I guess 50 emps or less) can live for only 2 weeks following a major crash of systems.  I supported such shops and always had a backup-restore plan in working place and used it on several critical cases inclusive of server drive failure and ransomware attack.   Measure THAT!!!   (Lesson - always ask for a large check for services in such cases).
jonesj26
50%
50%
jonesj26,
User Rank: Author
7/11/2018 | 1:44:13 PM
Re: Cybersecurity Risk Taxonomy
Thanks, Christian.  You're absolutely right about this problem being discussed for some time now.  Unfortunately, I don't believe it's broadly recognized yet as a foundational Achilles Heel for our profession.  Hopefully we can elevate it within the minds of our colleagues and accelerate the evolution of our profession.

Cheers

Jack
Christian Bryant
50%
50%
Christian Bryant,
User Rank: Ninja
7/11/2018 | 11:43:29 AM
Cybersecurity Risk Taxonomy
These are excellent points - in fact, the very list of risks you noted that are typically raised when asked are the ones I tend to see in initial project documents that relate to security.

Cybersecurity Risk Taxonomy (A. M. Rea-Guaman, T. San Feliu, J. A. Calvo-Manzano, I. D. Sanchez-Garcia) is a paper published under the International Conference on Software Process Improvement, 2017. It covers an interesting deep dive into studies published from 1990 to 2017. They found "132 papers and some of them mention some risk taxonomies within the scope of IT (information technologies) cybersecurity, although only five primary elements were selected, identifying the main risk taxonomies."

The perspectives covered include Asset, Attacks, Service, Business and External, with papers covering a wide range of combinations of taxonomy descriptions. Some of the items in the taxonomies include Business objects and dynamics models, Social engineering, Systems and technology failures, Failed internal processes, Resource or target information and Actions of people.

Your example InfoSec risks make sense upon more reading of studies like the one above, which is a great piece indicating this conversation of risk in InfoSec has been going on for some time.
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Ticketmaster Breach Part of Massive Payment Card Hacking Campaign
Jai Vijayan, Freelance writer,  7/10/2018
Lessons from My Strange Journey into InfoSec
Lysa Myers, Security Researcher, ESET,  7/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Cyberspace is much less secure than my old lamp.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-6681
PUBLISHED: 2018-07-17
Abuse of Functionality vulnerability in the web interface in McAfee Network Security Management (NSM) 9.1.7.11 and earlier allows authenticated users to allow arbitrary HTML code to be reflected in the response web page via appliance web interface.
CVE-2018-13864
PUBLISHED: 2018-07-17
A directory traversal vulnerability has been found in the Assets controller in Play Framework 2.6.12 through 2.6.15 (fixed in 2.6.16) when running on Windows. It allows a remote attacker to download arbitrary files from the target server via specially crafted HTTP requests.
CVE-2018-14338
PUBLISHED: 2018-07-17
samples/geotag.cpp in the example code of Exiv2 0.26 misuses the realpath function on POSIX platforms (other than Apple platforms) where glibc is not used, possibly leading to a buffer overflow.
CVE-2018-14337
PUBLISHED: 2018-07-17
The CHECK macro in mrbgems/mruby-sprintf/src/sprintf.c in mruby 1.4.1 contains a signed integer overflow, possibly leading to out-of-bounds memory access because the mrb_str_resize function in string.c does not check for a negative length.
CVE-2018-14329
PUBLISHED: 2018-07-17
In HTSlib 1.8, a race condition in cram/cram_io.c might allow local users to overwrite arbitrary files via a symlink attack.