Risk
3/28/2013
02:13 PM
Connect Directly
RSS
E-Mail
50%
50%

5 Steps To Strengthen Information Risk Profiles

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

3. You Need The Right People In The Room.

Establishing a risk profile that the business embraces requires involving the right people. Pironti recommended involving business process owners or "data owners." Ultimately, senior leadership will need to buy in as well. If you're unsure of whom the business process owners are in your organization, identify the people with profit-and-loss (P&L) responsibility. In other words: Whose bottom line gets hit if there's an information-related incident?

4. The Goal Is Not To Include Everything.

For businesses with finite resources -- and that's most of them -- trying to account for every shred of data that passes through the organization is not only inadvisable, it's a fast track to failure. Don't forget that the whole point of building an information risk profile is to prioritize based on your company's data and its relative importance for revenue, compliance and other factors.

"Look for the key business processes, the ones that are considered essentially important to the operations or health and safety of the organization," Pironti said. "It wouldn't be realistic to say that we should look at every detail and every thing."

Pironti applies the concept of "due care" here, which asks: Did you do what could be reasonably expected of you to protect your data? "That's your bare minimum starting point, and then you work upwards," Pironti said. "If there were a situation, we can [then] feel comfortable that we are protecting ourselves from legal concerns, from compliance concerns, from the court of public opinion -- as well as ensuring that our business can operate in a way that makes sense for us, versus what everybody else tells us we should do."

5. Avoid Too Many Cooks.

No one wants to be told their data or business process is a lower priority than that of the person sitting two doors down. Few people in a "get ahead" culture will ever willingly admit that their areas of responsibility aren't as important from a risk management standpoint. As a result, there's bit of diplomacy required of information security pros when developing a risk profile.

Pironti offered this tip: If there's already a business continuity or disaster recovery plan in place, start there -- a good one should have, in effect, already "ranked" the company's data priorities, which can help smooth out any ruffled feathers.

"A lot of organizations have already gone through that process, versus doing a real risk profile," Pironti said. "It's an easy starting point."

InformationWeek is conducting a survey on security and risk management. Take the InformationWeek 2013 Strategic Security Survey today. Survey ends March 29.

Previous
2 of 2
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-2595
Published: 2014-08-31
The device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which all...

CVE-2013-2597
Published: 2014-08-31
Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that lever...

CVE-2013-2598
Published: 2014-08-31
app/aboot/aboot.c in the Little Kernel (LK) bootloader, as distributed with Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to overwrite signature-verification code via crafted boot-image load-destination header values that specify memory ...

CVE-2013-2599
Published: 2014-08-31
A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption pas...

CVE-2013-6124
Published: 2014-08-31
The Qualcomm Innovation Center (QuIC) init scripts in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.4.x allow local users to modify file metadata via a symlink attack on a file accessed by a (1) chown or (2) chmod command, as demonstrated by changing the permissions of an arbitrary fil...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.