Attacks/Breaches
8/29/2014
12:31 PM
50%
50%

How To Create A Risk 'Pain Chart'

Consultant John Pironti outlines how to execute a risk-based approach to defending corporate assets.

If security and business operation requirements seem somewhat out of synch sometimes, it is because in many enterprises, they are. Yet aligning those two mandates can be critical for effectively protecting enterprises.

Next month at the Interop conference in New York, John Pironti, president of consulting company IP Architects, will be leading a workshop on aligning a risk-based approach to security to business needs and use it to better defend the organization and minimize risk. This process requires the creation of information risk profiles, threat and vulnerability analysis, vulnerability management, and business resiliency capabilities such as incident response. But many organizations are still falling short of this nirvana state of security, he says.

"I think that I would say that we have all the best intentions, but we're still following the shiny object in execution," he says.

While security professionals acknowledge the idea that they should be more business-aligned and better at applying an understanding of risk to their security strategy, the focus remains on trying to buy new technologies to solve all of an enterprise's problems, explains Pironti.

The key, he says, is to create a risk profile -- a pain chart for security that chronicles when an incident starts to hurt.

"First I figure out what my appetite is [for risk]," he says. "When does something become material to the organization? When does it come to the point where the organization says, 'enough is enough, we can't have this.' Then I build security frameworks, control models to reach to that level."

"That's how I turn the corner with the business, because now I'm not in contention with the business," he adds. "Now I can go back to the business and say, this is what you said…I built this to that level of capability. If that seems…too expensive to you or too much of an investment, then we need to recalibrate our expectations on what our risk appetite is."

The risk profile Pironti pitches includes the types and priority of information risks an organization finds acceptable and unacceptable. Organizations also need to take into account the legal standard of due care for the organization: the accepted minimum the organization would need to prove it was not reckless and did what a similar organization would do to secure its assets.

Every industry has a different tolerance for risk, Pironti says. For example, after TJX was breached several years ago, the company announced it had recorded strong sales even as it publicly acknowledged a significant jump in the costs associated with the incident. People tend to be harder on healthcare organizations however because healthcare records are viewed as more personal than credit cards, he argues.

"I can change credit cards; I can't change health records," Pironti says."So the impact is different."

The goal of the talk is to minimize the impact of an attack, he says.

"Let's understand that the inevitability is that something probably is going to happen within the operating career of an organization… Everything we're going to try and do is to shrink the problem. We are going to minimize impact, and our goal is to turn incidents into operational anomalies," he says.

Interop will run from September 29 to October 3 in New York.

Brian Prince is a freelance writer for a number of IT security-focused publications. Prior to becoming a freelance reporter, he worked at eWEEK for five years covering not only security, but also a variety of other subjects in the tech industry. Before that, he worked as a ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
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.
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
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.