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.

Risk

12/13/2013
07:05 AM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Advancing The IT Security DNA Through Risk Management

Shifting focus from the bright shiny things to critical business processes can actually stand to advance security technical maturity along with true risk mitigation

If an IT security organization feels it's in a maturity rut, perhaps stuck in the compliance-focused hamster wheel or lacking enough line-of-business support to make necessary security investments, one of the fast ways out of it is to take the spotlight away from security processes and technology and move it to business processes and business risks.

"Shifting the focus from technical things, from the bright, shiny security objects, to instead being about critical business processes, that shift is a big deal for risk management," says Sam Curry, chief strategy officer and chief technologist for RSA, the security division of EMC.

In its work with members of its Security for Business Innovation Council (SBIC), RSA recently helped publish a report on how to transform information security, with highlighted recommendations from security executives at a selection of Global 1000 firms. Among the five major suggestions for future-proofing security processes, three of them revolved around reworking IT risk management so its activities are cast in the light of its relativity to the business.

According to leading CISOs and CSOs, in addition to shifting their focus from technical assets to critical business processes, they should also be instituting business estimates of cybersecurity risks in order to show the financial impact to the business when risks come to play, as well as establishing a business-centric risk assessment process.

Critical to all of it is meaningful collaboration -- essentially folding in IT risk management decision-making into every business initiative of the company just as enterprise risk management is involved to calculate other business risks.

[Are you using your human sensors? See Using The Human Perimeter To Detect Outside Attacks.]

"A key aspect of risk management is having a process in place to ensure that for every initiative in your organization, a risk assessment is done at a very early stage in the lifecycle," says one SBIC participant, Vishal Salvi, CISO for HDFC Bank Limited.

It's why Dwayne Melancon of Tripwire recommends cross-functional teams to help establish a good hybrid perspective on IT risks.

"A number of organizations I work with have cross-functional teams that look at risk holistically to better understand dependencies, and these teams make recommendations about which risks the company should focus on from a business perspective," says Melancon, CTO of Tripwire. "The discussion and agreement process makes it a lot easier to allocate scarce resources to the highest priorities for the whole business."

Melancon says that focusing too much on technical risks instead of business risks is a common mistake of IT professionals working in isolation while conducting risk assessments.

"A top down, risk-based approach is best -- it allows you to focus on the 'so what?' aspect of risk to the business, instead of going down a technical rat hole around a risk that doesn't really impact the business in a significant way," he says.

This last point is important in understanding how collaboration between IT security and line-of-business leaders should work; the teamwork shouldn't be focused on making business people learn the intricacies of IT security technology. In fact, it means the opposite, Curry says.

"The security guys have to wake up and learn about business. It means the security people have to start carrying business books around and start talking to their peers and that will do more to advance the DNA of a company from a security perspective than the reverse," Curry says. "And when you do that, you find the technical maturation happens more easily."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.