02:13 PM

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.

2 of 2
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Current Issue
Dark Reading Tech Digest September 7, 2015
Some security flaws go beyond simple app vulnerabilities. Have you checked for these?
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2015-10-02
Buffer overflow in Canary Labs Trend Web Server before 9.5.2 allows remote attackers to execute arbitrary code via a crafted TCP packet.

Published: 2015-10-02
Cisco NX-OS 6.0(2)U6(0.46) on N3K devices allows remote authenticated users to cause a denial of service (temporary SNMP outage) via an SNMP request for an OID that does not exist, aka Bug ID CSCuw36684.

Published: 2015-10-02
Cisco Email Security Appliance (ESA) 8.5.6-106 and 9.6.0-042 allows remote authenticated users to cause a denial of service (file-descriptor consumption and device reload) via crafted HTTP requests, aka Bug ID CSCuw32211.

Published: 2015-10-01
lxc-start in lxc before 1.0.8 and 1.1.x before 1.1.4 allows local container administrators to escape AppArmor confinement via a symlink attack on a (1) mount target or (2) bind mount source.

Published: 2015-10-01
kernel_crashdump in Apport before 2.19 allows local users to cause a denial of service (disk consumption) or possibly gain privileges via a (1) symlink or (2) hard link attack on /var/crash/vmcore.log.

Dark Reading Radio
Archived Dark Reading Radio
What can the information security industry do to solve the IoT security problem? Learn more and join the conversation on the next episode of Dark Reading Radio.