This is cache of http://blog.gartner.com/blog/security.php?x=0&itemid=3099. Cache is the snapshot of article that we took when we index feed.
To see original page click here.
We are not affiliated with the authors of this article and not responsible for its content.
Defining Risk Management
2008-02-05 18:52:39 by Posted By: Paul Proctor, Research VP in IT Leaders - Security and Risk Management
 
The rise of risk management as both a discipline and a reference has led to confusion in terminology and applicability. The word "risk" has proliferated in titles for traditional roles and responsibilities such as security, business continuity, privacy and many operations functions. In some cases, this is nothing more than a title change with no fundamental shift in methodology. This proliferation has led organizations to struggle at the top with clearly defining what enterprise risk management (ERM) means to their organization, and at the bottom with defining what "risk" people do vs. their counterparts in traditional operational roles. Even within the various risk management groups, organizations must clearly define how responsibility is assigned.

The term "risk management" has grown in popularity to the point where it has been watered down, made irrelevant and considered a failure in many organizations. IT vendors have precipitated this by labeling many automation and management products with "Risk Management" or "GRC" in an attempt to take advantage of the popularity of the term. Many organizations have followed suit by mislabeling traditional, less mature approaches to addressing risks that typically involve isolated decisions in reaction to loss events or the indiscriminate application of technology without good governance, risk measurement or a transparent methodology. Organizations should use the label "risk management" only with efforts that apply a proactive approach to measuring reasonably anticipated risks and applying appropriate controls.

Organizations should start with a good internal risk hierarchy definition to which all risk-related groups can align. There is no single definition that works for all organizations, and differences will remain in the silos, but it is important to start from a common, overarching definition. This will help eliminate overlap in the silos, avoid gaps in coverage and facilitate good governance.

We have research on the way to help you.
 
 
 
 
 
 
TOP SEARCH
Expand / MinimizeClose Widget
  •  
RECENT SEARCH
Expand / Minimize
  •  
RELATED VIDEO
Expand / Minimize
SecurityRatty FAQ
Sergey Zarubin, 31yo
CISSP, CCSP
Moscow, Russia