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
How To Create A Risk 'Pain Chart'
Newest First  |  Oldest First  |  Threaded View
JasonSachowski
50%
50%
JasonSachowski,
User Rank: Author
9/3/2014 | 11:50:07 AM
Re: How To Create A Risk 'Pain Chart'
@MarilynCohodas, everything security always comes back to the business it supports which would be no different with determining risk/pain priorities.  A "committee" of decisison makers should be made up of people who can translate the techie-talk into meanful business language and consists of stakeholders throughout the organization (ex. InfoSec, Privacy, Legal, etc), shareholders, and executives.
GonzSTL
50%
50%
GonzSTL,
User Rank: Ninja
9/3/2014 | 11:40:31 AM
Re: Providing relatable value
This is classic Risk Management, and is nothing new. I believe that the ultimate sign off should lie in the hands of someone responsible for the entire organization, such as the CEO, COO, CRO, etc. As long as the proper personnel are involved in the risk assessment team, the security officer makes recommendations based on a well informed decision process conducted by the team. Mind you, the assumption is that the risk assessment is conducted properly. If the security office is empowered to make the decision, then certainly the officer has the final say, with the implied consent of the CEO through delegation of authority.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
9/2/2014 | 2:06:47 PM
Re: Providing relatable value
I would think that everyone on a security team would have the ability to determine what has a higher risk value than others. Its a group effort. However, you need an authoritative head to sign off on these decisions. I would say the person who signs off on corporate security policy would be the authoratative head here. Most likely the CSO/CISO. 

I think a good way to look at this principle is you wouldn't construct a $1000 fence to guard a $10 asset. Realistic safeguards need to be a priority.
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
9/2/2014 | 9:50:14 AM
Re: Providing relatable value
Concept sounds great to me, but who woud the decisionmakers be in determining risk/pain priorities? Thoughts anyone?  
Stratustician
50%
50%
Stratustician,
User Rank: Moderator
9/2/2014 | 9:09:50 AM
Re: Providing relatable value
I agree, I especially love the idea of assigning a risk or impact value to each specifically since as pointed out, some assets have more value than others.  Treating all risks as the same threat level is no longer a way to ensure that you are prioritizing the right areas of your security plan.  It's also a great way, as illustrated in the article, to ask for the funding you really need for each project based on the real risks and costs associated to protect those assets.
JeremiahT680
50%
50%
JeremiahT680,
User Rank: Apprentice
9/1/2014 | 12:28:28 PM
Sandboxing data inside an encrypted application layer
If you sandbox each record or entity within and create an interface in your own coding language the perhaps you could create so many layers or barriers to cross that the intrusion would be detected and prevented.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
8/29/2014 | 2:38:49 PM
Providing relatable value
This is great! For years now, Information Security has been progressing to the point where we can display extreme value to the business side of the operation. Not that we were irrelevant in the past, but I feel that we are getting the the point where non-security people can easily relate as to why security measures are so important.

In years to come I feel that this exercise will be quite prevalent and most likely already be ingrained in the minds of business owners. Educative repetition and relation analysis is the key.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-4103
PUBLISHED: 2022-01-23
Cross-site Scripting (XSS) - Stored in GitHub repository vanessa219/vditor prior to 1.0.34.
CVE-2021-4172
PUBLISHED: 2022-01-22
Cross-site Scripting (XSS) - Stored in GitHub repository star7th/showdoc prior to 2.10.2.
CVE-2022-23807
PUBLISHED: 2022-01-22
An issue was discovered in phpMyAdmin 4.9 before 4.9.8 and 5.1 before 5.1.2. A valid user who is already authenticated to phpMyAdmin can manipulate their account to bypass two-factor authentication for future login instances.
CVE-2022-23808
PUBLISHED: 2022-01-22
An issue was discovered in phpMyAdmin 5.1 before 5.1.2. An attacker can inject malicious code into aspects of the setup script, which can allow XSS or HTML injection.
CVE-2022-21707
PUBLISHED: 2022-01-21
wasmCloud Host Runtime is a server process that securely hosts and provides dispatch for web assembly (WASM) actors and capability providers. In versions prior to 0.52.2 actors can bypass capability authorization. Actors are normally required to declare their capabilities for inbound invocations, bu...