Risk
3/28/2013
02:13 PM
50%
50%

5 Steps To Strengthen Information Risk Profiles

Make sure you include the right employees and business processes when developing risk management strategy.

9 Bandwidth Hogs: Reality Vs. Myth
9 Bandwidth Hogs: Reality Vs. Myth
(click image for larger view and for slideshow)
Consider the phrase "information risk profile." It sounds serious, important. It sounds like something most companies should have in the information age. Yet it's risk-management strategy that's easy to put off or ignore altogether.

For organizations with an outdated. insufficient or altogether nonexistent information risk profile, it helps to start with a basic question: Just what the heck is one?

"I look at it as conversation that discusses the organization's tolerance for loss, disruption or availability issues regarding their data assets," IP Architects president John Pironti said in an interview. "When does it hurt when they lose something?

Having that conversation, as it were, can help companies define and prioritize smarter approaches to securing and safeguarding their information, no matter what that information might be. This is turn helps minimize the potential pain when things go wrong: Financial loss, PR embarrassment, productivity drains and similar downsides.

[ Are passwords passé? Read Kill Passwords: Hassle-Free Substitute Wanted. ]

Among the many reasons an information risk profile is an important tool in the digital age: A comprehensive one can help organizations clarify what is actually important versus what is perceived to be important. Failing to make that distinction often leads to wasted resources, ineffective strategies and poor decision making.

Pironti, who will chair the Information Security and Risk Management track at Interop, offered this advice on building effective, efficient information risk profiles.

1. Heed The Difference Between "Risk" And "Threat."

Pironti noted a common misconception about information risk: "I think security professionals, myself included, spend too much time thinking that they know 'risk' when they really know 'threat,'" he said. Although "threat" might apply to areas such as malware or phishing scams, "risk" should include a much broader view of data loss, corruption or downtime, no matter the cause.

Comprehensive profiles address not just targeted or indiscriminate security attacks, but risk of all kinds: Employee error, technology failure, vendor mistakes and so on. "At the end of the day, they have the same business impact," Pironti said.

2. Company Should 'Own' The Profile.

"You're looking for the business leadership to really help to understand: What should we care about and why?" Pironti said. This can be easier said than done, Pironti added, because executives and managers are often paid to take risks. But Pironti's view is shared by others in the security and privacy field.

Although information security pros should lead the process, the end result should be owned and maintained by the business. "If security guys just go around and give their perspectives and look for a rubber stamp from the business, it probably won't be embraced [or] viewed as something that's credible," he said. "It's probably not going to make it to the senior leadership or to the board level because it's going to be viewed as an operational review rather than a business-level review."

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-1449
Published: 2014-12-25
The Maxthon Cloud Browser application before 4.1.6.2000 for Android allows remote attackers to spoof the address bar via crafted JavaScript code that uses the history API.

CVE-2014-2217
Published: 2014-12-25
Absolute path traversal vulnerability in the RadAsyncUpload control in the RadControls in Telerik UI for ASP.NET AJAX before Q3 2012 SP2 allows remote attackers to write to arbitrary files, and consequently execute arbitrary code, via a full pathname in the UploadID metadata value.

CVE-2014-3971
Published: 2014-12-25
The CmdAuthenticate::_authenticateX509 function in db/commands/authentication_commands.cpp in mongod in MongoDB 2.6.x before 2.6.2 allows remote attackers to cause a denial of service (daemon crash) by attempting authentication with an invalid X.509 client certificate.

CVE-2014-7193
Published: 2014-12-25
The Crumb plugin before 3.0.0 for Node.js does not properly restrict token access in situations where a hapi route handler has CORS enabled, which allows remote attackers to obtain sensitive information, and potentially obtain the ability to spoof requests to non-CORS routes, via a crafted web site ...

CVE-2014-7300
Published: 2014-12-25
GNOME Shell 3.14.x before 3.14.1, when the Screen Lock feature is used, does not limit the aggregate memory consumption of all active PrtSc requests, which allows physically proximate attackers to execute arbitrary commands on an unattended workstation by making many PrtSc requests and leveraging a ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.