Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
What We Talk About When We Talk About Risk
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
RetiredUser
50%
50%
RetiredUser,
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.


7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-8003
PUBLISHED: 2020-01-27
A double-free vulnerability in vrend_renderer.c in virglrenderer through 0.8.1 allows attackers to cause a denial of service by triggering texture allocation failure, because vrend_renderer_resource_allocated_texture is not an appropriate place for a free.
CVE-2019-20427
PUBLISHED: 2020-01-27
In the Lustre file system before 2.12.3, the ptlrpc module has a buffer overflow and panic, and possibly remote code execution, due to the lack of validation for specific fields of packets sent by a client. Interaction between req_capsule_get_size and tgt_brw_write leads to a tgt_shortio2pages integ...
CVE-2019-20428
PUBLISHED: 2020-01-27
In the Lustre file system before 2.12.3, the ptlrpc module has an out-of-bounds read and panic due to the lack of validation for specific fields of packets sent by a client. The ldl_request_cancel function mishandles a large lock_count parameter.
CVE-2019-20429
PUBLISHED: 2020-01-27
In the Lustre file system before 2.12.3, the ptlrpc module has an out-of-bounds read and panic (via a modified lm_bufcount field) due to the lack of validation for specific fields of packets sent by a client. This is caused by interaction between sptlrpc_svc_unwrap_request and lustre_msg_hdr_size_v2...
CVE-2019-20430
PUBLISHED: 2020-01-27
In the Lustre file system before 2.12.3, the mdt module has an LBUG panic (via a large MDT Body eadatasize field) due to the lack of validation for specific fields of packets sent by a client.