Corporations not doing enough to protect data from Internet risk, CMU report says
Corporate boards of directors and senior management aren't adequately involved in the privacy and security of their computer systems and data, according to a new report released today by Carnegie Mellon University's CyLab.
The report, "Governance of Enterprise Security: CyLab 2010 Report," found that while company boards are taking risk management seriously, there remains a gap in understanding the relationship between information technology, or IT, and risk management.
The report is being presented today at the Bloomberg Boards & Risk Briefing, in Washington, D.C. The report is based on the results from 66 respondents to its survey at the board or senior executive level from Fortune 1000 companies. It builds on CyLab's first survey, conducted in 2008.
"The survey results indicate that boards and senior executives need to be more actively involved in the governance of the privacy and security of their computer systems and data, but this year's study shows some important areas of improvement," said Jody Westby, a distinguished fellow in CMU's CyLab, and CEO of Global Cyber Risk LLC, in a statement.
The report found that a majority of companies don't have full-time privacy, security and risk executives responsible for those issues. Respondents indicated that corporate boards reviewing privacy and security issues weren't focusing on activities that would help protect the organization from high-risk situations, such as reputational or financial losses due to breaches of personal identity information or theft of confidential or proprietary information.
The study makes 10 recommendations to improve Internet security. Among the suggestions:
• Review the components of an organization's security program and ensure that it meets best practices and standards and includes incident response, disaster recovery and breach response plans.
• Evaluate the existing organizational structure and establish a cross-organizational team that's required at least monthly to coordinate and communicate on privacy and security issues.
• Establish a board risk committee separate from the board audit committee and assign it responsibility for risks, including information technology risks. Recruit directors with risk and information technology governance expertise.
Show commenting policy
TribLive commenting policy
You are solely responsible for your comments and by using TribLive.com you agree to our Terms of Service.
We moderate comments. Our goal is to provide substantive commentary for a general readership. By screening submissions, we provide a space where readers can share intelligent and informed commentary that enhances the quality of our news and information.
While most comments will be posted if they are on-topic and not abusive, moderating decisions are subjective. We will make them as carefully and consistently as we can. Because of the volume of reader comments, we cannot review individual moderation decisions with readers.
We value thoughtful comments representing a range of views that make their point quickly and politely. We make an effort to protect discussions from repeated comments either by the same reader or different readers.
We follow the same standards for taste as the daily newspaper. A few things we won't tolerate: personal attacks, obscenity, vulgarity, profanity (including expletives and letters followed by dashes), commercial promotion, impersonations, incoherence, proselytizing and SHOUTING. Don't include URLs to Web sites.
We do not edit comments. They are either approved or deleted. We reserve the right to edit a comment that is quoted or excerpted in an article. In this case, we may fix spelling and punctuation.
We welcome strong opinions and criticism of our work, but we don't want comments to become bogged down with discussions of our policies and we will moderate accordingly.
We appreciate it when readers and people quoted in articles or blog posts point out errors of fact or emphasis and will investigate all assertions. But these suggestions should be sent via e-mail. To avoid distracting other readers, we won't publish comments that suggest a correction. Instead, corrections will be made in a blog post or in an article.